[cdc] Time related computed functions support to handle epoch time #2989
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yuzelin
changed the title
JingsongLi
reviewed
Mar 12, 2024
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><h5>year(time-column [, time-unit])</h5></td> |
There was a problem hiding this comment.
Can you find some other systems to refer to?
There was a problem hiding this comment.
Refer to Flink TO_TIMESTAMP_LTZ(numeric, precision), using precision as argument.
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Current time expressions can only handle DATE and TIMESTAMP.
This PR aims to support handle numeric value as epoch time.
Tests
API and Format
For example:
time-unit: second (default), millis, micros, nanos
Documentation
CDC Ingestion -> Computed Functions