Github user merrimanr commented on a diff in the pull request: https://github.com/apache/metron/pull/603#discussion_r120115152 --- Diff: metron-platform/metron-enrichment/src/main/java/org/apache/metron/enrichment/bolt/JoinBolt.java --- @@ -141,11 +141,12 @@ public void execute(Tuple tuple) { collector.emit( "message" , tuple , new Values( key - , joinMessages(streamMessageMap) + , joinMessages(streamMessageMap, this.messageGetStrategy) ) ); cache.invalidate(key); - collector.ack(tuple); + Tuple messageTuple = streamMessageMap.get("message:"); + collector.ack(messageTuple); --- End diff -- I don't believe so. The tuple that comes straight from the SplitBolt (the "message" stream) is the only tuple that is anchored. Tuples that go to EnrichmentBolts are not anchored.
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---