Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/622
> Your proposal has the advantage of making data in HBase self-identifying
(if one has the key), which I always like. However, it's a large change and
induces yet more complexity
What do you find unnecessarily complex here? The code base was already
designed to accept different row key implementations. So this change involves
the following.
1. The new decodable row key
2. Profiler client logic to instantiate row key builders
3. Profiler client logic to pass parameters to the instantiated row key
builders
I would agree that I think item 3 is unnecessarily complex. That's where I
wanted feedback. I think just passing parameters through an interface method
would simplify this a lot.
---
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.
---
