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.

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

bug: connector can not parse datatypes before 1970-01-01 #15435

Closed
st1page opened this issue Mar 5, 2024 · 1 comment · Fixed by #15437
Closed

bug: connector can not parse datatypes before 1970-01-01 #15435

st1page opened this issue Mar 5, 2024 · 1 comment · Fixed by #15437
Assignees
Milestone

Comments

@st1page
Copy link
Contributor

st1page commented Mar 5, 2024

risingwave_connector::parser: failed to parse non-pk column, padding with `NULL` error=Expected type `Some(Timestamp)` but got `i64` for `-2208988800000000000`

It is supported in RisingWave's SQL engine

dev=> select '1900-01-01 00:00:00'::timestamptz;
NOTICE:  Your session timezone is UTC. It was used in the interpretation of timestamps and dates in your query. If this is unintended, change your timezone to match that of your data's with `set timezone = [timezone]` or rewrite your query with an explicit timezone conversion, e.g. with `AT TIME ZONE`.

        timestamptz        
---------------------------
 1900-01-01 00:00:00+00:00
(1 row)
@github-actions github-actions bot added this to the release-1.8 milestone Mar 5, 2024
@xiangjinwu
Copy link
Contributor

The correct behavior of debezium parser is to read connect.name (#14703) and invoke one of from_secs / from_millis / from_micros rather than guessing the unit with i64_to_timestamptz.

@xiangjinwu xiangjinwu linked a pull request Mar 5, 2024 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants