[
https://issues.apache.org/jira/browse/METRON-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228497#comment-15228497
]
ASF GitHub Bot commented on METRON-93:
--------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/66#discussion_r58729524
--- Diff:
metron-streaming/Metron-Common/src/main/java/org/apache/metron/bolt/BulkMessageWriterBolt.java
---
@@ -81,8 +81,7 @@ public void execute(Tuple tuple) {
sensorMessageMap.put(sensorType, messageList);
} else {
try {
- String esType = sensorType + "_doc";
- bulkMessageWriter.write(esType, configurations, tupleList,
messageList);
+ bulkMessageWriter.write(sensorType, configurations, tupleList,
messageList);
--- End diff --
Yeah, I moved the _doc modification down into the ES writer rather than
having it at the bolt level. Should still work with the UI.
> Generalize the HBase threat intel infrastructure to support enrichments
> -----------------------------------------------------------------------
>
> Key: METRON-93
> URL: https://issues.apache.org/jira/browse/METRON-93
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> As it stands, the threat intel infrastructure is awkward. Namely, different
> threat intelligence sources must be pushed into separate hbase tables
> (malicious_ips separate form malicious_hosts, for instance). We'd rather
> have one table where the type is brought into the rowkey. Since this
> infrastructure is generalized, also add a simple hbase enrichment adapter.
> Furthermore, the configuration for a new enrichment should be added to
> zookeeper as part of the data load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
