[TINKERPOP-2145] Upgrading to 3.4.0 results in inconsistent query results

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 3.4.0
• Component/s: dotnet
• Environment: Azure CosmosDB, .NET Core 2.1
• Assignee: Unassigned
• Reporter: Ian Thomas
• Created: 25/Jan/19 21:04
• Updated: 20/Feb/19 19:42
• Resolved: 20/Feb/19 19:42

Description

I upgraded my application to use Gremlin.NET 3.4.0 in order to leverage the status attributes in the responses.  In particular, I was looking for RU cost and throttled request retry time from Cosmos.

In writing tests against this functionality to get into a throttled state, I started noticing that my queries were returning different results than expected.

For example, the below queries differ only by the presence of the property on `valueMap`, but in testing, return different results.  I haven't been able to determine any rule for how many results are missing, but the first query returns fewer results than the second.  I imagine it is because there is less data coming across with the limited scope of properties, but I really don't have any idea.

 g.V()
.hasLabel('vertexlabel').not(has('Property', true)) .has('StartDate', lte(_EndDate)).valueMap(true)

 g.V()
.hasLabel('vertexlabel').not(has('Property', true)) .has('StartDate', lte(_EndDate)).valueMap(true, 'StartDate')