You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Wesley Forti (JIRA)" <ji...@apache.org> on 2015/12/04 15:13:10 UTC

[jira] [Created] (SQOOP-2721) Creates Sqoop Jobs With Validation

Wesley Forti created SQOOP-2721:
-----------------------------------

             Summary: Creates Sqoop Jobs With Validation
                 Key: SQOOP-2721
                 URL: https://issues.apache.org/jira/browse/SQOOP-2721
             Project: Sqoop
          Issue Type: New Feature
            Reporter: Wesley Forti
            Priority: Minor


Hi guys, 

I would like to suggest a feature for sqoop job creation process.

As soon as we create a sqoop job, sqoop validates only if sqoop job syntax is correct. It does not validate values like DB connection information, if table exists and stuff like that.

So, what is in my mind is, since we have all information about db connection and table name, why not validate that during sqoop job creation?
Assuming that there could be a great interval between sqoop job creation and execution (this is my case), we could get some basic creation mistakes much sooner. (At least I dont have to wait until first execution)
. The main ideia is to check table names, connectivity issues and everything that is possible.

We could keep sqoop job behavior as it is, and run this checks when a validate parameter is present on sqoop job creation comand.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)