switch to pyelasticsearch #25

Closed
willkg opened this Issue Mar 28, 2012 · 6 comments

Projects

None yet

2 participants

@willkg
Member
willkg commented Mar 28, 2012

pyes keeps changing in non-trivial ways and the API isn't particularly stable. Additionally, it's pretty intense.

I think we should do one of three things:

  1. fork pyes and stabilize it
  2. switch to pyelasticsearch--probably the fork that the django-haystack folks maintain
  3. bundle the version that the django-haystack folks maintain into elasticutils an in that way maintain our own fork

This is pretty far future stuff. Probably shouldn't spend the time on this until there's a compelling reason to do so. We can hang out on pyes 0.15 for now.

@willkg
Member
willkg commented Jun 23, 2012

SUMO is using pyes 0.16. I vote we peg to that for now and then ditch pyes in the future. Given that, I'm going to bump this out of the milestone and do the pegging in issue #30.

@wraithan
Contributor

Using http://github.com/toastdriven/pyelasticsearch isn't need as jezdez has gotten commit access to http://github.com/rhec/pyelasticsearch and has integrated toastdriven's changes.

@willkg
Member
willkg commented Sep 4, 2012

Erik posted this:

https://github.com/erikrose/pyelasticsearch/compare/votizen#L2R572

That adds some things that help reliability. We definitely want some of that. Hopefully it makes its way to landing. I mention it here because we probably want to use things like auto-retrying and possibly failover.

@willkg
Member
willkg commented Jan 8, 2013

I'm currently working on switching over to pyelasticsearch. Tweaking the summary accordingly and assigning to myself.

@willkg willkg was assigned Jan 8, 2013
@willkg
Member
willkg commented Jan 17, 2013

DONE! YAY!

@willkg willkg closed this Jan 17, 2013
@willkg
Member
willkg commented Jan 17, 2013

Done in pull #92.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment