[SERVER-21467] Do not reverse byte order of GeoHash data on big-endian systems Created: 15/Nov/15 Updated: 23/Nov/16 Resolved: 22/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Portability |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bryan Chan | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Platforms F (01/29/16) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
src/mongo/db/geo/hash.cpp uses copyAndReverse to change the order of bytes in a hash when committing it to a buffer. This byte order reversal seems unnecessary on a big-endian system. |
| Comments |
| Comment by Githook User [ 25/Jan/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |
| Comment by Githook User [ 22/Jan/16 ] |
|
Author: {u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}Message: |