Add alter statements for altering table ttl after table creation #121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since materialized views don't support altering ttl configuration, we weren't able to do it for operations table. Signed-off-by: Pradeep Chhetri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Pradeep Chhetri [email protected]
Tested in local development environment by updating the ttl field in configuration file.
Which problem is this PR solving?
Resolves #120
Short description of the changes
We added alter statements for each of the three tables which gets executed if ttl is greater than 0.
Since materialized views don't support altering ttl configuration, we weren't able to do it for operations table.