Github user mkoch1 commented on the issue:
https://github.com/apache/storm/pull/1781
Rebase is done, sorry for the delay.
---
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
Github user mkoch1 commented on the issue:
https://github.com/apache/storm/pull/1781
That should do it - the batching option has been removed from MapState, in
favor of parallel processing with existing opaque and transactional logic to
handle consistency. Cassandra batch statements
Github user mkoch1 commented on the issue:
https://github.com/apache/storm/pull/1781
Pls note that mutliPut needs an update - will push commit today or tomorrow.
---
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
GitHub user mkoch1 opened a pull request:
https://github.com/apache/storm/pull/1781
STORM-1369: Add MapState implementation to storm-cassandra.
STORM-1369: Add MapState implementation to storm-cassandra.
https://issues.apache.org/jira/browse/STORM-1369
You can merge
GitHub user mkoch1 opened a pull request:
https://github.com/apache/storm/pull/1782
Feature/storm 1369 (#2)
STORM-1369: Add MapState implementation to storm-cassandra.
https://github.com/apache/storm/pull/1781
You can merge this pull request into a Git repository
Github user mkoch1 commented on the issue:
https://github.com/apache/storm/pull/1781
Did not notice that, sorry. Replaced now with an external resource
implementation. The code is not all that complex so it's not a big deal.
One thing I should point out: I borrowed the base
Github user mkoch1 commented on the issue:
https://github.com/apache/storm/pull/1781
Squashed. I don't really see how this should cause any conflicts though.
The only changes in existing code are a couple of namespace corrections (to
avoid wildcard imports, as suggested earlier
Github user mkoch1 closed the pull request at:
https://github.com/apache/storm/pull/1782
---
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
