Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Big Data Management
  3. Connections
  4. Mappings in the Hadoop Environment
  5. Mapping Objects in the Hadoop Environment
  6. Monitoring Mappings in the Hadoop Environment
  7. Mappings in the Native Environment
  8. Profiles
  9. Native Environment Optimization
  10. Data Type Reference
  11. Function Reference
  12. Parameter Reference
  13. Multiple Blaze Instances on a Cluster

Rules and Guidelines for Sqoop Sources

Rules and Guidelines for Sqoop Sources

Consider the following rules and guidelines when you configure a Sqoop source in a mapping:
  • If you create a password file to access a database, to run the mapping successfully, you must ensure that the password file exists on HDFS.
  • To override the default query in a mapping with an advanced query, you must define a mapping parameter and set its value to $CONDITIONS. You must then include $CONDITIONS in the WHERE clause of the custom query.
  • If you define a custom query, you must verify that the metadata of the custom query matches the metadata of the source object. Otherwise, Sqoop might write blank values to the target.
  • If you specify a sort condition in a mapping, the Data Integration Service ignores the Order By condition.
  • You cannot sort columns in a Sqoop source.
  • You cannot read distinct rows from a Sqoop source.
  • When you enable OraOop and configure an advanced query to read data from an Oracle source through Sqoop, the mapping fails on the Spark engine.
  • When you read data from an Oracle source through Sqoop and run the mapping on the Blaze or Spark engine, Sqoop treats the owner name as case sensitive.
  • If you configure the --username or --password argument in a JDBC connection or mapping, Sqoop ignores the arguments.


Updated July 03, 2018