You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Dharshana M Krishnamoorthy (Jira)" <ji...@apache.org> on 2021/09/09 13:18:00 UTC

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

Dharshana M Krishnamoorthy created ATLAS-4421:
-------------------------------------------------

             Summary: [Atlas: Hive Import] When import-hive is run with incorrect input the information is not conveyed to the user
                 Key: ATLAS-4421
                 URL: https://issues.apache.org/jira/browse/ATLAS-4421
             Project: Atlas
          Issue Type: Bug
            Reporter: Dharshana M Krishnamoorthy


{code:java}
[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!!! {code}
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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)