[
https://issues.apache.org/jira/browse/SQOOP-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422370#comment-13422370
]
Jarek Jarcec Cecho commented on SQOOP-517:
------------------------------------------
Hi Sriram,
thank you very much for your feedback. I'm sorry but I'm still unsure what
you're doing. Sqoop is not supporting import from MySQL into Cassandra directly
(at least not the apache version). Also your example command line do contain a
lot of cassandra like parameters that are definitely not available in Apache
Sqoop. Are you using some custom build or wrapper?
But if the issue is just in incorrect type mapping, then you might consider
overriding default types as is described in following section of Sqoop user
guide:
http://sqoop.apache.org/docs/1.4.1-incubating/SqoopUserGuide.html#_controlling_type_mapping
Jarcec
> sqoop import having issues with Timestamp to Cassandra (DateTypes).
> --------------------------------------------------------------------
>
> Key: SQOOP-517
> URL: https://issues.apache.org/jira/browse/SQOOP-517
> Project: Sqoop
> Issue Type: Bug
> Components: hive-integration, sqoop2-client, sqoop2-framework
> Affects Versions: 1.4.0-incubating
> Environment: Red Hat Linux - packaged with Datastax cassandra
> Reporter: sriram
>
> We are trying to import data from SQL Server , one of the tables have
> datetime field. Which is correctly converted to Timestamp in java, but when
> it tries to map it to cassandra DateType. It is failing.
> Timestamp (java) is not mapping to DateType(cassandra).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
