Skip to content

feat: support TTL as a column-level configuration #442

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

morsapaes
Copy link

Summary

Fixes #437.

Used the same approach as #275, although this requires users to set model contracts to enforced: true (which can be annoying if you're not using this feature, since it requires specifying the data_type for each column in the model).

Not sure how the release process works for the adapter, so added an entry to CHANGELOG.md under Unreleased.

Checklist

Delete items not relevant to your PR:

  • Unit and integration tests covering the common scenarios were added
  • A human-readable description of the changes was provided to include in CHANGELOG
  • For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

@mshustov mshustov requested a review from BentsiLeviav April 16, 2025 12:34
@mshustov mshustov requested a review from Copilot April 16, 2025 13:45
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

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.

Implement column level TTL configuration
2 participants