Table of Contents


  1. Abstract
  2. Installation and Upgrade
  3. 10.1.1 HotFix 1 Fixed Limitations and Closed Enhancements
  4. 10.1.1 HotFix 1 Known Limitations
  5. 10.1.1 Update 2 Fixed Limitations and Closed Enhancements
  6. 10.1.1 Update 2 Known Limitations
  7. 10.1.1 Update 1 Fixed Limitations and Closed Enhancements
  8. 10.1.1 Update 1 Known Limitations
  9. 10.1.1 Fixed Limitations and Closed Enhancements
  10. 10.1.1 Known Limitations
  11. Informatica Global Customer Support

Intelligent Data Lake Known Limitations (10.1.1)

Intelligent Data Lake Known Limitations (10.1.1)

The following table describes known limitations:
The Data Preview tab and Import to Lake option appear for Hive data assets that are not in the data lake (as defined in the IDL service configuration). You cannot import these assets into the lake using these options.
In a Hortonworks distribution, Sqoop does not support case-sensitive metadata and hence export fails.
The activity statistics such as row count for import, export, and publication operations do not display any values when you use Blaze engine for execution.
The Import operation fails if you try to import timestamp data with timezone from an Oracle data source. Timestamp with Timezone is not supported for Sqoop on Blaze engine due to file format limitations.
When you try to export data to append or overwrite a view on an external database or import from a view in an external database, the application indicates that the activity is complete, but the import or export operation fails because it is not allowed.
Column-level privileges are not supported on Ranger and Sentry due to third party (Ranger/Sentry) metadata access limitations.

Updated January 17, 2019