|
Re: The count query based on the vertex traversal edges is too slow!!!
Hi,
The first line in the code suggestion in my previous post should have been (added id() step):
targetIds = g.V().hasLabel('InstanceMetric').has('type', neq('network)).has('vlabel',
Hi,
The first line in the code suggestion in my previous post should have been (added id() step):
targetIds = g.V().hasLabel('InstanceMetric').has('type', neq('network)).has('vlabel',
|
By
HadoopMarc <bi...@...>
·
#5281
·
|
|
Re: The count query based on the vertex traversal edges is too slow!!!
Thank you very much for your answers, When I change the query statement to look like yours , it can go index query normally!
g.V().hasLabel('InstanceMetric').has('type',
Thank you very much for your answers, When I change the query statement to look like yours , it can go index query normally!
g.V().hasLabel('InstanceMetric').has('type',
|
By
wd w <wangwe...@...>
·
#5280
·
|
|
Re: java.lang.IllegalArgumentException: Could not instantiate implementation: org.janusgraph.diskstorage.es.ElasticSearchIndex
Looks like a version compatibility issue. What are your JanusGraph version and Elasticsearch version? Did you check if your version is supported as documented on
Looks like a version compatibility issue. What are your JanusGraph version and Elasticsearch version? Did you check if your version is supported as documented on
|
By
BO XUAN LI <libo...@...>
·
#5286
·
|
|
java.lang.IllegalArgumentException: Could not instantiate implementation: org.janusgraph.diskstorage.es.ElasticSearchIndex
I been trying to integrated apache atlas with janusgraph but it been giving below error. I am able to make it working on solr backend also the time and when I tried to switch to ELK backend I get the
I been trying to integrated apache atlas with janusgraph but it been giving below error. I am able to make it working on solr backend also the time and when I tried to switch to ELK backend I get the
|
By
Kalaiyarasi Thandavarayan <tkalai...@...>
·
#5279
·
|
|
Re: The count query based on the vertex traversal edges is too slow!!!
Hi,
Apparently, the query planner is not able to use the index for the outV() step. Can you see what happens if we split the query like this (not tested):
targetIds =
Hi,
Apparently, the query planner is not able to use the index for the outV() step. Can you see what happens if we split the query like this (not tested):
targetIds =
|
By
HadoopMarc <bi...@...>
·
#5278
·
|
|
Re: The count query based on the vertex traversal edges is too slow!!!
The total number of sides is 15000
The edge data meets the query condition is only 10000 in total
在2020年10月24日星期六 UTC+8 下午9:18:48<wd w> 写道:
The total number of sides is 15000
The edge data meets the query condition is only 10000 in total
在2020年10月24日星期六 UTC+8 下午9:18:48<wd w> 写道:
|
By
wd w <wangwe...@...>
·
#5277
·
|
|
Re: The count query based on the vertex traversal edges is too slow!!!
在2020年10月20日星期二 UTC+8 下午10:38:46<HadoopMarc> 写道:
在2020年10月20日星期二 UTC+8 下午10:38:46<HadoopMarc> 写道:
|
By
wd w <wangwe...@...>
·
#5276
·
|
|
Re: Deleting Composite doesn't remove the index
My problem is that the index is stuck in the DISABLED status, not INSTALLED. I tried to do the same thing as in that method (completed open transactions, closed unnecessary clusters), but this did not
My problem is that the index is stuck in the DISABLED status, not INSTALLED. I tried to do the same thing as in that method (completed open transactions, closed unnecessary clusters), but this did not
|
By
lex <lex.a...@...>
·
#5275
·
|
|
Re: Deleting Composite doesn't remove the index
Have you tried the solutions suggested in https://groups.google.com/g/janusgraph-users/c/GfYM538KsTo ?
Have you tried the solutions suggested in https://groups.google.com/g/janusgraph-users/c/GfYM538KsTo ?
|
By
BO XUAN LI <libo...@...>
·
#5274
·
|
|
Import graph from ConfiguredGraphFactory to hbase
Hello everyone, we want to test some OLAP queries for our requests,and, as far,as I understand, to do that, graph needs to be exported to Hadoop.
* janusgraph-0.5.1, hadoop-2.10.1
Currently we access
Hello everyone, we want to test some OLAP queries for our requests,and, as far,as I understand, to do that, graph needs to be exported to Hadoop.
* janusgraph-0.5.1, hadoop-2.10.1
Currently we access
|
By
Morgan Cole <morganc...@...>
·
#5273
·
|
|
Re: Deleting Composite doesn't remove the index
janusgraph 0.5.2, the same problem. Is anybody knows how to deal with it?
суббота, 22 февраля 2020 г. в 22:45:30 UTC+7, Shubham Yadav:
janusgraph 0.5.2, the same problem. Is anybody knows how to deal with it?
суббота, 22 февраля 2020 г. в 22:45:30 UTC+7, Shubham Yadav:
|
By
lex <lex.a...@...>
·
#5272
·
|
|
Re: The count query based on the vertex traversal edges is too slow!!!
Can you show the profiling of the query using the profile() step?
Best wishes, Marc
Op dinsdag 20 oktober 2020 om 14:22:59 UTC+2 schreef wan...@...:
Can you show the profiling of the query using the profile() step?
Best wishes, Marc
Op dinsdag 20 oktober 2020 om 14:22:59 UTC+2 schreef wan...@...:
|
By
HadoopMarc <bi...@...>
·
#5271
·
|
|
The count query based on the vertex traversal edges is too slow!!!
g.V().hasLabel("Instance").has("instanceId", P.within("12", "34")).bothE('Cause').has('enabled', true).as('e').bothV().has('instanceId', P.within('64', '123')).select('e').count();
The above count
g.V().hasLabel("Instance").has("instanceId", P.within("12", "34")).bothE('Cause').has('enabled', true).as('e').bothV().has('instanceId', P.within('64', '123')).select('e').count();
The above count
|
By
wd w <wangwe...@...>
·
#5270
·
|
|
Re: Memory leak in janus graph
Thanks Marc.Will do.
By
Sowmia J <sowm...@...>
·
#5269
·
|
|
Re: Modify Column.keys in projection query
Hi Alexander,
Readers of this list can help you better if you provide the query you tried on one of the example graphs or a sample graph you provide yourself.
The Column.keys and Column.values are not
Hi Alexander,
Readers of this list can help you better if you provide the query you tried on one of the example graphs or a sample graph you provide yourself.
The Column.keys and Column.values are not
|
By
HadoopMarc <bi...@...>
·
#5268
·
|
|
Re: Modify Column.keys in projection query
But map() can not be applied to Column.keys structure
вс, 18 окт. 2020 г. в 13:21, HadoopMarc <bi...@...>:
But map() can not be applied to Column.keys structure
вс, 18 окт. 2020 г. в 13:21, HadoopMarc <bi...@...>:
|
By
Александр Петраки <snuchib...@...>
·
#5267
·
|
|
Re: Modify Column.keys in projection query
Hi Alexander,
See:
https://groups.google.com/g/gremlin-users/c/OqpJwd2WWdk/m/3cKVp8iYDQAJ
Best wishes, Marc
Op donderdag 15 oktober 2020 om 13:26:36 UTC+2 schreef Александр Петраки:
Hi Alexander,
See:
https://groups.google.com/g/gremlin-users/c/OqpJwd2WWdk/m/3cKVp8iYDQAJ
Best wishes, Marc
Op donderdag 15 oktober 2020 om 13:26:36 UTC+2 schreef Александр Петраки:
|
By
HadoopMarc <bi...@...>
·
#5266
·
|
|
Re: Docker support for ConfiguredGraphFactory
Hi Mike,
I think the problem might be that the docker image replaces parts of the gremlin-server.yaml file at runtime using env variables. So not sure if copying the gremlin-server.yaml file will be a
Hi Mike,
I think the problem might be that the docker image replaces parts of the gremlin-server.yaml file at runtime using env variables. So not sure if copying the gremlin-server.yaml file will be a
|
By
Michael Kaiser-Cross <mkaise...@...>
·
#5265
·
|
|
Docker support for ConfiguredGraphFactory
I spent a while today looking through the janusgraph-docker repository on GitHub, and it didn't look like there is a good way to configure a ConfiguredGraphFactory without injecting a custom
I spent a while today looking through the janusgraph-docker repository on GitHub, and it didn't look like there is a good way to configure a ConfiguredGraphFactory without injecting a custom
|
By
Mike Thomsen <mikert...@...>
·
#5264
·
|
|
Re: EdgeId and RelationId using VertexWritable
Hi Anjani
Even I noticed the same (typeId is derived from edgeLabel) but the exact logic is still unknown to me too. For now I am relying on the observation that the typeId remains same for same
Hi Anjani
Even I noticed the same (typeId is derived from edgeLabel) but the exact logic is still unknown to me too. For now I am relying on the observation that the typeId remains same for same
|
By
"ra...@gmail.com" <rafi1...@...>
·
#5263
·
|