Breaking Changes from 0.90 to 1.1


(Lawrence cooke) #1

Hi,

I have been using 0.90 and have just updated to 1.1.

Problem I am having is that the data in 1.1 seems to be formatted
differently than 0.90

In 0.90 the json raw data looks like:

"field":data

however in 1.1 the data seems to be sorting it:
"field":{data}

This means that in my code anywhere I was referring to
$results['fields']['fieldname']

needs to be $results['fields][fieldname][0]

If this an option that can be changed, or is this a new way that
elasticsearch is storing data.(with all fields being an array instead of
standard string?

Thanks!

--
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/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #2

I think you are referring to that: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_return_values.html

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 14 mai 2014 à 09:59:06, Lawrence cooke (mrcosgrove1@gmail.com) a écrit:

Hi,

I have been using 0.90 and have just updated to 1.1.

Problem I am having is that the data in 1.1 seems to be formatted differently than 0.90

In 0.90 the json raw data looks like:

"field":data

however in 1.1 the data seems to be sorting it:
"field":{data}

This means that in my code anywhere I was referring to $results['fields']['fieldname']

needs to be $results['fields][fieldname][0]

If this an option that can be changed, or is this a new way that elasticsearch is storing data.(with all fields being an array instead of standard string?

Thanks!

--
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/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.com.
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/etPan.53732313.643c9869.dcd2%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.


(Lawrence cooke) #3

Thanks for your reply,

does the flat_settings work on query results, it does not seem that it does
from the way its written, but was hoping there was an option to choose to
return query results flattened.

On Wednesday, May 14, 2014 6:02:26 PM UTC+10, David Pilato wrote:

I think you are referring to that:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_return_values.html

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr

Le 14 mai 2014 à 09:59:06, Lawrence cooke (mrcos...@gmail.com<javascript:>)
a écrit:

Hi,

I have been using 0.90 and have just updated to 1.1.

Problem I am having is that the data in 1.1 seems to be formatted
differently than 0.90

In 0.90 the json raw data looks like:

"field":data

however in 1.1 the data seems to be sorting it:
"field":{data}

This means that in my code anywhere I was referring to
$results['fields']['fieldname']

needs to be $results['fields][fieldname][0]

If this an option that can be changed, or is this a new way that
elasticsearch is storing data.(with all fields being an array instead of
standard string?

Thanks!

--
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/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/54e61954-f480-4a46-b0b6-5523f10d34da%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/9b918043-3a60-45fe-886d-171036ccc69e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(ElasticSearch Users mailing list) #4

Unfortunately no, you'll need to adjust your code to adapt to the breaking
change. If it helps, you could use _source filtering and it will return the
exact format from the JSON document:

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-source-filtering.html#search-request-source-filtering

--
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/2bfb75ef-7172-4603-8dfb-19297e22ff59%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #5