I mean that possibly we need to change the logic back to use `StaticArrayEntryList.of(Iterable<E> ... ...)` instead of `StaticArrayEntryList.of(Iterator<E> ... ...)`. If so, we may need to use

Hi, I am trying to connect to multiple schema's through java using the Cluster method. The properties files are as follows: gremlin-server.yaml # Copyright 2019 JanusGraph Authors # # Licensed under

What @porunov mentions, looks quite interesting. When I made the change in the code, I didn't actually notice I changed the signature that is used for `ofStaticBuffer`. But as you mentioned, it now

We've had another post about memory leaks just the other day, here: https://lists.lfaidata.foundation/g/janusgraph-users/message/5544 Do you think what you encountered is a duplicate of that problem

Got the same error throw new IllegalArgumentException("Store manager class " + graph.getBackend().getStoreManagerClass() + "is not supported");

One more thing I noticed is that previously we were passing `Iterable` and right now we are passing `Iterator` `ofStaticBuffer` and those methods are computed differently actually. Here are the first

Hello. I have been having memory leaks while using Janusgraph and found that there were a few places that I was not explicitly closing transactions and thought that might be the culprit. I am now

I did not figure out the reason of the problem, but what is interesting - CPU does not recover even after an hour or two and the process continues reading from Scylla with pretty high speed. Looks

Thank you for reporting this bug! That's interesting. The one difference I see is that now the code performs `rs.iterator()` immediately (and not lazily as it was previously). That said, I didn't

Hello, I would like to ask the following: Is there any recommended way to perform Schema/Data migration? Thanks in advance, Nick.

Hi there! What you describe looks very interesting and is definitely not intended behavior. You mentioned my PR which seems to cause these troubles. That's quite interesting because this PR was

Hi Mladen, Having answered several questions about the JanusGraph InputFormats, I can confirm that many users encounter problems with the size of the input splits. This is the case in particular for

After some research I figured out that rolling back this PR https://github.com/JanusGraph/janusgraph/pull/2080/files# helps

JG 0.5.3(same on 0.5.2), cannot be reproduced on JG 0.3.2 Backend: scyllaDB Indexing backend: ElasticSearch Steps to reproduce: 1) Create a node with a composite index for the field "X" 2) Create

Hello Mladen, Yes, we have experienced this issue as well, although we weren't able to fix it. You solution sounds very interesting, could you share your enhacement as a PR (even

Hi Mladen, I wasn’t aware that the CqlInputFormat we’re using is considered legacy. Looks then like we should migrate to spark-cassandra-connector. Could you please create an issue on GitHub

Hi, Can you provide more info on how the fields in your example are indexed? E.g. composite or mixed, what are all indexes involving any of these fields. 「Patrick Streifel <prstreifel@...>」在

We are running into a JanusGraph bug where a traversal that should return a list of vertices is returning an empty list. Here is some background info: Using a JanusGraph Server with

Hey there! I've recently been working on some Apache Spark jobs for Janusgraph via hadoop-gremlin (as described on https://docs.janusgraph.org/advanced-topics/hadoop/) and encountered several issues.

Thank you very much everyone