Skip to content

fix(catalog): URL-encode table full_name in TablesAPI#1277

Open
dotuananh0712 wants to merge 1 commit intodatabricks:mainfrom
dotuananh0712:fix/1266-tables-url-encode
Open

fix(catalog): URL-encode table full_name in TablesAPI#1277
dotuananh0712 wants to merge 1 commit intodatabricks:mainfrom
dotuananh0712:fix/1266-tables-url-encode

Conversation

@dotuananh0712
Copy link

@dotuananh0712 dotuananh0712 commented Feb 19, 2026

Summary

Unity Catalog allows table names with special characters (e.g. '%') which must be URL-encoded in requests to the Databricks REST APIs. This fix applies _escape_multi_segment_path_parameter to the full_name parameter in TablesAPI.get(), delete(), exists(), and update() methods.

Changes

  • Added _escape_multi_segment_path_parameter import to catalog.py
  • Applied URL encoding to full_name in:
    • TablesAPI.delete() (line 16218)
    • TablesAPI.exists() (line 16242)
    • TablesAPI.get() (line 16287)
    • TablesAPI.update() (line 16484)

Fixes

Fixes #1266


This PR was contributed by an AI assistant (OpenCode).

NO_CHANGELOG=true

Unity Catalog allows table names with special characters (e.g. '%')
which must be URL-encoded in requests to the Databricks REST APIs.
This fix applies _escape_multi_segment_path_parameter to the full_name
parameter in TablesAPI.get(), delete(), exists(), and update() methods.

Fixes databricks#1266
@github-actions
Copy link

If integration tests don't run automatically, an authorized user can run them manually by following the instructions below:

Trigger:
go/deco-tests-run/sdk-py

Inputs:

  • PR number: 1277
  • Commit SHA: 797314ba2b5e88d89fb43c02b959be4985d0bf98

Checks will be approved automatically on success.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ISSUE] tables.get does not URL-encode table names with special characters

1 participant