You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Umesh Padashetty (JIRA)" <ji...@apache.org> on 2019/03/20 07:06:00 UTC

[jira] [Assigned] (ATLAS-2983) Fixes and clean up for Atlas Kafka bridge utility

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

Umesh Padashetty reassigned ATLAS-2983:
---------------------------------------

    Assignee: Umesh Padashetty

> Fixes and clean up for Atlas Kafka bridge utility
> -------------------------------------------------
>
>                 Key: ATLAS-2983
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2983
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core, atlas-webui
>    Affects Versions: 1.0.0, 1.1.0
>            Reporter: Umesh Padashetty
>            Assignee: Umesh Padashetty
>            Priority: Major
>         Attachments: ATLAS-2983.patch
>
>
> # Currently, import-kafka.sh script allows selective kafka topic import by providing -t or --topic option, but the script only checks for the topics which start with the topic name provided and does not support regular expression based selective import. With the fix provided, regex patterns can be used along with -t as well as -f (file based import) option
>  # When a bad import-kafka command is being fired, following usage is being printed on the console. Here, option should be -t instead of -n. Have fixed this minor issue, along with some more text changes
>  ** import-kafka.sh [*-n* <topic regex> OR --topic <topic regex >]
>  # Since we now have support for kakfa bridge and hbase hook/bridge, option for creating entities for the following in Atlas UI could be removed 
>  ## hbase_table
>  ## hbase_column
>  ## hbase_column_family
>  ## kafka_topic
>  ## hbase_namespace



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