[
https://issues.apache.org/jira/browse/STREAMS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248849#comment-14248849
]
ASF GitHub Bot commented on STREAMS-243:
----------------------------------------
GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/167
STREAMS-243 | Updated S3Configurator to throw a more descriptive excepti...
...on when the s3config can not be read
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robdouglas/incubator-streams STREAMS-243
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/167.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 #167
----
commit 639bd3a696431db65b62f92b773c9e5a64c2d63b
Author: Robert Douglas <[email protected]>
Date: 2014-12-16T20:22:21Z
STREAMS-243 | Updated S3Configurator to throw a more descriptive exception
when the s3config can not be read
----
> S3 Persist Writer does not flush or shutdown on stream shutdown
> ---------------------------------------------------------------
>
> Key: STREAMS-243
> URL: https://issues.apache.org/jira/browse/STREAMS-243
> Project: Streams
> Issue Type: Bug
> Reporter: Steve Blackmon
>
> S3 Persist Writer does not seem to flush or shutdown on stream shutdown,
> which has the side-effect of not allowing the stream process to close.
> When cleanUp() is called, the writer should flush and terminate gracefully.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
