Hi all,
I'm getting some strange behavior from the ES server when using a term
query + a geo distance filter + a sort. I've tried this with 1.3.2,
1.3.5, as well as 1.4.0. All exhibit this same behavior. I'm using the
Java transport client. Here is my SearchRequestBuilder payload in
I just noticed I had a typo in my query, this is the query payload I'm
executing if I run it in HTTP (which works)
{
from : 0,
size : 10,
query : {
term : {
ug_context :
c2d2d78a-69cc-11e4-b22e-81db7b9aa660__user__zzzconnzzzlikes
}
},
Looks like a bug in org.apache.usergrid.persistence.index.impl.
EsEntityIndexImpl
Check if the types are set to a non-null value in the SearchRequest. If
you force them to be a null value, SearchRequest will throw the NPE you
posted.
Jörg
On Tue, Nov 11, 2014 at 6:11 PM, Todd Nine
You're right Jorg. There was an issue where types was incorrectly set to
null because more than 1 was specified. As a result, it passed the check
for at least 1 element in the array, even though the type itself in element
0 was null. Thank you for your help!
On Tuesday, November 11, 2014
