[GODRIVER-1456] Extended JSON writer should escape keys Created: 02/Jan/20 Updated: 28/Oct/23 Resolved: 07/Jan/20 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | JSON & ExtJSON |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Chiaravalloti | Assignee: | Isabella Siu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The extJSONValueWriter.WriteDocumenElement() method should escape keys when writing. The BI Connector team encountered an issue where a key with these characters "\usb#" could not be unmarshalled since that is not a valid unicode sequence. A simpler example is:
This outputs:
I believe this is the only line that requires a change; the key should be escaped before writing. |
| Comments |
| Comment by Ryan Chipman [ 08/Jan/20 ] |
|
BI Connector 2.13.3, which incorporates this fix, has been released. Thanks all for the expedited fix and release! |
| Comment by Githook User [ 07/Jan/20 ] |
|
Author: {'name': 'iwysiu', 'email': 'isabella.siu@10gen.com', 'username': 'iwysiu'}Message: |
| Comment by Githook User [ 07/Jan/20 ] |
|
Author: {'name': 'iwysiu', 'email': 'isabella.siu@10gen.com', 'username': 'iwysiu'}Message: |
| Comment by Chandler Wyatt [ 07/Jan/20 ] |
|
Hi All, I was wondering if we could establish a ballpark ETA for release of this bug fix. After a discussion with the CAE for the customer who encountered this bug (Utelogy), it seems that the customer is now considering moving away from mongo due to this issue, which is severely impacting the operability of their BI Connector, and preventing their move to production. I think if we can let the customer see the light at the end of the tunnel, we can get them off the ledge. I greatly appreciate your work on this and your consideration of establishing an ETA for the release. Thank you very much! |