Issues faced for consistent indexing (both Composite & Mixed) [ElasticSearch]
Index wasn't created in ElasticSearch, giving a 404, when a vertex totals direct Index Query is performed
--> As a work around. for initial data 1000 Documents of sample data was ingested, and as we expected, the indexes were not present
--> data was re-indexed. Indexes were created in ElasticSearch, and some composite indexes needed re-Indexing as well. After reindexing, the performance was as expected...Custom ID best practice
Indexing
I need to perform upgrade my janusgraph to new version
script in empty-sample.groovy is called twice
JG 0.6 vs JG 1.0 different behaviour for same Gremlin query
ServerGremlinExecutor.<init> - Could not invoke constructor on class org.janusgraph.graphdb.manageme
ConfiguredGraphFactory
for dynamic graph creation.I configured 3 nodes to be the CassandraDB backend cluster, which are all up and running. Here's the complete janusgraph-cql-configuration.properties file:...
many graphs
JanusGraphFactory.open()
any more since JanusGraph Server already opened the graph instances for you.
By using the JanusGraphFactory directly in Gremlin Console you basically circumvent this whole functionality from JanusGraph Server and instead access the JanusGraph API directly to load the graphs yourselves. This means that it doesn't know about your Gremlin Server YAML which also explains why you cannot use graph names defined in that YAML...Indexing on vertex label
Add a collection of values in an edge property
g.addE('link').from('x').to('y').property('p', [1, 2, 4]).next() ...
Custom Vertex IDs and Serialized Graph
g.io("/tmp/foo.kryo").write().iterate()
Then doing the converse with a read()
but then it errors with must provide vertex id
....Concurrent updates during a REINDEX
JanusGraph can begin writing incremental index updates right after an index is defined. However, before the index is complete and usable, JanusGraph must also take a one-time read pass over all existing graph elements associated with the newly indexed schema type(s). Once this reindexing job has completed, the index is fully populated and ready to be used. The index must then be enabled to be used during query processing.which made me wonder how JanusGraph handles incremental updates happening concurrently to a
REINDEX
.
For instance, if we consider a slow reindexing process (e.g. done through the ManagementSystem
interface) that can take several hours, how are concurrent additions/updates/deletions of vertices/edges/properties handled?...Is Java 17 support on the roadmap?
Do Custom Vertex IDs Guarantee Single Instance of That Vertex?
Just wondering if we're still guaranteed vertex uniqueness that locking previously would (try to) enforce?Yes. And the reason is exactly what you suggested: the vertex id is what gets serialized to the backend. Good suggestion that we should have included it in the doc. Would you mind creating an issue or PR for that?...
secure connection - TLS
Best configuration for a single server
Elasticsearch mixed index performance
Support to query vertex with custom id in Gremlin.Net SDK
No serializer found for type 'janusgraph.RelationIdentifier'.
Stacktrace attached.
No serializer found for type 'janusgraph.RelationIdentifier'.
Stacktrace attached.
Vertex ID collisions