-
Notifications
You must be signed in to change notification settings - Fork 379
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
[Improvement] Unify the modification behavior of the comment field. #4968
Comments
@mchades i want to have a try. |
@koonchen No problem! Please go ahead and feel free to ping me if you have any questions |
Deprecate the removeComment change across all entities. |
Allow null or empty string as valid values for newComment in updateComment. |
@AbhiSharmaNIT Yeah, you summed it up correctly! I have not seen @koonchen submit the relevant PR so far, so I think if you are interested in this issue, you can also submit a PR. |
@mchades this week is a national holiday, and you didn't assign me |
assign is not a required step, you can start at any time. |
@mchades I don't think so. You need to let others know the urgency and responsibility of the matter. |
I think the comments on the issue are sufficient. If you care about this, it has been assigned to you now, so please start as soon as possible. Others can also submit at any time before relevant PRs are submitted. |
…ent field (#5121) ### What changes were proposed in this pull request? - deprecated the removeComment change - the new comment of updateComment supports null and empty string ### Why are the changes needed? Fix: #4968 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? Pass existing tests Co-authored-by: chenzeping.ricco <[email protected]>
…ent field (#5288) ### What changes were proposed in this pull request? - deprecated the removeComment change - the new comment of updateComment supports null and empty string ### Why are the changes needed? Fix: #4968 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? Pass existing tests Co-authored-by: Ricco Chen <[email protected]> Co-authored-by: chenzeping.ricco <[email protected]>
…e comment field (apache#5121) ### What changes were proposed in this pull request? - deprecated the removeComment change - the new comment of updateComment supports null and empty string ### Why are the changes needed? Fix: apache#4968 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? Pass existing tests Co-authored-by: chenzeping.ricco <[email protected]>
What would you like to be improved?
Currently, only the fileset supports the
removeComment
change; other entities like catalog and table only supportupdateComment
changes. Additionally,newComment
cannot be null or an empty string. We should unify this behavior.How should we improve?
Unify the modification behavior of the comment field:
removeComment
changeupdateComment
supports null and empty stringThe text was updated successfully, but these errors were encountered: