-
Notifications
You must be signed in to change notification settings - Fork 596
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
feat(types): support ns timestamp #19827
base: main
Are you sure you want to change the base?
Conversation
sorry, mis clicked update branch |
cc @xiangjinwu PTAL❤️ |
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 you also include the testing SQLs you have tried?
- Is any caller of
to_protobuf
/from_protobuf
assuming thatTimestamp
would be fixed 64-bit? This assumption is no longer true.
) | ||
} | ||
let dt = s | ||
.parse::<jiff::civil::DateTime>() |
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.
Why do we need to introduce yet another dependency in addition to chrono
and speedate
?
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.
Because chrono can't be parsed, and speedate is only parsed at the us level
@@ -495,7 +495,7 @@ impl HummockVersion { | |||
.clone_from(&group_construct.table_ids); | |||
self.levels.insert(*compaction_group_id, new_levels); | |||
let member_table_ids = if group_construct.version | |||
>= CompatibilityVersion::NoMemberTableIds as _ | |||
>= CompatibilityVersion::NoMemberTableIds as i32 |
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.
avoid unrelated change
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.
It seems we do need this as long as we use jiff
in src/common/src/types/datetime.rs
. Not sure why though ... maybe a rustc bug.
Btw it can be group_construct.version() >= CompatibilityVersion::NoMemberTableIds
rather than if group_construct.version >= CompatibilityVersion::NoMemberTableIds as i32
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.
It doesn't seem to work because the type of CompatibilityVersion::NoMemberTableIds is not i32
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.
group_construct.version()
returns CompatibilityVersion
, while group_construct.version
is i32
added in ci |
@@ -495,7 +495,7 @@ impl HummockVersion { | |||
.clone_from(&group_construct.table_ids); | |||
self.levels.insert(*compaction_group_id, new_levels); | |||
let member_table_ids = if group_construct.version | |||
>= CompatibilityVersion::NoMemberTableIds as _ | |||
>= CompatibilityVersion::NoMemberTableIds as i32 |
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.
It seems we do need this as long as we use jiff
in src/common/src/types/datetime.rs
. Not sure why though ... maybe a rustc bug.
Btw it can be group_construct.version() >= CompatibilityVersion::NoMemberTableIds
rather than if group_construct.version >= CompatibilityVersion::NoMemberTableIds as i32
Btw you can fix the e2e test with https://www.sqlite.org/sqllogictest/doc/trunk/about.wiki
|
26d9664
to
6b8af32
Compare
FYI regarding your latest e2e failure, it is actually a bug in our existing
Given it is out of scope of this PR, let's just replace the case with one without |
6b8af32
to
2c87c76
Compare
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
our timestamp only support ms, But our internal implementation is capable of ns, it's just that we automatically convert it to ms when we read it in, and this pr can read ns to support ns.
Checklist
Documentation
Release note