It would only affect the use of JanusGraph+Elastic if you were offering it in an -as-a-Service (-aaS) offering, like a commercial DBaaS. In which case the SSPL would require you to commit back to the

Sounds normal to me. Note that setting query.batch=true might help a bit. Also note that the graph structure, in particular the number of repeat steps, is important. Finally, note that caching in the

If I am understanding correctly, this does not affect the usage of Elasticsearch in JanusGraph. Regarding AWS's decision, seems no additional configs/code changes are needed if someone wants to use

Hi All, I have a multi-level graph with total 800 vertices. When I run g.V(<id of parent>).repeat(out()).emit() for first time, it takes 300ms. In profile(), I could see RepeatStep takes most of the

Please also read the stance of Elasticsearch itself (because the AWS article did not link to it ): https://www.elastic.co/blog/license-change-clarification

Hi all, Since ES seems to have changed their licensing, what does this entail about the future usage of ES as a JanusGraph index

Analytical queries require a full table scan. Some people succeed in speeding up analytical queries on JanusGraph using OLAP, check the older questions on OLAP and SparkGraphComputer

Hi, I have used https://github.com/IBM/expressive-reasoning-graph-store project to import the turtle file having around 4 Lakhs of concepts ad this project is using Janusgraph 0.4.0. Now after

Hi Vinayak, JanusGraph has defined hadoop InputFormats for its storage backends to do OLAP queries, see https://docs.janusgraph.org/advanced-topics/hadoop/ However, these InputFormats have several

The path of the BulkLoaderVertexProgram might be doable, but I cannot help you on that one. In the stack trace above, the yarn appmaster from spark-yarn apparently tries to communicate with HBase but

I mean, what happens if you try to run MapReduceIndexManagement on BigTable. Apparently, you get this error message "MapReduceIndexManagement is not supported for BigTable" but I would like to see the

Hi All, I am working on OLAP using Spark and Hadoop. I have a couple of questions. 1. How to execute a filter step on the driver and create an RDD of internal ids? 2. Distributing the collected Ids to

Thanks Nicolas, I am able to reproduce it using your configs & script. Created an issue at https://github.com/JanusGraph/janusgraph/issues/2369 Looks like a bug with calculating cache entries' size.

Thank you for response! I am using BulkLoaderVertexProgram from console. Sometimes it works correctly. This error still exist when i am running read from hbase spark job. my

Thanks a lot for your reply. I don't get any error message. The REINDEX step is very slow (2000/s) for the mixed index and fails after running for a few days. Everytime indexing fails or the cluster

#Private reply from OP: Yes, i am running bulk load from hdfs(graphson) in janusgraph-hbase. Yes, i have graphson part files from spark job with a structure like grateful-dead.json example. But if

Thanks for reposting your issue on the janusgraph-users list! Can you please show the entire stack trace leading to your error message? Note that your issue might be related

we have imported around 4 billion vertices in janus graph. We are using big table and elastic search reindexing speed is very slow..around 2000 records per second is there any way to speed it

Hi OK, do I understand right that you want to bulk load data from hdfs into janusgraph-hbase? Nothing wrong with that requirement, I do not know how to ask this in a more friendly way! Is your input

Hi! I have this configuration janusgraph: 0.5.2 spark 2.4.0 hbase 2.1.5 hadoop 2.7.7 I have 3 nodes hadoop on my cluster. I am set up janusgraph with hadoop infrastructure and run load data and read