ORC-1973: [C++] Use int64_t instead of google::protobuf::int64 for Protobuf v22+
#2388
Conversation
This file contains hidden or 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
…r `Protobuf` v22+
dongjoon-hyun
force-pushed
the
ORC-1973-2.0
branch
from
b00732a to
6f0ffab
Compare
dongjoon-hyun
added a commit
that referenced
this pull request
Sep 12, 2025
…r `Protobuf` v22+ ### What changes were proposed in this pull request? This PR aims to use `int64_t` instead of `google::protobuf::int64` to follow ProtocolBuff v22.0 changes. - https://github.com/protocolbuffers/protobuf/releases/tag/v22.0 > Fixed C++ code generation for protos that use int32_t, uint32_t, int64_t, uint64_t, size_t as field names. ### Why are the changes needed? Currently, `branch-2.0` branch CIs are broken like the following. - https://github.com/apache/orc/actions/runs/17683570590/job/50263141762 ``` In file included from /Users/runner/work/orc/orc/c++/src/io/InputStream.cc:19: /Users/runner/work/orc/orc/c++/src/io/InputStream.hh:75:31: error: no type named 'int64' in namespace 'google::protobuf' virtual google::protobuf::int64 ByteCount() const override; ~~~~~~~~~~~~~~~~~~^ /Users/runner/work/orc/orc/c++/src/io/InputStream.cc:115:21: error: no type named 'int64' in namespace 'google::protobuf' google::protobuf::int64 SeekableArrayInputStream::ByteCount() const { ~~~~~~~~~~~~~~~~~~^ /Users/runner/work/orc/orc/c++/src/io/InputStream.cc:116:42: error: no type named 'int64' in namespace 'google::protobuf' return static_cast<google::protobuf::int64>(position); ~~~~~~~~~~~~~~~~~~^ 3 errors generated. ``` ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #2388 from dongjoon-hyun/ORC-1973-2.0. Authored-by: Dongjoon Hyun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Member
Author
|
Merged to branch-2.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
This PR aims to use
int64_tinstead ofgoogle::protobuf::int64to follow ProtocolBuff v22.0 changes.Why are the changes needed?
Currently,
branch-2.0branch CIs are broken like the following.How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.