Update needed for scalastic supporting Elasticsearch 1.0 GA

Question

Update needed for scalastic supporting Elasticsearch 1.0 GA

rbraley opened this issue 10 years ago · comments

Ryan Braley commented 10 years ago

http://www.elasticsearch.org/blog/1-0-0-released/

Jeroen Rosenberg · Answer 1 · Fri Feb 14 2014 00:50:27 GMT+0800 (China Standard Time)

I'm getting connection errors after upgrading Elasticsearch to 1.0.0

Jeroen Rosenberg · Answer 2 · Wed Apr 02 2014 16:16:08 GMT+0800 (China Standard Time)

Any progress on this?

Benny Sadeh · Answer 3 · Wed Apr 02 2014 17:03:30 GMT+0800 (China Standard Time)

I'm traveling until end of May, so no.
If anyone else wants to do it, just send me a pull request and I'll merge
it.

Benny

On Apr 2, 2014, at 10:16 AM, Jeroen Rosenberg notifications@github.com
wrote:

Any progress on this?

Reply to this email directly or view it on
GitHubhttps://github.com//issues/37#issuecomment-39300139
.

Jeroen Rosenberg · Answer 4 · Wed Apr 02 2014 17:38:13 GMT+0800 (China Standard Time)

Thanks for the update Benny and enjoy the rest of your trip

Martin Smith · Answer 5 · Sun Apr 13 2014 02:14:01 GMT+0800 (China Standard Time)

I'm working on this some in my fork, but I haven't added any of the new Percolate API or the Snapshot API (it's still in place in 1.1 but marked deprecated). I'm trying to get all the tests to run still, so if anyone has any ideas on #40, let me know, and I'll finish and push commits that work with 1.1.

Thanks!

Martin

Jeroen Rosenberg · Answer 6 · Mon Apr 28 2014 18:05:18 GMT+0800 (China Standard Time)

Awesome work @martinb3 I saw you've also fixed #40 now. Are you able to release v1.1 now?

Benny Sadeh · Answer 7 · Mon Apr 28 2014 21:43:39 GMT+0800 (China Standard Time)

Not while traveling

Benny

On Apr 28, 2014, at 1:05 PM, Jeroen Rosenberg notifications@github.com
wrote:

Awesome work @martinb3 https://github.com/martinb3 I saw you've also
fixed #40 #40 now. Are you able
to release v1.1 now?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/37#issuecomment-41541732
.

Jeroen Rosenberg · Answer 8 · Mon Apr 28 2014 21:49:52 GMT+0800 (China Standard Time)

I understand @bsadeh I meant @martinb3's fork

Martin Smith · Answer 9 · Tue Apr 29 2014 20:44:08 GMT+0800 (China Standard Time)

@jeroenr To clarify, I haven't been doing any releases, I was just offering to push 1.1-compatible code that could be released. I've still actually got some code that is failing tests, though. Still working on it :)

Jeroen Rosenberg · Answer 10 · Tue Apr 29 2014 21:09:25 GMT+0800 (China Standard Time)

@martinb3 Thanks Martin, that was indeed what I meant. Whether your code is releasable so you could make a tag or something (that's enough 'released' for now for me)

Martin Smith · Answer 11 · Mon May 05 2014 03:33:41 GMT+0800 (China Standard Time)

@bsadeh I'm still unable to get the cluster recovery tests to pass. The nodes don't seem to want to join each other. The good news is, it fails on the older releases as well, so it's just something in my setup. @jeroenr I've pushed all the code I've adjusted, so you should be good to go to use that fork until there's a release. cheers!

Jeroen Rosenberg · Answer 12 · Mon Jul 14 2014 20:03:42 GMT+0800 (China Standard Time)

Hi guys, it's been a while. Any update on this? FYI, I'm running @martinb3's version for a while now without issues.

Benny Sadeh · Answer 13 · Tue Jul 15 2014 03:51:33 GMT+0800 (China Standard Time)

my apologies guys.
all i can say is that i'm swamped with another project right now and have
no bandwidth for it.
i did try the conversion, and a lot of tests are failing as a result. a
cursory look did not reveal the problem, and it looks like i'll have to dig
into if i'd like to fix it.
but if anyone beats me to it, i'll be happy :-)

On Mon, Jul 14, 2014 at 5:03 AM, Jeroen Rosenberg notifications@github.com
wrote:

Hi guys, it's been a while. Any update on this? FYI, I'm running @martinb3
https://github.com/martinb3's version for a while now without issues.

—
Reply to this email directly or view it on GitHub
#37 (comment).