-
Notifications
You must be signed in to change notification settings - Fork 609
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
refactor(types): remove type_name
and sub_fields
from Field
#20496
Merged
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
8 tasks
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8 tasks
18b4236
to
27c218b
Compare
9 tasks
0165303
to
6d40b4b
Compare
6d40b4b
to
81b85ca
Compare
xxchan
approved these changes
Feb 19, 2025
BTW, what's the current behavior of |
145a308
to
144ede2
Compare
xiangjinwu
approved these changes
Feb 20, 2025
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
Signed-off-by: Bugen Zhao <[email protected]>
144ede2
to
46a2007
Compare
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR removes
type_name
andsub_fields
from theField
struct.These two fields are specific to
Field
s with struct (composite) types.type_name
only presents if the composite type is from external schema (like Avro definition) and is only used for debugging purposes (likeDESCRIBE
)sub_fields
is used for fields of composite types. Note thatStructType
already contains the information of field name and field type, so the only point ofsub_fields
is to providetype_name
for fields of composite types.These 2 fields are poorly maintained in our codebase, because there are multiple constructors and they are not enforced to be initialized.
So I believe deprecating them is a good choice. Ideally, we should embed
type_name
directly insideStructType
(#19538), i.e., the tree structure for the data type, instead of having another tree structure (i.e.,sub_fields
).Checklist
Documentation
Release note