Cannot parse JSON Error when processing a long response

[sammefford]

Cannot parse JSON Error when processing a long response

com.marklogic.client.MarkLogicIOException: Cannot parse JSON '[{"ICS_codeData":{"midbData":{"co' for fn:doc("/content/GUIDE://1972/4442a1b1-2107-4796-b2da-7bf722d05fc1/ndl-w/u/|||/a2a6f9a4-3261-421b-a309-00631c482ebc.json")
        at com.marklogic.client.io.SearchHandle$MatchDocumentSummaryImpl.populateExtractedResult(SearchHandle.java:607) ~[java-client-api-3.0.3.jar:na]
        at com.marklogic.client.io.SearchHandle$MatchDocumentSummaryImpl.getExtracted(SearchHandle.java:567) ~[java-client-api-3.0.3.jar:na]
        at MarkLogicDatabaseClientTestCase.queryForCodePage(MarkLogicDatabaseClientTestCase.java:127) [TestCase/:na]
        at MarkLogicDatabaseClientTestCase.main(MarkLogicDatabaseClientTestCase.java:162) [TestCase/:na]
Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected end-of-input: was expecting closing '"' for name
 at [Source: [{"ICS_codeData":{"midbData":{"co; line: 1, column: 67]
        at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1581) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:533) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.core.base.ParserMinimalBase._reportInvalidEOF(ParserMinimalBase.java:470) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._parseName2(ReaderBasedJsonParser.java:1447) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._parseName(ReaderBasedJsonParser.java:1431) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextFieldName(ReaderBasedJsonParser.java:778) ~[jackson-core-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:208) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeObject(JsonNodeDeserializer.java:224) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.BaseNodeDeserializer.deserializeArray(JsonNodeDeserializer.java:270) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:71) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.deser.std.JsonNodeDeserializer.deserialize(JsonNodeDeserializer.java:15) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3736) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.fasterxml.jackson.databind.ObjectMapper.readTree(ObjectMapper.java:2271) ~[jackson-databind-2.6.5.jar:2.6.5]
        at com.marklogic.client.io.SearchHandle$MatchDocumentSummaryImpl.populateExtractedResult(SearchHandle.java:600) ~[java-client-api-3.0.3.jar:na]
        ... 3 common frames omitted

PR: #593

[sammefford]

Copy of #598 for 3.x branch

[laquereric]

Sorry to bother ... Is there an anticipated completion data for java-client-api-3.0.5?

[kcoleman-marklogic]

I believe Sam is on vacation, so I'll throw in my two cents:

I think that's probably the wrong milestone, unless Sam plans to make a patch available. We've already released 3.0.6. I don't think we have a timeline for 3.0.7 yet.

[laquereric]

Thanks Kim - I appreciate your reply... Here is the situation: A ML customer is running a patched version of this library and that is reducing a quality metric of the whole system. They researched this and they would like to get back to 'released code' ASAP. I think Sam put this on 'milestone:java-client-api-3.0.5'. Maybe it should be on either 3.0.7 or on a new milestone 3.0.6.1? It would be great it we could expedite this. Thanks! Eric

…

On Thu, Dec 22, 2016 at 1:55 PM, Kim Coleman ***@***.***> wrote: I believe Sam is on vacation, so I'll throw in my two cents: I think that's probably the wrong milestone, unless Sam plans to make a patch available. We've already released 3.0.6. I don't think we have a timeline for 3.0.7 yet. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#598 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAihfDL8zKxzyiSeBmNo668y71K8xaoks5rKsemgaJpZM4LK25O> .

-- Eric Laquer cell: 215 527 1106

[sammefford]

Thanks for pointing that out. I'm not sure why I set the milestone to 3.0.5, I meant 3.0.7. I'm not the one to set priorities or release dates . . . please go to through "usual" channels for that (i.e. support). If it will help for me to get the code merged into github, I can prioritize that. However, I was thinking that's not the goal. You're looking for an official release, correct? To get that prioritized, I believe our support organization has channels.

[laquereric]

Sorry - I'm behind on my personal..... I think we are fine to pick this uo after vaca... Regards, Eric

…

On Thu, Dec 22, 2016 at 5:24 PM, Sam Mefford ***@***.***> wrote: Thanks for pointing that out. I'm not sure why I set the milestone to 3.0.5, I meant 3.0.7. I'm not the one to set priorities or release dates . . . please go to through "usual" channels for that (i.e. support). If it will help for me to get the code merged into github, I can prioritize that. However, I was thinking that's not the goal. You're looking for an official release, correct? To get that prioritized, I believe our support organization has channels. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#598 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAihWIFaH8GLBIY-xvLpfa50ENvAuGZks5rKviqgaJpZM4LK25O> .

-- Eric Laquer cell: 215 527 1106

[sammefford]

Details to reproduce are attached to support ticket https://help.marklogic.com/staff/Tickets/Ticket/View/17586/inbox/-1/-1/-1/0/25
In comment from Thomas Diepenbrock posted on: 21 September 2016 04:49 PM