streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STREAMS-166) S3PersistReader does not correctly handle directory listing
Date Sat, 20 Sep 2014 22:18:34 GMT

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

ASF GitHub Bot commented on STREAMS-166:
----------------------------------------

Github user renato2099 commented on the pull request:

    https://github.com/apache/incubator-streams/pull/80#issuecomment-56282179
  
    @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.


> S3PersistReader does not correctly handle directory listing
> -----------------------------------------------------------
>
>                 Key: STREAMS-166
>                 URL: https://issues.apache.org/jira/browse/STREAMS-166
>             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
(v6.3.4#6332)

Mime
View raw message