Export All failure in secured multi-tenant clusters

The Export All feature is resolved to follow tenant boundaries and cluster security policies in secured multi-tenant environments. However, certain architectural limitations remain when using Impala or encountering existing directory permissions.

Impala export fails when targeting arbitrary locations

Condition

Export operations using Impala fail when the target directory is outside the source database.

Cause

When tenant colocation is enabled, Impala exports use a CREATE TABLE AS SELECT approach that creates an external table. The external table must comply with tenant colocation rules and therefore must reside within the source database’s warehouse directory. This is an architectural constraint of Hive and Impala.

Solution

  1. Use Hive for exports to arbitrary locations.
  2. When using Impala, export to a subdirectory within the source database warehouse directory.
  3. Configure appropriate access control policies to allow required export paths within tenant boundaries.

Exported files not accessible in Hue file browser

Condition

Exported files are not readable through the Hue file browser.

Cause

Files created through Impala exports are owned by the Impala service user.

Solution

  1. Use Hive for exports. Hive exports use doAs, which creates files owned by the end user.
  2. Configure appropriate directory permissions or access control policies to allow user access to exported files.

Impala export fails when targeting arbitrary locations

Condition

Export operations using Impala fail when the target directory is outside the source database.

Cause

When tenant colocation is enabled, Impala exports use a CREATE TABLE AS SELECT approach that creates an external table. The external table must comply with tenant colocation rules and therefore must reside within the source database’s warehouse directory. This is an architectural constraint of Hive and Impala.

Solution

  1. Use Hive for exports to arbitrary locations.
  2. When using Impala, export to a subdirectory within the source database warehouse directory.
  3. Configure appropriate access control policies to allow required export paths within tenant boundaries.