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
Possible Bug with Text.CONTAINS_REGEX & token toLowerCase

storage.parallel-backend-ops
Direct Search using Lucene

Sending multiple lines in the console to a remote server
Graph object not available to create custom long id in remote server setup
Different vertex Ids with exactly same properties
Preservation of order for LIST property
index convergence to REGISTERED failed
Does the quintillion edges limitation stil exists after introducing custom vertex id support?
