[
https://issues.apache.org/jira/browse/SQOOP-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Szabo updated SQOOP-1735:
--------------------------------
Fix Version/s: (was: 1.4.7)
1.5.0
> Sqoop job fails (but not 'sqoop import') if --create-hive-table is set and
> the hive table already exists
> --------------------------------------------------------------------------------------------------------
>
> Key: SQOOP-1735
> URL: https://issues.apache.org/jira/browse/SQOOP-1735
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.5
> Environment: CentOS 6.6
> Sqoop v. 1.4.5
> Reporter: Joshua Clausen
> Priority: Minor
> Labels: fail, hive, job, table
> Fix For: 1.5.0
>
>
> If you run the same import config from the command line via "sqoop import"
> the import will succeed. Jacek mentioned in a reply to someone that
> --create-hive-table was intended to create the table if it doesn't already
> exist, so I'd expect the behavior within a job should match that.
> The cause is because by default the PROPNAME "hive.fail.table.exists" inside
> the SQOOP_SESSIONS hsqldb table is set to "true" and there's no way to change
> that (besides running an "update" statement inside a hsqldb client), e.g.
> "update sqoop_sessions set propval = false where propname =
> 'hive.fail.table.exists';"
> I'd suggest the best fix would be to add an additional parameter for "sqoop
> import" that allows the user to explicitly set the behavior if the hive table
> already exists. Something like "--hive-fail-table-exists [true/false]".
> That, or just have the propname = hive.fail.table.exists by default be set to
> 'false' in the sqoop_sessions table.
> Note, when I submitted this issue I had to select a "Fix Version/s" in order
> to submit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
