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
Set ttlaction back to free #17039
Set ttlaction back to free #17039
Conversation
If we only set the property default value to free, would that resolve the backward compatibility? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
.setDescription("When file's ttl is expired, the action performs on it. Options: " | ||
+ "DELETE_ALLUXIO(default), FREE or DELETE") | ||
+ "FREE(default) or DELETE") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we still have delete alluxio
alluxio-bot, merge this please |
### What changes are proposed in this pull request? Set the ttlAction back to free to fix the backward compatibility issue from our daily sanity test. ### Why are the changes needed? Fix the backward compatibility proto issue from a previous PR Alluxio#16823. ### Does this PR introduce any user facing changes? No. pr-link: Alluxio#17039 change-id: cid-887a9d5ddfe7f4f9e0b929a83f529278b1d9bd90
### What changes are proposed in this pull request? Set the ttlAction back to free to fix the backward compatibility issue from our daily sanity test. ### Why are the changes needed? Fix the backward compatibility proto issue from a previous PR Alluxio#16823. ### Does this PR introduce any user facing changes? No. pr-link: Alluxio#17039 change-id: cid-887a9d5ddfe7f4f9e0b929a83f529278b1d9bd90
What changes are proposed in this pull request?
Set the ttlAction back to free to fix the backward compatibility issue from our daily sanity test.
Why are the changes needed?
Fix the backward compatibility proto issue from a previous PR
#16823.
Does this PR introduce any user facing changes?
No.