Skip to content

Conversation

@Gabriel39
Copy link
Contributor

Proposed changes

Issue Number: close #16362

Problem summary

Describe your changes.

Checklist(Required)

  1. Does it affect the original behavior:
    • Yes
    • No
    • I don't know
  2. Has unit tests been added:
    • Yes
    • No
    • No Need
  3. Has document been added or modified:
    • Yes
    • No
    • No Need
  4. Does it need to update dependencies:
    • Yes
    • No
  5. Are there any changes that cannot be rolled back:
    • Yes (If Yes, please explain WHY)
    • No

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...

@github-actions github-actions bot added the area/planner Issues or PRs related to the query planner label Feb 2, 2023
@hello-stephen
Copy link
Contributor

hello-stephen commented Feb 2, 2023

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.01 seconds
load time: 497 seconds
storage size: 17171858630 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230203030315_clickbench_pr_89840.html

Copy link
Contributor

@yiguolei yiguolei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yiguolei yiguolei merged commit 3f4ca3d into apache:master Feb 3, 2023
morningman pushed a commit that referenced this pull request Feb 5, 2023
…16364)

* [Bug](CURRENT_TIMESTAMP) Fix wrong default value after schema change

* update

* update
dutyu pushed a commit to dutyu/doris that referenced this pull request Feb 6, 2023
…pache#16364)

* [Bug](CURRENT_TIMESTAMP) Fix wrong default value after schema change

* update

* update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/planner Issues or PRs related to the query planner dev/1.2.2-merged kind/test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Wrong default value CURRENT_TIMESTAMP after schema change

4 participants