Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CatalogVersion and move CatalogHandle to SPI #15425

Merged
merged 3 commits into from
Dec 17, 2022

Conversation

dain
Copy link
Member

@dain dain commented Dec 16, 2022

Description

Add CatalogVersion and move CatalogHandle to SPI

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

}
finally {
catalogsUpdateLock.unlock();
}
}

static CatalogVersion computeCatalogVersion(String catalogName, String connectorName, Map<String, String> properties)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't we say something about catalog versions being lexical sortable? Hashing doesn't seem to satisfy that. If it's not a real constraint, maybe just remove the comment about it being lexical sortable since that would be an implementation detail from the connector side.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future work, a version can be anything the catalog store want and isn't required to be sortable.

Copy link
Member

@electrum electrum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments from @erichwang

@dain dain merged commit d3e9e9f into trinodb:master Dec 17, 2022
@dain dain deleted the catalog-handle branch December 17, 2022 18:54
@github-actions github-actions bot added this to the 404 milestone Dec 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants