You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Jon Zeolla (JIRA)" <ji...@apache.org> on 2019/02/24 04:36:00 UTC

[jira] [Updated] (METRON-2003) Bro plugin topic should fall back to the log writer's path

     [ https://issues.apache.org/jira/browse/METRON-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Zeolla updated METRON-2003:
-------------------------------
    Summary: Bro plugin topic should fall back to the log writer's path  (was: Bro plugin topic should fall back to $path)

> Bro plugin topic should fall back to the log writer's path
> ----------------------------------------------------------
>
>                 Key: METRON-2003
>                 URL: https://issues.apache.org/jira/browse/METRON-2003
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Jon Zeolla
>            Assignee: Jon Zeolla
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As of METRON-1992 a regression was implemented where the destination kafka topic name no longer uses $path when `Kafka::topic_name` is not set.  The order of precedence should be:
> 1. `$config = table(["topic_name"] = "kafka_topic_name_override")`
> 2. `Kafka::topic_name`
> 3. `$path`



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)