-
Notifications
You must be signed in to change notification settings - Fork 74
Closed
Description
I’ve been running some additional tests on the MarkLogic Java API using the 3.0-develop code and I’ve noticed an odd behavior. It seems as though whenever MarkLogic is queried for a page of results with an index greater than the number of held records (i.e. asking for the XXX Codes with a startIndex of 1mil when only 50k records are present), the MarkLogic server doesn’t populate the extract-resolution-time field in its response. This causes the MarkLogic Java API to throw an error when it attempts to convert the non-existent value of that field into a time. This commit ( 7ee7589 ) appears to be the cause of the error on the MarkLogic Java API side as before it there was no support the extract-resolution-time element.