Right now, it's very difficult to spin up a cluster in Frankfurt
(eu-central-1) because the released versions of the AWS plugin don't
support the region yet. I assume that when version 1.5.0 of Elasticsearch
is released, the plugin will get a version bump as well -- but when is that
going to be?
I think the best thing about open source is, you can clone the github repo
branch es-1.4 of the plugin and build a snapshot version 2.4.2-SNAPSHOT for
yourself.
Last commit on es-1.4 was adding eu-central-1 so it should work then:
This does not mean a release wouldn't be a good idea
Right now, it's very difficult to spin up a cluster in Frankfurt
(eu-central-1) because the released versions of the AWS plugin don't
support the region yet. I assume that when version 1.5.0 of Elasticsearch
is released, the plugin will get a version bump as well -- but when is that
going to be?
What's the difference between the es-1.4 and es-1.x branches? es-1.4 stops
updating once Elasticsearch 1.5 is released?
On Wednesday, January 21, 2015 at 4:00:54 PM UTC-5, Jörg Prante wrote:
I think the best thing about open source is, you can clone the github repo
branch es-1.4 of the plugin and build a snapshot version 2.4.2-SNAPSHOT for
yourself.
Last commit on es-1.4 was adding eu-central-1 so it should work then:
Right now, it's very difficult to spin up a cluster in Frankfurt
(eu-central-1) because the released versions of the AWS plugin don't
support the region yet. I assume that when version 1.5.0 of Elasticsearch
is released, the plugin will get a version bump as well -- but when is that
going to be?
What's the difference between the es-1.4 and es-1.x branches? es-1.4 stops
updating once Elasticsearch 1.5 is released?
On Wednesday, January 21, 2015 at 4:00:54 PM UTC-5, Jörg Prante wrote:
I think the best thing about open source is, you can clone the github
repo branch es-1.4 of the plugin and build a snapshot version 2.4.2-SNAPSHOT
for yourself.
Last commit on es-1.4 was adding eu-central-1 so it should work then:
I'm curious what the release cycle for Elasticsearch and the
es-cloud-aws plugin are. https://github.com/elasticsearch/elasticsearch-
cloud-aws/issues/165 lays out why, but I'll include it here for
completeness:
Right now, it's very difficult to spin up a cluster in Frankfurt
(eu-central-1) because the released versions of the AWS plugin don't
support the region yet. I assume that when version 1.5.0 of Elasticsearch
is released, the plugin will get a version bump as well -- but when is that
going to be?
I'm not wild about the idea of running snapshot code in production... but
that would probably work.
On Thursday, January 22, 2015 at 1:10:30 PM UTC-5, Jörg Prante wrote:
Yes, 1.5 will become a new branch with the status of 1.x once it is
released, and 1.x will then become the base for further 1.x releases (if
any)
Jörg
On Thu, Jan 22, 2015 at 5:50 PM, David Ashby <delta.m...@gmail.com
<javascript:>> wrote:
What's the difference between the es-1.4 and es-1.x branches? es-1.4
stops updating once Elasticsearch 1.5 is released?
On Wednesday, January 21, 2015 at 4:00:54 PM UTC-5, Jörg Prante wrote:
I think the best thing about open source is, you can clone the github
repo branch es-1.4 of the plugin and build a snapshot version 2.4.2-SNAPSHOT
for yourself.
Last commit on es-1.4 was adding eu-central-1 so it should work then:
I'm curious what the release cycle for Elasticsearch and the
es-cloud-aws plugin are. https://github.com/
elasticsearch/elasticsearch-cloud-aws/issues/165 lays out why, but
I'll include it here for completeness:
Right now, it's very difficult to spin up a cluster in Frankfurt
(eu-central-1) because the released versions of the AWS plugin don't
support the region yet. I assume that when version 1.5.0 of Elasticsearch
is released, the plugin will get a version bump as well -- but when is that
going to be?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.
