Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/2556
@HeartSaVioR @arunmahadevan
I tested this manually against HBase 2.0.0 beta-1 and HBase 1.1.2 using the
examples as well as some custom code covering trident and core storm
read/write. All
Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/2556
@arunmahadevan Yes, I will share the results of my testing and will test
for backward compatibility.
I don't have high hopes for backward compatibility based on
Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/2556
@ptgoetz the changes looks good.
1. Can you share the results of testing these changes with HBase 2.0
2. Are these changes compatible with HBase 1.x ? Can we try running the
Github user agresch commented on the issue:
https://github.com/apache/storm/pull/2556
What is the expectation for Storm users using different versions of HBase?
Should we have some shim layer to allow using any version?
---
Github user ptgoetz commented on the issue:
https://github.com/apache/storm/pull/2556
> Did you test the patch manually with HBase 2.0 beta 1?
Not extensively. The point on this JIRA/PR is to raise awareness that we
should look at targeting new ecosystem versions. This holds
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2556
I'm expecting that the patch is just for the update of API change, hence
questions look more important than the code change.
Several questions:
1. Did you test the patch manually
