[jira] [Resolved] (ASTERIXDB-3250) Ensure writing indexes' empty files to S3

["Ian Maxon (Jira)" <ji...@apache.org>]

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

Ian Maxon resolved ASTERIXDB-3250.
----------------------------------
    Resolution: Fixed

> Ensure writing indexes' empty files to S3
> -----------------------------------------
>
>                 Key: ASTERIXDB-3250
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-3250
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>    Affects Versions: 0.9.9
>            Reporter: Wail Y. Alkowaileet
>            Assignee: Wail Y. Alkowaileet
>            Priority: Major
>              Labels: triaged
>             Fix For: 0.9.9
>
>
> When flushing empty components, empty files are not written to S3 (but written on local disk). When adding a new node (or removing a new node). The following error was observed:
> {noformat}
> Unequal number of trees and filters found in ..../storage/partition_64/Test/MyDataset/0/MyDataset {noformat}
> This happened as the boomfilter size was 0 bytes and not written to S3 during the flush operation.



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