Hey Ryan It would be really great if you could guide me along these lines you mentioned above. I would be available if you need any more information. Saurabh Verma PE *DISCLAIMER - This email

Missed your response about the different cluster. That’s the underlying issue then. Because of the way Scylla works, you’ll need to make sure that the cluster on which the restore occurs has the

Hey Ryan I backed up data on each node of “cluster1”, and then restored data on each node of “cluster2” Thanks -- Thanks & Regards, Saurabh Verma, India

So you backed up data on each node of “cluster1”, and then restored data on each node of “cluster1”? -- Ryan Stauffer Founder, Enharmonic, Inc. enharmonic.ai 415-684-3855

Very good! Thank you all. We agreed to have next release managers: Chris - version 0.2.3 Oleksandr - version 0.3.2 Florian - version 0.4.0

Hey Ryan Point 2, I missed the question around same scylla cluster, I am moving it to a different scylla cluster the IPs are changed. Does that matter? Thanks Saurabh Verma PE *DISCLAIMER - This

Hi Ryan Thanks for the response. Below answers to your questions:- 1. Are you backing up and restoring the same keyspace on the same Scylla cluster, or is one of those variables changing? - The

I can definitely take over one release and both the order and also the assignment of release managers you proposed, Oleksandr, sound good to me! Am Donnerstag, 11. April 2019 16:40:02 UTC+2 schrieb

I actually had the same order in mind. I'm hoping to finish up the testing on my open service wrapper PR next week and then work on noarch rpm and Deb packages to add to the releases. If we all agree

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