Hi all, This morning I went through and tagged all the issues and pull requests that I feel belong in the 0.2.3 release. Currently there are only 2 open pull requests targeting the 0.2 branch. I can't

Thank you Chris for sharing the checklist! I am going to vacation in the end of this week, so I think I won't be able to review release artifacts but I think other members will be able to review it.

Hi guys, I just had a short call with Jason about what is required for releases and wanted to share my notes. I'm back from vacation and plan to get the process started this week. JanusGraph Release

Circling back around on this. I'm going to dig into those two branches/features over the next few days Thanks, Ryan

Currently we are using Scroll API for realtime search requests when using ElasticSearch as an index backend. In my experience it often creates more than 500 parallel cursors (sometimes more then 10000

No problem at all, glad it worked out! A good reference as well is the Scylla community slack channel - the engineers on there are very helpful in troubleshooting, and anyone using open source is

Hi Ryan The above method works successfully for JG recovery, thank you so much Ryan for the timely assistance, and sharing this crucial & fundamental information. Thanks a lot once again Saurabh Verma

For terminology, I'm going to call your 2 clusters "source" and "replica". "Source" is the Scylla cluster that you want to backup, and "replica" is the cluster that you want to copy the data to. For

Hi Ryan Please send me the commands whenever possible Thanks a lot -- Saurabh Verma Inline images Principal Engineer 
 m: +917976984604 skype: saurabh.verma-zeotap

Ryan, It would be cool to get some help. A good starting point would be make the graph readonly using a TinkerpopStrategy. This implemenation should be straight forward. My current state on task 3 and

Hi It would be cool to get the documentation ready for the release of version 0.3.2. Therfefore, It would be cool, if some of the JanusGraph folks checks the documentation. Afterwards, We can merge

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