[
https://issues.apache.org/jira/browse/METRON-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059406#comment-16059406
]
ASF GitHub Bot commented on METRON-1001:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/621#discussion_r123512057
--- Diff:
metron-platform/metron-parsers/src/main/java/org/apache/metron/parsers/bolt/ParserBolt.java
---
@@ -118,6 +116,27 @@ protected void initializeStellar() {
StellarFunctions.initialize(stellarContext);
}
+ private Map<String, Object> getMetadata(Tuple t, boolean readMetadata) {
+ Map<String, Object> ret = new HashMap<>();
+ if(!readMetadata) {
+ return ret;
+ }
+
ret.put(SimpleStormKafkaBuilder.FieldsConfiguration.TOPIC.getFieldName(),
t.getString(2));
--- End diff --
The contract is that the value is the first element in the tuple, the key
the 2nd element in the tuple and any metadata from the environment passed in
after that.
> Allow metron to ingest parser metadata along with data
> ------------------------------------------------------
>
> Key: METRON-1001
> URL: https://issues.apache.org/jira/browse/METRON-1001
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Currently, we only ingest data in Metron. Often, there is valuable metadata
> constructed up-stream of Metron that is relevant to enrichment and cross-cuts
> many data formats. Take, for instance, a multi-tenancy case where multiple
> sources come in and you'd like to tag the data with the customer ID. In this
> case you're stuck finding ways to add the metadata to each data source's
> format. Rather than do that, we should allow metadata to be ingested along
> with the data associated with it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
