Hadoop connection

Hive integration

Hive database names can only contains letters, numbers and underscores.
This database is used as fallback for datasets which do not have a database set.

Advanced

Class name of a custom HDFS properties

Naming rules for new datasets

These settings define how managed HDFS datasets are located and mapped to Hive tables. These settings are only applied when creating a new managed HDFS dataset. You can always modify these afterwards in the HDFS dataset settings. See for more information.

This will be prepended before the dataset name in the path, relative to the connection root. You may reference variables here, they will be expanded dynamically
This will be appended after the dataset name in the path, relative to the connection root. You may reference variables here, they will be expanded dynamically
Hive database names can only contains letters, numbers and underscores.

You may reference variables here, they will be expanded dynamically
Hive table names can only contains letters, numbers and underscores.

This will be prepended before the dataset name in the hive table name. You may reference variables here, they will be expanded dynamically
Hive table names can only contains letters, numbers and underscores.

This will be appended after the dataset name in the hive table name. You may reference variables here, they will be expanded dynamically
Path does not include any variable reference. Datasets will be created in an absolute path, which is not recommended for relocation purposes and may cause name clashes.
Table and schema name do not include any variable reference. Datasets will be created with absolute names, which is not recommended for relocation purposes and may cause name clashes.
This will be prepended to the path for uploaded datasets. Variables expansion is not supported.

Custom properties

For specific use cases

Impersonation-related settings