[Issue #1372] read TIME as picosecond LongColumnVector for zero-copy Trino - #1373
Open
gengdy1545 wants to merge 7 commits into
Open
[Issue #1372] read TIME as picosecond LongColumnVector for zero-copy Trino#1373gengdy1545 wants to merge 7 commits into
gengdy1545 wants to merge 7 commits into
Conversation
gengdy1545
force-pushed
the
feature/timeBlock
branch
from
August 14, 2026 08:16
0197f40 to
a4474cf
Compare
Collaborator
Author
|
PTAL |
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
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.
this PR is based on the SHORT/INT/LONG split branch (
feature/splitInteger). Please do not merge yet.