[ATLAS-4421] [Atlas: Hive Import] When import-hive is run with incorrect input the information is not conveyed to the user

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 3.0.0, 2.3.0
• Component/s: atlas-core
• Labels: hive
• Assignee: Disha Talreja
• Reporter: Dharshana M Krishnamoorthy
• Created: 09/Sep/21 13:17
• Updated: 29/Sep/21 18:07
• Resolved: 29/Sep/21 18:07

Description

[root@quasar-cxwzxp-3 bin]# /opt/cloudera/parcels/CDH/lib/atlas/hook-bin/import-hive.sh -f /tmp/file2.txt
...
Log file for import is /var/log/atlas/import-hive.log
...
Hive Meta Data imported successfully!!! 

In the above example, file /tmp/file2.txt does not exists.

The log file is not created in the expected location /var/log/atlas/import-hive.log which is tracked by Jira**

Here, this gives the user an impression that the import is success while nothing has actually happened.
It would be good to convey that no data was imported in such cases

This is true even when the database name/pattern provided to -d or table name/pattern provided to to -t are incorrect

Issue Links

• links to: Apache Review Board