[
https://issues.apache.org/jira/browse/METRON-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367573#comment-16367573
]
ASF GitHub Bot commented on METRON-1337:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/853
I am not an expert in hbase, I cannot say how i'd implement it.
The version thing we can leave out, it will be just as good or bad as what
we have in zookeeper right?
I think the use case is:
For any given User ( at least ) we need the ability to store currently
known and future unknown configurations as bytes, with configuration type
identifier lookup. This should be done such that new configuration types can
be added by 'putting' config bytes with a new identifier.
I think that gets us a long way.
> List of facets should not be hardcoded
> --------------------------------------
>
> Key: METRON-1337
> URL: https://issues.apache.org/jira/browse/METRON-1337
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Major
>
> Currently the facet fields shown in the left panel of the Alerts UI is hard
> coded in a javascript file. This should be configurable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
