# Breaking Changes from 0.90 to 1.1

**URL:** <https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508>\
**Category:** Elasticsearch\
**Created:** [May 14, 2014, 7:59am UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508 "2014-05-14T07:59:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lawrence\_cooke](https://avatars.discourse-cdn.com/v4/letter/l/43a26b/32.png) [@Lawrence\_cooke](https://discuss.elastic.co/u/Lawrence_cooke)\
**Post date:** [May 14, 2014, 7:59am UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508/1 "2014-05-14T07:59:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 14, 2014, 8:02am UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508/2 "2014-05-14T08:02:26Z")

</div>

I think you are referring to that: [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/\_return\_values.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_return_values.html)

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr

Le 14 mai 2014 à 09:59:06, Lawrence cooke ([mrcosgrove1@gmail.com](mailto: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](mailto: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](https://groups.google.com/d/msgid/elasticsearch/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](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](mailto: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](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](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Lawrence\_cooke](https://avatars.discourse-cdn.com/v4/letter/l/43a26b/32.png) [@Lawrence\_cooke](https://discuss.elastic.co/u/Lawrence_cooke)\
**Post date:** [May 14, 2014, 9:56am UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508/3 "2014-05-14T09:56:50Z")

</div>

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](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/_return_values.html)
> 
> --  
> _David Pilato_ | _Technical Advocate_ | _[Elasticsearch.com](http://Elasticsearch.com)_  
> @dadoonet [https://twitter.com/dadoonet](https://twitter.com/dadoonet) | @elasticsearchfr[https://twitter.com/elasticsearchfr](https://twitter.com/elasticsearchfr)
> 
> Le 14 mai 2014 à 09:59:06, Lawrence cooke ([mrcos...@gmail.com](mailto: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](mailto: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.com](https://groups.google.com/d/msgid/elasticsearch/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/54e61954-f480-4a46-b0b6-5523f10d34da%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://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](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](mailto: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](https://groups.google.com/d/msgid/elasticsearch/9b918043-3a60-45fe-886d-171036ccc69e%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![ElasticSearch\_Users\_](https://avatars.discourse-cdn.com/v4/letter/e/b4bc9f/32.png) [@ElasticSearch\_Users\_](https://discuss.elastic.co/u/ElasticSearch_Users_)\
**Post date:** [May 14, 2014, 1:46pm UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508/4 "2014-05-14T13:46:01Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:29am UTC](https://discuss.elastic.co/t/breaking-changes-from-0-90-to-1-1/17508/5 "2017-07-06T01:29:28Z")

</div>


