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

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

GitHub user steveblackmon opened a pull request:

    https://github.com/apache/incubator-streams/pull/85

    added support for file: and hdfs: schemes

    reader and writer are not internally consistent - removing timestamp read 
from wrong field for testing
    "scheme": "file" works :)
    will submit another PR for STREAMS-167 which will allow timestamps and 
metadata reading from a previously written hdfs stream.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/incubator-streams STREAMS-173

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-streams/pull/85.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #85
    
----
commit 6016a7740ae52b14ed15647efa530c365d789e8d
Author: sblackmon <[email protected]>
Date:   2014-09-14T02:56:42Z

    added support for file: and hdfs: schemes
    reader and writer are not internally consistent - removing timestamp read 
from wrong field for testing
    "scheme": "file" works :)
    will submit another PR for STREAMS-167 which will allow timestamps and 
metadata reading from a previously written hdfs stream.

----


> TwitterConfigurator doesn't properly create TwitterUserInfoConfiguration from 
> hocon
> -----------------------------------------------------------------------------------
>
>                 Key: STREAMS-167
>                 URL: https://issues.apache.org/jira/browse/STREAMS-167
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>
> Found this trying to run streams-examples/twitter-history-elasticsearch with 
> the suggested configuration file.  The fix is pretty simple, replace this old 
> code with a better config serialization mechanism.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to