Changing default ES index name prefix
janusgraph_<index_name>
. I would like to change the prefix for all indices to something like jgtest1_<index_name>
.
I tried following the documentation (https://docs.janusgraph.org/index-backend/elasticsearch/#janusgraph-indexx-and-indexxelasticsearch-options), adding this line to the JanusGraph server .properties file:
index.search.elasticsearch.index-name = jgtest1
however, this does not seem to work. ...Migrating from Bigtable to Cassandra
Drop the Janus Graph Schema
Idempotent upsert, is that possible?
Deserializing of Vertex ID with Custom String value
TreeStep and MultiQuery support
g.V().has(...).out(...).has(...).out(...).has(...)
nicely leverages the MultiQuery optimisation and returns results in acceptable time.
However, as soon as we add a tree()
step, as in g.V().has(...).out(...).has(...).out(...).has(...).tree()
, all MultiQuery optimisations are disabled and the traversal time increases drastically.
Based on the following code, I think this applies to all Steps with PATH requirement (e.g. PathStep
, TreeStep
): https://github.com/JanusGraph/janusgraph/blob/v1.0/janusgraph-core/src/main/java/org/janusgraph/graphdb/tinkerpop/optimize/JanusGraphTraversalUtil.java#L393
...Deleting static Vertex Labels from the database
isStatic
on the vertexLabel, then it fails.
```...suggest an example to write spring-boot based rest api using janusgraph
Using custom vertex IDs for import/export
Olap using spark cluster taking much more time than expected.
Reindexing using the Mgmt System
Deleting duplicate connections from the schema?
JanusGraphManagement
interface. Due to a bug that existed for a long time that app created thousands of duplicate connections between same node and edge labels via management.addConnection()
.
This has become a problem, because these connections are getting cached in the StandardSchemaCache
which has unlimited size and started taking up all the heap. I'm looking for a way to safely delete the duplicated connections from the schema without dropping the schema and without disrupting other instances of the app working with this graph.
Does anyone have experience with anything similar? I'm currently exploring the internals of JanusGraphManagement
and ways to use the tx.query()
interface to remove the unwanted relations, but I'd really appreciate any tips and ideas of an easier/safer solution....Accelerating the vertex upsert
Janusgraph Tokenizer & Solr
JanusGraph 1.0 full-text search predicate in python - broken
TextP.textContains()
was serialized as if it were P.textContains()
.
That was changed in version 0.6.0 of JanusGraph to let JanusGraph serialize its predicates with a JanusGraph specific type identifier, but the server kept a fallback mechanism so it could still deserialize predicates sent that way: https://docs.janusgraph.org/changelog/#serialization-of-janusgraph-predicates-has-changed
This fallback mechanism was then removed in JanusGraph 1.0.0: https://docs.janusgraph.org/changelog/#remove-support-for-old-serialization-format-of-janusgraph-predicates
...Unable to use next() in gremlin-python
Speeding up node adding to Janusgraph
Splitting Backing ElasticSearch Index To Increase Primary Shards As JG Mixed Index Grows
Usage of _lock_ tables with ConfiguredGraphFactory vs. JanusGraphFactory
edgestore_lock_
and graphindex_lock_
. We are operating two JanusGraph clusters which use the same schema, both running on ScyllaDB. While one instance is managed by JanusGraphFactory
, we have configured multiple graphs in the other instance using ConfiguredGraphFactory
. Recently, we noticed an unexpected storage usage caused by the table edgestore_lock_
, so we started comparing the utilization of these tables for both scenarios:
```...StandardJanusGraph
when vp[~T$VertexExists->true]
is deleted. This only affects deletions because on additions, the vertex is always "new" https://github.com/JanusGraph/janusgraph/blob/06526e728f468bf7fca072c3cf2c5d9024830be0/janusgraph-core/src/main/java/org/janusgraph/graphdb/database/StandardJanusGraph.java#L762OLAP job failing with NullPointerException error