Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: The Cloudera Community will undergo maintenance on Saturday, August 17 at 12:00am PDT. See more info here.

"where" clause not considered for identifying split range in cloudera teradata connector and sqoop

"where" clause not considered for identifying split range in cloudera teradata connector and sqoop

New Contributor

Hi All,

 

I'm working on importing data from Teradata using sqoop 1.4.5 and cloudera teradata connector 1.4x. I'm currently using the below command:

 

sqoop import --connect jdbc:teradata://teradata/dwh/ --username sample --password 'sample' --table table1 --where 'partition=1' --hive-import --hive-table foo.table1  --target-dir /tmp/foo --split-by id --delete-target-dir

 

I'm kind of intrigued by the below line in the stdout:

 

5/10/20 11:27:42 INFO teradata.TeradataSplitByValueInputFormat: SELECT MIN( id ), MAX( id ) FROM "table1"

 

I'm wondering why the "where" clause is not used to figure out the range for partitions as it does for other connectors like PostgreSQL?