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

ASF subversion and git services commented on ASTERIXDB-3252:
------------------------------------------------------------

Commit bc62a6fa458b47fb9f694e3c77bb8b3dce76bea5 in asterixdb's branch 
refs/heads/master from Shahrzad Shirazi
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=bc62a6fa45 ]

[ASTERIXDB-3252][IDX] Fix index-only w/ UNKNOWN entries

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
In order to create the correct result for index-only queries when the secondary 
index includes
UNKNOWNs , output types generated by the B-tree secondary-index search should be
 nullable/missable
Change-Id: I2e2163755e396678eec87771d70978e6134a9232
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17748
Integration-Tests: Jenkins <[email protected]>
Tested-by: Ali Alsuliman <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>


> Not assigning the right data type to the result of B-tree index search
> ----------------------------------------------------------------------
>
>                 Key: ASTERIXDB-3252
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3252
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: COMP - Compiler
>            Reporter: shahrzad shirazi
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> Index only plans creates wrong result when we have a composite secondary key 
> and we are including  null and missing.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to