[Feature-wip] support datev2/datetimev2/timev2 in FE #9611
Closed
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
github-actions
bot
added
area/load
Gabriel39
changed the title
Contributor
|
Please update the datatype documentation |
Contributor
Author
@hf200012 Im planning to update doc when I finish refactoring date/datetime. This PR just add new types in BE and users cannot use it actually. |
Gabriel39
force-pushed
the
rafactor_time
branch
3 times, most recently
from
68456d9 to
5d6dab9
Compare
Gabriel39
force-pushed
the
rafactor_time
branch
3 times, most recently
from
acfbd0c to
248aace
Compare
Contributor
Author
|
To avoid rebase problem, I take all changes in FE and BE into a single PR 9916. And I just closed this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Proposed changes
#9575
Problem Summary:
Describe the overview of changes.
Checklist(Required)
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...