Elasticsearch 1.0.1 Support?

[randyjensen]

Just tested this with 1.0.1 and everything blew up. Rolled back to 0.90.9 and everything is good again. Any chance support for that is in the works? Or am I missing an easy way to get ROR 1.3 to support ES 1.0.1?

[maruf89]

+1

[sscarduzio]

The internal API has slightly changed, I'm spring-cleaning a bit and I'll release an update for the latest ES (1.2) soon.

[sscarduzio]

Find the plugin build compatible to your version in the download directory in the repo.

E.g. if you have ElasticSearch 1.2.0, use: https://github.com/sscarduzio/elasticsearch-readonlyrest-plugin/blob/master/download/elasticsearch-readonlyrest-v1.3_es-v1.2.0.zip

Tell me how it goes.

[randyjensen]

Just upgraded my local environment to 1.2.0 to test and so far everything looks great.

Thank you!

[sscarduzio]

Glad it works :)
By the way @randyjensen @maruf89 : could you share a bit more information on how you use this plugin and why you chose it?
Also, I'm very open to suggestion for further development: new features? What should change? Should docs be clearer? You have an idea for a new plugin?

[randyjensen]

I found this while looking for a way to secure an ES instance for a client. It was dead simple install and setup.

The docs could be clearer, but only because I was so new to ES at the time. This second time around re-installing it with ES1.2.0, everything made perfect sense and it took seconds to get running.

[maruf89]

I'm building a web service which talks directly to ES as a REST API and am
interested in this because I would like to circumvent talking to the server
to handle all my read-only data requests. I'll give it a shot in the coming
day or 2 and leave some more feedback if anything comes up.

On Mon, Jun 2, 2014 at 4:03 PM, Randy Jensen notifications@github.com
wrote:

I found this while looking for a way to secure an ES instance for a
client. It was dead simple install and setup.

The docs could be clearer, but only because I was so new to ES at the
time. This second time around re-installing it with ES1.2.0, everything
made perfect sense and it took seconds to get running.

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