You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Hussain Towaileb (Jira)" <ji...@apache.org> on 2021/04/07 15:09:00 UTC

[jira] [Commented] (ASTERIXDB-2743) Skip not found keys/fails and continue execution for S3 external datasets

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

Hussain Towaileb commented on ASTERIXDB-2743:
---------------------------------------------

https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/6723

> Skip not found keys/fails and continue execution for S3 external datasets
> -------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-2743
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2743
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>          Components: EXT - External data
>    Affects Versions: 0.9.5
>            Reporter: Hussain Towaileb
>            Assignee: Hussain Towaileb
>            Priority: Major
>             Fix For: 0.9.7
>
>
> When querying an S3 external dataset, it is possible to encounter keys/files that are not found on the S3. A possible example is if while we are querying, the key got deleted before the query reaches that file.
>  
> The current behavior throws an exception if the above happens, this needs to be update to just ignore the file and go to the next one without failing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)