[
https://issues.apache.org/jira/browse/STREAMS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582713#comment-15582713
]
ASF GitHub Bot commented on STREAMS-412:
----------------------------------------
GitHub user steveblackmon opened a pull request:
https://github.com/apache/incubator-streams/pull/301
level up rss provider
add main methods to each Provider (STREAMS-412)
add real integration tests (STREAMS-415)
fix a failing test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/steveblackmon/incubator-streams 0.4-rss
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/301.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 #301
----
commit 427faf5378b3de99df81604dd4ec856c89766224
Author: Steve Blackmon @steveblackmon <[email protected]>
Date: 2016-10-17T16:44:20Z
level up rss provider
add main methods to each Provider (STREAMS-412)
add real integration tests (STREAMS-415)
fix a failing test
----
> ability (and instructions on how) to run processors directly from console
> -------------------------------------------------------------------------
>
> Key: STREAMS-412
> URL: https://issues.apache.org/jira/browse/STREAMS-412
> Project: Streams
> Issue Type: Improvement
> Reporter: Steve Blackmon
>
> All of the processors currently require attachment to a run-time to use.
> If processors could be configured and executed directly from the console,
> they would become more valuable for casual use cases where users just want to
> easily transform documents without writing or deploying custom code.
> This would probably take the form of adding a main method and perhaps a
> Runnable trait to each processor, that when launched resolves the appropriate
> typesafe config, starts up the process, and transforms documents from STDIN
> writing them to STDOUT until the input stops.
> Instructions how to do this should also be added to the javadocs of the
> processors and/or the markdowns of each module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
