Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/853
I think it's a fair question @ottobackwards. Anything that might affect
how the HBase table is laid out should be worked out now or we're back to
altering tables during upgrades. Currently the row key is the user name, the
column family is hardcoded (although configurable), and the column qualifier is
hardcoded. Would you add the type to the row key or store different client
settings in different columns?
We could add versioning but that is not trivial and will increase the scope
of this PR. I can take it on here if we decide we want it but this PR is
already large. Follow on maybe? Either way works for me. If we decide a
follow on is better I would make an effort to do it right away before we do a
release.
Jackson is the standard in Metron for serialization/deserialization. I
think we should have a very compelling reason to introduce something new.
Happy to discuss.
---
