Hi Eliz, You are supposed to use Tinkerpop's gryo writer to create kryo graph input files (I do not believe there is a formal spec of the format). There is also the BulkDumperVertexProgram to create a

Hi Biko and Marc, Below is the method I used to create test.kryo, which was converted from a CSV file: vertices.txt vi vertices.txt 123

Please refer to the documentation here: http://docs.janusgraph.org/latest/advanced-schema.html Thanks, Jerry

Thank you Jean-Baptiste. Actually I was using gremlin (not, graph-client). In the schema definition, I have something like that // load configuration from file conf = new

With so many high-profile companies and others out there with Titan/Janus in production, I can only imagine that most, if not all, have written some higher-level tools for managing the database and,

Just set the timeout before call() mgmt.awaitGraphIndexStatus(graph, 'VbyName').timeout(1, java.time.temporal.ChronoUnit.SECONDS).call() Robert Dale

You are right, it does work! I was not reading the awaitGrahpIndexStatus results correctly. This ofcourse leads me to the question: why does it take one minute to create/enable an index (even on an

Are you saying that this doesn't work for you? gremlin> graph = JanusGraphFactory.open('inmemory') ==>standardjanusgraph[inmemory:[127.0.0.1]] gremlin> g =

Hi, Curious: when an edge is deleted based on TTL, are the nodes that are connected only to those edges also deleted? Or do I need to specify TTL for nodes as well? Same question

I tried the explicit waiting and enabling of the index but the result is the same. I tried looking in the JanusGraph source code but I am struggling to understand the project structure and cannot find

Oh, I see. I had the wrong expectation. Looks like the index doesn't go to registered. I have found it to be a good practice to always wait for the index to be available and then explicitly enable

Thanks but I do not think they overlap. I added some explicit 'tx().rollback()' before 'openManagement()' but the result is the same.

Be sure to not overlap graph and mgmt transactions. Every time you start a traversal with 'g.' or mutate the 'graph' a transaction is started. Always commit or rollback the current graph/g

Thanks for your response Jason. I did a little more research and also tried your example (which works). So when I add an index on a property of either a Vertex or an Edge the graph uses the index as

Hi All, I am totally new to Graph Databases. I am using node js package gremlin-javascript with Janusgraph Project. When I execute the node pgm, I get the following error: I am not sure what is

Hi Misha, I think I misused the word "stable" - it is all relative in software in general and large open-source projects in particular. And, of course, it is not all about a nice number like 1.0. I

Hi Nikolai, Can you please define what you mean by "stable release"? Are you looking for a 1.0 release? That's probably not happening for a while — the next release's version will be 0.2.0. That

JanusGraph's documentation [1] shows both ES and Solr have document index TTL. But looking at the code, I only see Solr has it on: private static final IndexFeatures SOLR_FEATURES = new

We are going with titan-1.0.0 for now as (correct me if I am wrong) JG does not have a stable release yet.

Did you create the index before inserting data? Did you make sure to commit the management transaction, i.e. mgmt.commit()? In this example below, you can see a name property getting created and