streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STREAMS-166) S3PersistReader does not correctly handle directory listing
Date Sun, 21 Sep 2014 02:32:33 GMT


ASF GitHub Bot commented on STREAMS-166:

Github user smashew commented on the pull request:
    It is per listing you get back... I think. It turns out to be the same $$$ either way
    Sent from my iPhone
    > On Sep 20, 2014, at 5:17 PM, Renato Marroquin <> wrote:
    > @smashew I see, this totally makes sense then. But then it the cost is 1cent per
1000, then wouldn't it be better to use 1000?
    > I do understand your point, having too many configurations make it more difficult,
but I don't think that having to recompile the code for a specific use case makes it less
difficult. IMHO we should use a default value like 500 and if the user wants to change it,
then he should be able to do it using the config files.
    > —
    > Reply to this email directly or view it on GitHub.

> S3PersistReader does not correctly handle directory listing
> -----------------------------------------------------------
>                 Key: STREAMS-166
>                 URL:
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Robert Douglas
>   Original Estimate: 3h
>  Remaining Estimate: 3h
> In its current form, the S3PeristReader is not able to pick up on files inside of a given
directory. In addition to checking for common prefixes, we need to ensure there are no object
summaries in the listing response before we assume we are dealing with a single file.

This message was sent by Atlassian JIRA

View raw message