-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Trident API and other topologies #46
Comments
Yes absolutely, I will make a release for 0.8.0 and plan to support Trident. AFAIK LinearDRPCTopology and transactional topologies are being deprecated so I do not think it's worth spending time on it at this point, unless there is a request for it (I am not using them myself...). ACTUALLY, (... checking issues ...) there is a request for LinearDRPCTopology in issue #42 and I opened issue #41 for transactional topologies. doh. So, I might do #42. Thanks for testing the 0.8.0 upgrade! Good to know its working well! |
Great that you plan to support 0.8.0 with redstorm. I know this is a tough one but do you have a vague timeline when you might work on it and release it? |
👍 for Trident support! |
I am leaving for vacations tonight :D so I'll work on it at the end of August. |
another 👍 for Trident support! :) |
getting there, see issue #50 |
bump |
any news on this? |
unfortunately not much but will reserve some time on this in the next few weeks. |
I just pushed 0.7.0.beta1 which includes Trident examples in Let me know what you think! |
Looks good! |
Yes it will shortly. Just need to create the Java proxies for all the |
Ok :) |
It'd be great to see example spec tests for a Trident topology, either here (testing examples/trident/word_count_topology) or in the redstorm-starter project. |
Is there anything planned regarding the support of the newly introduced Trident API (Storm 0.8) as well as the other existing topologies?
I just updated the storm dependency of redstorm to storm 0.8.0 for my own testing and it seems that the existing redstorm samples work flawlessly.
The text was updated successfully, but these errors were encountered: