[jira] [Commented] (ASTERIXDB-2372) Providing a float value predicate to an integer primary index does not work as expected.

["Xikui Wang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463198#comment-16463198 ] 

Xikui Wang commented on ASTERIXDB-2372:
---------------------------------------

I'm trying to work on this problem and have an issue with the non-force index. In the case where we have a non-enforced index with different types, let's say the record is double and the index is int64, return NULL will cause an empty result. An example is a query in the test case `btree-index-04`. Any thoughts on this?

> Providing a float value predicate to an integer primary index does not work as expected.
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-2372
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2372
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Taewoo Kim
>            Assignee: Taewoo Kim
>            Priority: Critical
>
> If we have an integer primary index and feed a float value predicate that is not an integer such as 1.3, the search result is not correct.
>  
> The DDL and DML
> {code:java}
> drop dataverse test if exists;
> create dataverse test;
> use test;
> create type MyRecord as closed {
>   id: int64
> };
> create dataset MyData(MyRecord) primary key id;
> insert into MyData({"id":1});
> insert into MyData({"id":2});
> select * from MyData where id = 1.3;{code}
>  
> The result should be empty. But, it returns 1 and 2 as the result.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)