I've tested it with ES 1.1 and the described behaviour is gone. So the Java API does a correct interpretation of the JSON search result.
On Thursday, January 30, 2014 11:23:04 PM UTC+1, Martin Pape wrote: > > Thanks for the information. I still have some months till production, so > might workaround now and wait for ES 1.0. Anyone know then ES 1.0 is > planned to be release? > > BR - Martin > > On Thursday, January 30, 2014 6:54:58 PM UTC+1, Binh Ly wrote: >> >> Martin, I have verified this behavior and it still pesists in 0.90.10. I >> checked the latest ES master build at it indeed returns 2 values in the >> List as expected so I am expecting it to behave as you expect in ES 1.0. >> For now, what it does is it returns a single item inside the List, but that >> item is in turn an ArrayList of 2 String values. If you have only 1 value, >> it returns a single item in the List, and that item is a String. So you can >> test accordingly in code to check if the value is a String or an ArrayList >> and then adjust accordingly. Should be rectified in 1.0 I hope. :) >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5bc24d1a-d696-4bc5-97bd-86f6780cd4f4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
