[jira] [Resolved] (METAMODEL-184) "is null" and "is not null" filter items not evaluated correctly on ElasticSearch

["Kasper Sørensen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/METAMODEL-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kasper Sørensen resolved METAMODEL-184.
---------------------------------------
       Resolution: Fixed
         Assignee: Dennis Du Krøger
    Fix Version/s: 4.4.0

> "is null" and "is not null" filter items not evaluated correctly on ElasticSearch
> ---------------------------------------------------------------------------------
>
>                 Key: METAMODEL-184
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-184
>             Project: Apache MetaModel
>          Issue Type: Bug
>            Reporter: Kasper Sørensen
>            Assignee: Dennis Du Krøger
>             Fix For: 4.4.0
>
>
> We have been made aware of this via this bug report for the DataCleaner application [1].
> What happens is that we create a query "WHERE x IS NULL". What happens is that this criteria is translated into an ElasticSearch TermFilter with a null operand, instead of creating an ExistsFilter which would work a lot better.
> In the case reported in [1] "x" is a date field, but in principle that doesn't matter. It just means that the user gets another error report entirely: That "null" is not a valid date format.
> [1] https://github.com/datacleaner/DataCleaner/issues/610



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)