Big picture, my understanding is that you're trying to backup and restore the underlying Scylla keyspace ("idgraph1"), right (procedure described here

Thank you Jason! Waiting for your notes. I also think that we should release 0.2.3 then 0.3.2 then 0.4.0 so that users wouldn't be confused which one is the latest and which one they should use. I

Hi all I am trying to recover a JG cluster backed by scyllaDB using steps at https://groups.google.com/d/msg/aureliusgraphs/WyJpzZ4Wcuw/AW4-1GXRfI0J I am always getting the error as below Could not

All three have been added to the JanusGraph org https://issues.sonatype.org/browse/OSSRH-47679 Splitting up the release management duties sounds good. Do we have volunteer release managers for each

Thanks, Dmitry. Looks like are already several comments for the PR for the review, could start addressing them to help the review. Thanks, Henry

Jan, I really like this overall approach and would love to lend a hand in making it happen. I like the idea of streamlining both schema management and general user access to a JanusGraph instance - I

Hi As a follow up to my talk last week, I would like to start a discussion on this topic about redesign the Schema Management. General idea is to deprecated direct access to JanusGraph server using

If the plan is to split it up I'm more than willing to take one of the releases. My username is chupman.

I could do the next line of releases. But if someone else wants to, then feel free to do so. Jason: Would you say that it makes sense for a single committer to do all three releases or could it make

Hello Jason, Thank you for your response. I could try to be a release manager but I have almost no experience in publishing new releases, so it can be error prone. I published the release only once

I mainly referred to the Python library with my earlier comment regarding the size of the PR. There, it would probably have been possible to first create a smaller PR with just a minimal level of

Releases are done on Sonatype OSS. For reference, here is original conversation and the original ticket for JanusGraph. If a committer is interested in stepping up to be a release manager, you can

Apologies for bumping up this thread again - just wanted to update on one aspect of codacy behaviour which previously was inconclusive. I have just had a confirmation that codacy bot actually DOES

Just pushed a commit to remove/reclassify all TODOs in the code.

Hello, Thanks to all who attended the recent online meetup. We had a lot of folks show up and a ton of great questions. Also, big shout and thank you to Chris, Ryan, Jan, and John for speaking. They

There are multiple problems which I see which are not yet resolved: 1. We don't own the domain `janusgraph.org` that is why we can't recover accounts for Docker Hub and maven nexus (sonatype I

Misha, Jason, Could you please check if "fufler" signed a CLA? If so, could you create a PR to include him into janusgraph-legal repository? Regards, Oleksandr

When i try to reindex a mixed index with hbase backend, It really bothered me with such exception : [07:18:22:139] [ERROR] -

Hi Henry, Thanks for coming back on this. I had a quick look at the todos right now, and I think they basically can all be removed - which I will do early next week when I come back from travelling.

I'm going to go with blocking notifications from codacy and I'll open a good first issue to add the link for blocking to CONTRIBUTING.md. The in-line comments are helpful for review and I think