Skip to content

[feature][PES][datasource] add support for hive datasource sharing with kerberos keytab for non-creator users #1090

Description

@v-kkhuang

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Problem Description

Is your feature request related to a problem? Please describe.

Currently, Hive datasources configured with Kerberos authentication can only be queried by the datasource creator or administrators. In multi-tenant scenarios where a shared Kerberos keytab is already available on the server, other users still cannot access the same Hive datasource without re-creating it and uploading their own keytab, resulting in duplicated configuration and operational overhead.

Description

A short description of your feature

Add a feature switch linkis.datasource.hive.share.enable (default off) to allow non-creator users to query Hive datasources. When enabled, the system uses a local keytab file (located at linkis.datasource.hive.share.keytab.path, derived from the principal name) instead of downloading the keytab from BML, and the permission checks in the metadata query service are relaxed so that any authenticated user can access Hive datasources.

Use case

Describe the use case of your feature request and the solution you'd like.

In a multi-tenant environment where a single Kerberos keytab (e.g. a service principal) is shared across users, operators want all users to query the same Hive datasource for metadata without re-creating it. By enabling the share switch and placing the keytab file on the metadata query server, any authenticated user can query the shared Hive datasource metadata.

Solutions

Describe alternatives you've considered.

The alternative is for each user to create their own Hive datasource and upload their own keytab via BML, which duplicates configuration and storage. The shared-keytab approach centralizes keytab management on the server and reduces redundant datasource definitions.

Anything else

Additional context or screenshots about the feature request.

This change also includes a minor fix to the DB2 schema query to trim schema names (TRIM(SCHEMANAME)) so that whitespace-padded schema names are not returned.

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions