Behavior of missing filter in 1.3.2

Hi,

I am trying to determine what the behavior of the missing filter should be.
I have a one-node instance of ES 1.3.2 running on centos 6.

I add the following simple document to an index:

{
"testField": "",
"testField2": ""
}

And ran the following query:
{
"query" : { "filtered" : {"filter": {
"missing": {
"field": "testField"
} } } }
}

At first, running under JDK 1.7.0_60, I was not able to retrieve the
document. When I upgraded to JDK 1.7.0_67, I was able to retrieve the
document with the query above. This is repeatable when I backlevel the jdk
I am not able to find the document. I am aware of the open issue affecting
the missing filter
at https://github.com/elasticsearch/elasticsearch/issues/7348 but should I
rely on the missing filter working with null strings under JDK 1.7.0_67?

-drew

--
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/9856e5a0-130c-4463-9fdd-03e7764712a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.