-
Notifications
You must be signed in to change notification settings - Fork 577
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
Add system column rw_timestamp
for any tables
#11629
Comments
This issue has been open for 60 days with no activity. If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the You can also confidently close this issue as not planned to keep our backlog clean. |
Some additions: they can only be referenced by a batch query and not by a streaming query. |
|
Sorry, please ignore them. Let's start from |
The requirements come from the debugging and trouble shooting for the tricky bugs such as https://risingwave-labs.slack.com/archives/C048771BGKF/p1691736276987669?thread_ts=1691732764.258889&cid=C048771BGKF |
rw_timestamp
for any tables
Is your feature request related to a problem? Please describe.
Expose
rw_timestamp
on any tables.Because our subscription already exposed a timestamp
rw_timestamp
based on epoch, I think there isn’t any concern about exposing the internal epoch using a hidden column.Besides, I think vnode and epoch is also useful in some cases. How about do them together?
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
Slack discussion https://risingwave-labs.slack.com/archives/C048771BGKF/p1691737477347599?thread_ts=1691732764.258889&cid=C048771BGKF
The text was updated successfully, but these errors were encountered: