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

Improve DateTime64 pushdown to ClickHouse #23789

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

ssheikin
Copy link
Contributor

@ssheikin ssheikin commented Oct 15, 2024

Description

Additional context and related issues

PRs:

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## Section
* Improve DateTime64 pushdown to ClickHouse. ({issue}`issuenumber`)

The time zone is not stored in the rows of the table,
but is stored in the column metadata.

From ClickHouse documentation
https://clickhouse.com/docs/en/sql-reference/data-types/datetime

The point in time is saved as a Unix timestamp, regardless of the time
zone or daylight saving time. The time zone affects how the values of
the DateTime type values are displayed in text format and how the values
specified as strings are parsed (‘2020-01-01 05:00:01’).

Timezone agnostic Unix timestamp is stored in tables, and the timezone
is used to transform it to text format or back during data import/export
or to make calendar calculations on the values (example: toDate, toHour
functions etc.). The time zone is not stored in the rows of the table
(or in resultset), but is stored in the column metadata.
@ssheikin ssheikin force-pushed the ssheikin/42/trino/clickhouse-datetime64-pushdown branch from 3c07a01 to 0c80cf5 Compare October 16, 2024 07:29
@ebyhr ebyhr removed their request for review October 24, 2024 06:08
Copy link

This pull request has gone a while without any activity. Tagging the Trino developer relations team: @bitsondatadev @colebow @mosabua

@github-actions github-actions bot added the stale label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant