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

Unable to access/drop a vertex after dropping a property key.
Error during serialization: [no message for java.lang.NullPointerException]
exception every time we run either g.V(node_id).valueMap()
or g.V(node_id).drop().iterate()
. We were wondering if there is any way we could recover from this error or any workarounds...drop() slow performance
where to find gremlin-java docs
connect JG tutorial with java(dependency issues)
Changing the Cardinality of a Property
storage.cql.executor-service
Benchmarks
How to run the mapreduce reindexing job
Performance Problems/Config review