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-35) There is no Reader / Writer for S3
Date Fri, 25 Apr 2014 20:49:16 GMT

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

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

Github user smashew commented on the pull request:

    https://github.com/apache/incubator-streams/pull/3#issuecomment-41437666
  
    Matt, I am terribly sorry, you'll have to forgive me... I am very new to Apache and greatly
appreciate your time and attention to these changes. This came from an internal forked repo...
    
    Here are all the issues that this resolves, I can't assign them to myself in Apache's
Jira,
    
    https://issues.apache.org/jira/browse/STREAMS-35?jql=project%20%3D%20STREAMS
    https://issues.apache.org/jira/browse/STREAMS-36?jql=project%20%3D%20STREAMS
    https://issues.apache.org/jira/browse/STREAMS-37?jql=project%20%3D%20STREAMS
    https://issues.apache.org/jira/browse/STREAMS-38?jql=project%20%3D%20STREAMS
    



> There is no Reader / Writer for S3
> ----------------------------------
>
>                 Key: STREAMS-35
>                 URL: https://issues.apache.org/jira/browse/STREAMS-35
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Matthew Hager
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Need to create a reader / writer for S3



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message