Is there a way to configure NO_LIMIT in org.janusgraph.graphdb.query.BaseQuery

[sauvermazeotap]

• NO_LIMIT is defined as Integer.MAX_VALUE (2147483647) in org.janusgraph.graphdb.query.Query
• BaseQuery (parent of all query classes) is using NO_LIMIT for slice queries
• On K,V backends, this can get into full scan query
• Is there a way to configure BaseQuery limit at runtime? Also why is it set to Integer.MAX_VALUE?

[li-boxuan]

Can you give a scenario where you want to configure the limit? Does gremlin limit step not work for you?

[li-boxuan]

Can you show what the result of "mgmt.printIndexes()" is and what your JanusGraph version is?

[sauvermazeotap]

JG version is 0.5.2

PFB

`gremlin> mgmt = graph.openManagement()
==>org.janusgraph.graphdb.database.management.ManagementSystem@a91119b
gremlin> mgmt.printIndexes()
==>------------------------------------------------------------------------------------------------
Vertex Index Name | Type | Unique | Backing | Key: Status |

idIndex | Composite | true | internalindex | idValue: ENABLED |
| | | | idType: ENABLED |

Edge Index (VCI) Name | Type | Unique | Backing | Key: Status |

---

Relation Index | Type | Direction | Sort Key | Order | Status |
---------------------------------------------------------------------------------------------------`

The output is misformatted due to github markdown

[sauvermazeotap]

hey @li-boxuan, my bad, PFB observation with 0.5.2

gremlin> g.V().has('idValue','011c40f6-18d8-4111-77be-7ff5238d1eed').has('idType','id_mid_4').limit(1).bothE().otherV().profile()
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur

JanusGraphStep([],[idValue.eq(011c40f6-18d8-411... 1 1 2.747 84.89
_condition=(idValue = 011c40f6-18d8-4111-77be-7ff5238d1eed AND idType = id_mid_4)
_orders=[]
_limit=1
_isFitted=true
_isOrdered=true
_query=multiKSQ[1]@4
_index=idIndex
optimization 0.025
optimization 0.360
backend-query 0.000
_query=idIndex:multiKSQ[1]@4
_limit=4
JanusGraphVertexStep(BOTH,vertex) 20 20 0.489 15.11
_condition=(EDGE AND visibility:normal)
_orders=[]
_isFitted=true
_isOrdered=true
_query=org.janusgraph.diskstorage.keycolumnvalue.SliceQuery@8009c75e
_multi=true
_vertices=1
optimization 0.028
>TOTAL - - 3.237 -

One question here : with limit 1, why limit=4 is applied in multiKSQ?

[li-boxuan]

with limit 1, why limit=4 is applied in multiKSQ

That is a bug which is fixed in 0.6.0. The scheduled release deadline for 0.6.0 is May 1st.

[sauvermazeotap]

thanks @li-boxuan for the quick response