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

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

Commit da4eda85bef1bd7e8311890490c5c9c53a0a875f in asterixdb's branch 
refs/heads/master from Wail Alkowaileet
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=da4eda85be ]

[MULTIPLE ISSUES] Fixes for columnar datasets

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

Details:
This patch introduces multiple changes/fixes::
- ASTERIXDB-3194: Write DatasetFormat for row datasets
  in Metadata.Dataset
- ASTERIXDB-3193: Fix bug in Pushdown rule when multi-part
  dataverse names are used
- ASTERIXDB-3192: Fix handling empty components of
  columnar datasets
- ASTERIXDB-3191: Change type of FreeSpaceTolerance to
  double (instead of float)

Metadata changes:
- DatasetFormat will appear for both row
  and columnar datasets
- FreeSpaceTolerance in Metadata.Dataset will
  be displayed differently
  - before: 0.15000000596046448
  - after: 0.15

Change-Id: I3cad84ea748eedc8b376c6701dbc4e8fa911b733
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17542
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Reviewed-by: Wail Alkowaileet <[email protected]>
Reviewed-by: Murtadha Hubail <[email protected]>


> Columnar datasets fails when queried empty flushed components
> -------------------------------------------------------------
>
>                 Key: ASTERIXDB-3192
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3192
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>    Affects Versions: 0.9.9
>            Reporter: Wail Y. Alkowaileet
>            Assignee: Wail Y. Alkowaileet
>            Priority: Critical
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> If (for some reason) a flushed component of a columnar dataset is empty, a 
> query against such a dataset would fail with internal error:
> {code:java}
> java.lang.IndexOutOfBoundsException: 0 >= 0 {code}



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

Reply via email to