|
I just hit this issue as well:
3.0.4:
2015-07-21T13:49:50.641+1000 I COMMAND [conn3] command cats.$cmd command: insert { insert: "mycats", documents: [ { _id: ObjectId('55adc15ec6f1d50f10afa54d'), name: "a"b" } ], orde
|
red: true } keyUpdates:0 writeConflicts:0 numYields:0 reslen:40 locks:{ Global: { acquireCount: { r: 2, w: 2 } }, MMAPV1Journal: { acquireCount: { w: 8 }, acquireWaitCount: { w: 1 }
|
, timeAcquiringMicros: { w: 23 } }, Database: { acquireCount: { w: 1, W: 1 } }, Collection: { acquireCount: { W: 1 } }, Metadata: { acquireCount: { W: 4 } } } 320ms
|
2015-07-21T13:50:21.742+1000 I QUERY [conn3] query cats.mycats query: { name: "a"b" } planSummary: COLLSCAN ntoreturn:0 ntoskip:0 nscanned:0 nscannedObjects:1 keyUpdates:0 write$onflicts:0 numYields:0 nreturned:1 reslen:56 locks:{ Global: { acquireCount: { r: 2 } }, MMAPV1Journal: { acquireCount: { r: 1 } }, Database: { acquireCount: { r: 1 } }, Collection$ { acquireCount: { R: 1 } } } 0ms
|
2.4.14:
In this case, escape characters also don't work in the 2.4.x shell - I needed to use ' (single quotes) as the outer to get a double quote in, backslash for escape seems to be broken
Tue Jul 21 14:10:34.412 [conn3] query cats.mycats query: { name: "a"b" } ntoreturn:0 ntoskip:0 nscanned:1 keyUpdates:0 locks(micros) r:87 nreturned:1 reslen:56 0ms
|
Also, I believe this is related to SERVER-14739, which covers newline escape characters.
|