Upgrading from 0.90.7 to 1.4. Gotchas?

Are there any precautions to take before upgrading from 0.9 to 1.4?

Different data types?
Different API calls?
etc...

And, what is the best way to upgrade? Can we just add a node at the newer
version and let it pull the data?

Thanks.

http://yves.zioup.com
gpg: 4096R/32B0F416

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I would be interested too, we are using the same 0.90.7 version.

Jason

On Thu, Nov 20, 2014 at 2:03 PM, Yves Dorfsman yves@zioup.com wrote:

Are there any precautions to take before upgrading from 0.9 to 1.4?

Different data types?
Different API calls?
etc...

And, what is the best way to upgrade? Can we just add a node at the newer
version and let it pull the data?

Thanks.

http://yves.zioup.com
gpg: 4096R/32B0F416

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHO4itzYRinoR1-qW2FRXQT6bxTpuPADoW6zTsJ%3DgKLoGmZBKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

I can't remember what 0.90.x was unlike as that was long ago for us, but we
recently upgraded from 1.1.0 to 1.4.0.

Look
at http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/breaking-changes.html

additionally pay attention to:

  • scripting:
    • replacement of mvel w/ groovy and disabling dynamic scripting by
      default. We elected to install the mvel plugin manually and change our
      scripts to identify that they are mvel (lang=mvel) and make some minor
      adjustments to make compatible (such as use of _score instead of doc.score
      in scripts). We will do the upgrade to groovy from mvel separately to take
      care of security concerns w/ mvel.
  • lot of percolator changes in 1.x
  • multi field changes in 1.0.0
  • disk space allocation decider configuration format changed in 1.x
    sometime (if you're configuring that)
  • enabled CORS if you're using HEAD (see
    https://github.com/mobz/elasticsearch-head/issues/170)

In general, I would go through release notes
at http://www.elasticsearch.org/downloads/ and look under breaking changes
for every version since your last version.

On Thursday, November 20, 2014 7:47:04 AM UTC-5, Jason Wee wrote:

I would be interested too, we are using the same 0.90.7 version.

Jason

On Thu, Nov 20, 2014 at 2:03 PM, Yves Dorfsman <yv...@zioup.com
<javascript:>> wrote:

Are there any precautions to take before upgrading from 0.9 to 1.4?

Different data types?
Different API calls?
etc...

And, what is the best way to upgrade? Can we just add a node at the newer
version and let it pull the data?

Thanks.

http://yves.zioup.com
gpg: 4096R/32B0F416

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5070f24d-92d6-42ba-a447-4dd759c59fb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

The most surprising part of my upgrade from 0.90 to 1.0.1 was the drop of
indexing performance. So, yes, I’m also interested to know any gotchas.
2014年11月20日 下午8:47于 "Jason Wee" peichieh@gmail.com写道:

I would be interested too, we are using the same 0.90.7 version.

Jason

On Thu, Nov 20, 2014 at 2:03 PM, Yves Dorfsman yves@zioup.com wrote:

Are there any precautions to take before upgrading from 0.9 to 1.4?

Different data types?
Different API calls?
etc...

And, what is the best way to upgrade? Can we just add a node at the newer
version and let it pull the data?

Thanks.

http://yves.zioup.com
gpg: 4096R/32B0F416

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/3c6b6789-de98-40d4-9532-ae78b5465c4a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAHO4itzYRinoR1-qW2FRXQT6bxTpuPADoW6zTsJ%3DgKLoGmZBKA%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAHO4itzYRinoR1-qW2FRXQT6bxTpuPADoW6zTsJ%3DgKLoGmZBKA%40mail.gmail.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAP0hgQ1W5Rw0QqYtiGExJZUNSJ8QsOAxmxYSDgk-6b_zK%3DkmJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Also, forgot to mention... if you have native scripts, they will
mysteriously throw Unsupported Operation exception whenever invoked. Looks
like they made a mistake in 1.4.0 (that is now reverted on master), that
requires you to override the setScorer in native scripts. It's ok, I just
wish they documented in breaking changes.

On Thursday, November 20, 2014 1:03:17 AM UTC-5, Yves Dorfsman wrote:

Are there any precautions to take before upgrading from 0.9 to 1.4?

Different data types?
Different API calls?
etc...

And, what is the best way to upgrade? Can we just add a node at the newer
version and let it pull the data?

Thanks.

http://yves.zioup.com
gpg: 4096R/32B0F416

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/743f6571-af44-40cc-a1c8-f9474cae4773%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.