Skip to content

Add TIME to catalog ColumnTypeName - #975

Closed
dhet wants to merge 1 commit into
databricks:mainfrom
dhet:add-time-column-type
Closed

dhet wants to merge 1 commit into
databricks:mainfrom
dhet:add-time-column-type

Conversation

@dhet

@dhet dhet commented Nov 19, 2026 •

Copy link
Copy Markdown

Summary

Adds TIME to com.databricks.sdk.service.catalog.ColumnTypeName so that Unity Catalog columns of type TIME deserialize to a proper enum value instead of null.

Why

Unity Catalog returns type_name: "TIME" for TIME columns (e.g. from tables().list() / tables().get()), but ColumnTypeName has no TIME constant. Because the SDK's ObjectMapper enables READ_UNKNOWN_ENUM_VALUES_AS_NULL, ColumnInfo.getTypeName() silently becomes null for these columns.

Callers that switch on the type name then fail with a NullPointerException, and there is no way to tell a TIME column apart from a genuinely missing type without falling back to parsing type_text.

ColumnTypeName is generated from the OpenAPI spec, so the lasting fix is to add TIME to the spec; this PR is the equivalent change to the generated code.

What changed

Interface changes

  • ColumnTypeName.TIME: new enum constant.

Behavioral changes

  • ColumnInfo.getTypeName() (and other ColumnTypeName fields) returns ColumnTypeName.TIME instead of null for TIME columns.

Internal changes

None.

How is this tested?

mvn -pl databricks-sdk-java compile passes. No unit tests were run or added; the change is a single generated enum constant.

🤖 Generated with Claude Code

@dhet dhet changed the title Add TIME column type Add TIME to catalog ColumnTypeName Nov 19, 2026
@dhet dhet closed this Nov 19, 2026
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.

1 participant