[
https://issues.apache.org/jira/browse/ASTERIXDB-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17398233#comment-17398233
]
ASF subversion and git services commented on ASTERIXDB-2791:
------------------------------------------------------------
Commit 738ec5db3224ac571bfca374e4090b1f9100908a in asterixdb's branch
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=738ec5d ]
[ASTERIXDB-2791][IDX] Use OptionalBoolean for unknown key option
- user model changes: no
- storage format changes: no
- interface changes: no
Change-Id: I1abfa1ce1ac6d3848a684a78c1da992cc2fd6ca1
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/12784
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Ali Alsuliman <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>
> Enable storing nulls in secondary indexes
> -----------------------------------------
>
> Key: ASTERIXDB-2791
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2791
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: IDX - Indexes, STO - Storage
> Affects Versions: 0.9.5
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Fix For: 0.9.7
>
>
> Currently, nulls and missings keys are not stored in secondary indexes. This
> applies across all index types. For B-Tree indexes, it should be possible to
> accept nulls and missings keys (for example, to enable using secondary
> indexes for prefix searches). For other index types, they should determine
> how to deal with UNKNOWNs in a proper way.
> * Make sure array indexes handle NULLs/MISSINGs
> * Make sure inverted indexes handle NULLs/MISSINGs
> * Make sure R-Tree indexes handle NULLs/MISSINGs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
