Hi ViVek, I would suggest to upgrade to 0.6.0 version of JanusGraph. It's hard to understand your case from that scope of information you provided. Generally, I would suggest checking if you always

To add to Mark's suggestions there is also a multiQuery option in janusgraph-core. Notice, it's internal API and not Gremlin. Thus, it might be unavailable to you if you can access JanusGraph internal

Hi, There are three solution directions: if you have keys to your vertices available, either vertex ids or unique values of some vertex property, you can start as many gremlin clients as your

Hi There, we have Janus-Graph with back-end store Foundation DB and index back-end as Elastic Search. Please let me know what is the best way to export/read Millions of Records from JaunusGraph by

Hi Marc, IMHO, an index should not prevent a query to work. Moreover the result of a query should not depends of backends (storage and index). If an index backend cannot process a predicate, the

I have also encountered this problem, but I have found a reliable way to reproduce. The following query works perfectly in the gremlin console (both server and client from Janusgraph 0.6.0

Hi Toom, See, https://docs.janusgraph.org/index-backend/text-search/#full-text-search_1 Indeed, the negative text predicates are only available to Elasticsearch (and, apparently as you say, to the

Hi, With JanusGraph 0.6.0 and Lucene index backend, queries fail if they contain predicate like textNotPrefix, textNotContains: java.lang.IllegalArgumentException: Relation is not supported for string

Hi Team, We are facing some issues with the Janusgraph 0.5.3, we captured heap dumps and find memory leaks. Can you please check if this is a leak suspect? -- ViVek Raghuwanshi Mobile

Hi Claudio, Paging with range can only work with a vertex centric index, otherwise the vertex table is scanned for every page. If you just want all results, the alternative is to forget about the

Hi Tanroop, Does the problem also occur if you replace v() with V().limit(1) inside your query? If not, at what result size does your issue start to occur? Btw, your post has a typo: "user" and

Hi, I have some performance issue extacting nodes attached to a node with pagination I have a simple graph with CompositeIndex on property name (Please find schema definition in attachments). The

Hi You are suggesting above experiment for isolating the issue right ? I thought about not using the CQL executor service but we are in primary stage have not done any workload tests to figure out the

Hi Tanroop, I have also faced same issue and have posted a query about it on this channel 'GraphTraversal Thread Stuck'. Did you found the root cause of above issue ? Thanks, Sujay Bothe

Hi Pawan, OK, I did a small upgrade session myself and did not encounter any issues (apart from having to set numTokens: 4 in conf/cassandra.yaml). This is what I did: Start from a fresh

I've seen this - https://docs.janusgraph.org/advanced-topics/serializer/ But an example would greatly help (btw, we develop mostly in Python).

Hi! Is there a way to add custom property types to JanusGraph (similar to RelationIdentifier / Geoshape) to be later used by the GraphSON serializer? Ideally without re-building JanusGraph. Due to

Hi Marc, I have also tried with "graph.allow-upgrade=true" and added "storage.cql.request-timeout" as well but am still facing the same issue. Please check the attached janusgraph server log for your

Hi Pawan, It seems I miss the practical experience, but it seems you have to set graph.allow-upgrade=true (although it is not clear whether this applies to all version changes or only to "storage

Hi Marc, Thanks for your reply, But nothing was changed on the cassandra cluster part, Keyspace is already there with graph data and it was working before the janusgraph version upgrade. I don't