List property ordering - mixed index not used as expected
submissionDate4
property, it seems that mixed index is utilized for sorting as seen on single property - index used for ordering.png
enclosed....
Unable to use mounted configuration
ConfiguredGraphFactory works on versions<=0.6.4 but does not work with version>=1.0.0
The traversal source [g] for alias [g] is not configured on the server.
Guava com.google.common.base.Preconditions getting java.lang.IllegalArgumentException: null
Cross-graph querying with Janusgraph
How to disable embedded gremlin server in Janusgraph docker image?
CQL query timeout issues
Janusgraph + Solr Cloud + Zookeeper
Gremlin console ConfiguredGraphFactory issue with 1.1.0 (working fine on 1.0.0)
:> ConfiguredGraphFactory.getGraphNames()
. Thanks for the hints.Janusgraph-Cassandra Storage Backend issue and table clarification
Graph does not support the provided graph computer: SparkGraphComputer
graphManager: org.janusgraph.graphdb.management.JanusGraphManager
graphManager: org.janusgraph.graphdb.management.JanusGraphManager
Embedded graph with Scylla backend in Java
Wrote claim for id block threshold exception
Wrote claim for id block [9280001, 9360001] in PT1.2S => too slow, threshold is: PT0.3S
Wrote claim for id block [9280001, 9360001] in PT1.2S => too slow, threshold is: PT0.3S
Running OLAP queries on Janusgraph outside the Gremlin Console (from Java and G.V())
Groovy Mode
for query submission:...Support for saving arrays of vectors
Why queries are slow when more than one mixed index in query
ConfiguredGraphFactory.open("tenant51").traversal().V().has('_t', 'infra:container').has('_it', gt(123)).limit(100)
is taking 400ms
while
ConfiguredGraphFactory.open("tenant51").traversal().V().has('_it', gt(123)).limit(100)
or
ConfiguredGraphFactory.open("tenant51").traversal().V().has('t', 'infra:container').limit(100)
...
Index Creation Help
Transaction Recovery not working as expected
Transaction Failure
section here Failure & Recovery - JanusGraph for handling when persistence to indexing backends fail. I've enabled the tx write-ahead log and have tried setting up the recovery process. Based on the logs, it seems that the process is initializing properly but I don't see much after that and I don't believe indexing is being retried based on queries using this index. I also see that getStatistics returns 0,0. I'm wondering if anyone had any insight into what's going on here/what I might be missing?
We're using cassandra as our backend storage and lucene for indexing at the moment. Thank you!...