Table of Contents

Search

  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

Third-Party Limitations (10.1.1 HotFix 1)

Third-Party Limitations (10.1.1 HotFix 1)

The following table describes third-party known limitations:
Bug
Description
BDM-5478
You cannot use impersonation users or operating system profiles to run mappings on an Azure HDInsight cluster that uses ADLS or WASB. HDInsight clusters that use ADLS or WASB are single-user clusters.
BDM-5217
When you test an HDFS connection to the HDInsight cluster from the Developer tool, the test connection fails with the following error:
org.apache.hadoop.fs.azure.AzureExceptionom : org.apache.hadoop.fs.azure.KeyProviderException: java.io.IOException: Cannot run program '/usr/lib/python2.7/dist-packages/hdinsight_common/decrypt.sh': CreateProcess error=2
Workaround:
If the HDInsight cluster uses the WASB file system, perform the following steps:
  1. On the Linux machine on the HDInsight cluster, open the command line.
  2. Go to the directory that contains the
    decrypt.sh
    file.
  3. Run the following command:
    /decrypt.sh <ENCRYPTED ACCOUNT KEY>
    The command returns a decrypted key for the encrypted key in the
    fs.azure.account.key.STORAGE_ACCOUNT_NAME .blob.core.windows.net
    property.
  4. In the
    core-site.xml
    file of the Developer client system, replace the original encrypted key with the decrypted value.
  5. To disable encryption and decryption, comment out the following properties in the
    core-site.xml
    file:
    • fs.azure.account.keyprovider.STORAGE_ACCOUNT_NAME.blob.core.windows.net
    • fs.azure.shellkeyprovider.script
  6. Restart the Developer tool.
This workaround does not apply to HDInsight clusters that use the ADLS file system, for which there is no workaround.