Date
1 - 3 of 3
Not sure if vertex centric index is being used
mo...@...
It does say isFitted=true in the pfofile output but it doesn't mention the relation Index name like it does in case of composite indexes.
Is it that for vertex centric indexes index name is not displayed in profile output? Is this a bug?
gremlin> g.V().has('project', 'projectId', 138).outE('hasHouseUnit').has('hasHouseUnitBlock', 'C').profile()
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur
=============================================================================================================
JanusGraphStep([],[~label.eq(project), projectI... 1 1 0.641 37.98
\_condition=(~label = project AND projectId = 138)
\_isFitted=false
\_query=multiKSQ[1]@2147483647
\_index=byProjectIdComposite
\_orders=[]
\_isOrdered=true
optimization 0.021
optimization 0.212
JanusGraphVertexStep([hasHouseUnitBlock.eq(C)]) 679 679 1.048 62.02
\_condition=(hasHouseUnitBlock = C AND type[hasHouseUnit])
\_isFitted=true
\_vertices=1
\_query=org.janusgraph.diskstorage.keycolumnvalue.SliceQuery@85318457
\_orders=[]
\_isOrdered=true
optimization 0.074
>TOTAL - - 1.690 -
hardy arora <hardi...@...>
I have the same question.
On Wednesday, 10 October 2018 05:53:36 UTC-4, m...@... wrote:
It does say isFitted=true in the pfofile output but it doesn't mention the relation Index name like it does in case of composite indexes.Is it that for vertex centric indexes index name is not displayed in profile output? Is this a bug?'hasHouseUnitBlock', 'C').profile()
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur
============================================================ ============================== ===================
JanusGraphStep([],[~label.eq(project), projectI... 1 1 0.641 37.98
\_condition=(~label = project AND projectId = 138)
\_isFitted=false
\_query=multiKSQ[1]@2147483647
\_index=byProjectIdComposite
\_orders=[]
\_isOrdered=true
optimization 0.021
optimization 0.212
JanusGraphVertexStep([hasHouseUnitBlock.eq(C)]) 679 679 1.048 62.02
\_condition=(hasHouseUnitBlock = C AND type[hasHouseUnit])
\_isFitted=true
\_vertices=1
\_query=org.janusgraph.diskstorage.keycolumnvalue.SliceQuery @85318457
\_orders=[]
\_isOrdered=true
optimization 0.074
>TOTAL - - 1.690 -
chrism <cmil...@...>
I have the same question. Anyone able to offer some light on this issue.
There is (as usually) certain way of constructing Gremlin Query to get local index used,
but there is not way to know it is used or not, making such effort rather a guess and trying to rely on speed improvements.
toggle quoted message
Show quoted text
There is (as usually) certain way of constructing Gremlin Query to get local index used,
but there is not way to know it is used or not, making such effort rather a guess and trying to rely on speed improvements.
On Wednesday, October 10, 2018 at 8:53:36 PM UTC+11 m...@... wrote:
It does say isFitted=true in the pfofile output but it doesn't mention the relation Index name like it does in case of composite indexes.Is it that for vertex centric indexes index name is not displayed in profile output? Is this a bug?
==>Traversal Metrics
Step Count Traversers Time (ms) % Dur
=============================================================================================================
JanusGraphStep([],[~label.eq(project), projectI... 1 1 0.641 37.98
\_condition=(~label = project AND projectId = 138)
\_isFitted=false
\_query=multiKSQ[1]@2147483647
\_index=byProjectIdComposite
\_orders=[]
\_isOrdered=true
optimization 0.021
optimization 0.212
JanusGraphVertexStep([hasHouseUnitBlock.eq(C)]) 679 679 1.048 62.02
\_condition=(hasHouseUnitBlock = C AND type[hasHouseUnit])
\_isFitted=true
\_vertices=1
\_query=org.janusgraph.diskstorage.keycolumnvalue.SliceQuery@85318457
\_orders=[]
\_isOrdered=true
optimization 0.074
>TOTAL - - 1.690 -