Great to hear that worked for you. Caused by: com.datastax.oss.driver.api.core.DriverTimeoutException: Query timed out after PT2SAs seen from this PR:

Thanks Marc for response. Our graph is very large around 1TB, so can not hold in memory. Subgraphs that we want to retrieve can have 30 -40 connected nodes. We have requirement of around 200 TPS. We

Hi Chris, Hard to interpret your report. It maybe worthwhile to try the documented way of remote connection with traversal.withRemote(...) or

Hello, I wanted to try out the new Janusgraph 0.6.0 release and I encountered some unexpected issues while trying to deploy it on Cassandra 3.11.5. One of the issues I came across seems to be

Hi Anjani, How large is your graph, can you hold it in memory in its entirety? How large are the subgraphs you want to retrieve in terms of width and size? What are your requirements regarding TPS?

Hello, thanks for the responses. I attempted to add storage.cql.internal.string-configuration = "datastax-java-driver { advanced.metadata.schema.debouncer.window = 1 second }" to my

Hello Everyone, We have a requirement to build a search functionality to find connected nodes based on some identifiers with high performance and TPS. While doing analysis we noticed gremlin queries

Also, notice, if you want to use multiple configuration options, you will need to split them using new line character. I.e. `\n` and not `;`. See example here:

You can also play with `advanced.metadata.schema.debouncer.max-events`. For more configurations see: https://docs.datastax.com/en/developer/java-driver/4.13/manual/core/configuration/reference/

Hi, Mladen that issue is most likely related to this discussion of how the new CQL driver updates schema view: https://groups.google.com/a/lists.datastax.com/g/java-driver-user/c/Bc0gQuOVVL0 As

Hello, I wanted to try out the new Janusgraph 0.6.0 release and I encountered some unexpected issues while trying to deploy it on Cassandra 3.11.5. The first issue occurs during graph creation. I'm

Thank you Marc, I was able to reproduce your sample by console: :remote connect tinkerpop.server conf/remote.yaml session # it is GryoMessageSerializerV3d0 - no problem here, but must have

Here is how I see this: - the current public release with direct download is 4 years old 7.5.11, compiled with Java 8 and supporting Java 9 according to its and build script; - the public Oracle

Thanks for this information [I mean the facts, this forum is not intended to spread opinions on third parties]. After, checking, I was surprised myself. The deviation from the JE has occurred since

https://github.com/JanusGraph/janusgraph/issues/2808

Hi Chris, Thanks for reporting. I could confirm the exception you got by using the console and server files from the distribution. I got the right results, though, when I changed the contents of

I found the following information that might be important for those who (myself included) use or plan to use Bekeley JE as embedded storage: "The current public release of BDB JE is 7.5.11. What you

We have fully integrated our backend with JS:0.6 as recommended, including DB connection using new driver: GraphBinaryMessageSerializerV1. All seams o work as before, except: GraphTraversal<Vertex,

Hi Jan, When you say "We stopped testing HBase 1 in our CI solution already in branch 0.3" does that mean you are not sure whether HBase1 tests would run on a custom build for 0.4+? If so, the code

Will the support for BigTable persist when dropping HBase 1? With 0.5, JG uses the HBase 2 as client for Bigtable. Von: janusgraph-users@... <janusgraph-users@...> im Auftrag von schwartz@...