GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/17
Streams 86
Added in Reentrant read and write locks anytime the provider queue is being
updated or read from. This should ensure that we do not have situations where
data is lost between this provider and any subsequent components down stream
from it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robdouglas/incubator-streams STREAMS-86
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/17.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 #17
----
commit 50a70bcd9504dab60a9b694b3f25f738d09ab595
Author: Robert Douglas <[email protected]>
Date: 2014-05-19T18:33:47Z
STREAMS-86 | Added a Reentrant Read/Write lock to ensure that the provider
queue is only accessed when appropriate. This helps to make sure that we don't
drop data between this provider any any subsequent components
commit 6ccf4e6d8dd83695e65a81dc69bc661ee4840da7
Author: Robert Douglas <[email protected]>
Date: 2014-05-19T18:37:52Z
STREAMS-86 | Added a readlock around offering to the provider queue
commit a08900b6eb753c2bf57c0d7047bda84ca4ebe69f
Author: Robert Douglas <[email protected]>
Date: 2014-05-19T18:40:09Z
STREAMS-86 | Added back in old number of attempts to try (will change in
separate pull request)
commit 34bb2bc7c40ac351ff4f0cad0f80584fe58aff5b
Author: Robert Douglas <[email protected]>
Date: 2014-05-19T18:42:03Z
STREAMS-86 | Added in constructQueue() call in prepare method
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
