GitHub user nickwallen opened a pull request:
https://github.com/apache/metron/pull/933
METRON-1452 Rebase Dev Environment on Latest CentOS 6
Currently the CentOS development environment
(`metron-deployment/development/centos6`) is based on an image
[metron/centos_base](https://app
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/929
I updated the instructions and the `solr.zookeeper` business is legacy
naming, but I think it does fit since it's specific to zookeeper rather than
connecting to ES master. I dunno, that's just wha
Github user cestella closed the pull request at:
https://github.com/apache/metron/pull/929
---
GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/934
METRON-1423: Ambari work to handle Solr configuration
## Contributor Comments
This PR allows support for Metron-related Solr configuration and management
through Ambari. That does NOT include
Github user ctramnitz commented on the issue:
https://github.com/apache/metron/pull/579
I think
https://github.com/apache/metron/pull/579/commits/ccd99dda3c8a72408ae13eeaca078af1e345a36c#diff-e0385f97ebea64bab3a83bceef70bb4aR67
expected.put(BasicPaloAltoFirewallParser.PaloAltoDomai
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/579
from @ctramnitz on the PR I made against his branch.
> However, I'm not sure the result for is really as expected.
> It shouldn't be "<11>Jan 5 05:38:59 PAN1.exampleCustomer.com 1", but
Github user ctramnitz commented on the issue:
https://github.com/apache/metron/pull/579
For the syslog header vs message parser this future_use is not really
important. This has other implications than just carrying arbitrary data in a
field that is labeled to do something else.
---
I would like to bring this discussion to a conclusion and update the PR
accordingly. To clarify on whether we depend on an RDBMS right now, we do
but only for authentication which will probably be replaced at some point.
So the answer is not really. I personally agree with Simon and think we
shou
+1 I think going with HBase is a good approach for now. Thanks for laying
out the pros and cons.
On Fri, Feb 9, 2018 at 3:46 PM, Ryan Merriman wrote:
> I would like to bring this discussion to a conclusion and update the PR
> accordingly. To clarify on whether we depend on an RDBMS right now,