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.
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
Fix logical error with IPv4 in Protobuf, add support for Date32 #48486
Fix logical error with IPv4 in Protobuf, add support for Date32 #48486
Changes from all commits
bb6cf52
c2f1828
8af9cf6
34cc7b6
7dcf642
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Could we write
: public ProtobufSerializerNumber<UInt32>
here for consistency withProtobufSerializerDate
?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 cannot, because otherwise we will get logical error
Bad cast from type DB::ColumnVector<StrongTypedef<unsigned int, DB::IPv4Tag>> to DB::ColumnVector<unsigned int>'
.IPv4
type is not the same asUInt32
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.
Yeah, I see.
DataTypeDate
is derived fromDataTypeNumberBase<UInt16>
however for unknown reasonDataTypeIPv4
is not derived fromDataTypeNumberBase<UInt32>
.Probably if
DataTypeIPv4
was derived fromDataTypeNumberBase<UInt32>
withColumnType = ColumnVector<UInt32>
, that would make things easier.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.
I tried to change it to
DataTypeNumberBase<UInt32>
withColumnType = ColumnVector<UInt32>
, but seems like it won't work as in some places we need to distinguish betweenColumnVector<UInt32>
andColumnIPv4
(for example for proper CAST I guess) and that's the reason it's implemented as separate DataType. Let's keep it as is.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.
Let's not throw
LOGICAL_ERROR
here. We can add new types in future and forget to support it in Protobuf format. It's ok to thow justILLEGAL_COLUMN
.