Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bug: hummock time travel query syntax should use session's default time zone #19753

Open
zwang28 opened this issue Dec 11, 2024 · 0 comments
Open

bug: hummock time travel query syntax should use session's default time zone #19753

zwang28 opened this issue Dec 11, 2024 · 0 comments
Assignees
@zwang28
Labels
type/bug Something isn't working
Milestone
release-2.2

Comments

@zwang28
Copy link
Contributor

zwang28 commented Dec 11, 2024

Describe the bug

Currently, SELECT * FROM t_foo FOR SYSTEM_TIME AS OF '2000-02-29T12:13:14'; will use the UTC+0 time zone.
To ensure consistency with other RW usages of timestamps, it should adhere to the SET TIME ZONE directive.

Error message/log

No response

To Reproduce

No response

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response
@zwang28 zwang28 added the type/bug Something isn't working label Dec 11, 2024
@zwang28 zwang28 self-assigned this Dec 11, 2024
@github-actions github-actions bot added this to the release-2.2 milestone Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zwang28 zwang28

Labels
type/bug Something isn't working
Projects
None yet
Milestone
release-2.2
Development

No branches or pull requests
1 participant
@zwang28