[
https://issues.apache.org/jira/browse/ATLAS-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123107#comment-17123107
]
Umesh Padashetty commented on ATLAS-3813:
-----------------------------------------
Kafka file import was built this way and isan expected behavior. Following is
the test case I had written while testing Kafka import. Do we now plan to
change this behavior?
Test Scenario:
* Verify that when an invalid topic name is saved in the file and when this
file path is passed as a param to import script with -f option, then there
should not be any error when the script is run
Expected Result:
* The topics which are valid should be read and added (if new) updated (if pre
existing). Rest topics should be ignored
> Import-<hive/kafka>.sh script shows wrong message of Import success even when
> there are no database/table/topic are imported in the System
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-3813
> URL: https://issues.apache.org/jira/browse/ATLAS-3813
> Project: Atlas
> Issue Type: Bug
> Reporter: Mandar Ambawane
> Assignee: Mandar Ambawane
> Priority: Major
>
> While importing Hive-data from the file, if file has db names and table names
> which are not in the Hive. Application still shows message as "Hive Meta Data
> imported successfully!!!"
> While importing Kafka-Topic data from the file, if file has Topic names
> which are not present in Kafka. Application still shows message as "Kafka
> Data Model imported successfully!!!"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
