Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/513
Thats a great point about leveraging any changes they make to the Bytes
class... I'm now thinking, what if we added simple methods to the
HBaseClientService interface [1] that wrapped the calls to Bytes?
Something like:
`byte[] toBytes(boolean b)
byte[] toBytes(long l)
byte[] toBytes(double d)
byte[] toBytes(String s)
`
Then HBase_1_1_2_ClientService would implement those methods and use the
Bytes class from 1.1.2, and if someone implemented a 0.94 version it would be
up to them to use the Bytes class from 0.94 or whatever they wanted to do. The
processors never know they are dealing with the Bytes class.
[1]
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-standard-services/nifi-hbase-client-service-api/src/main/java/org/apache/nifi/hbase/HBaseClientService.java
---
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.
---
