-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[Protocol Change] Protocol RFC for Table Redirect #4507
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
base: master
Are you sure you want to change the base?
Conversation
|
||
* **RedirectWriterOnly**: | ||
When enabled, redirectable clients must redirect both reads and writes. For non-redirectable clients, | ||
**reads from the source table are still allowed**, but **writes are blocked**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can clients "optionally" decide to redirect to target tables for reads?
|
||
* **State**: Indicates the status of the redirect. While the exact values are implementation-specific, the following | ||
high-level states are recommended: | ||
* `IN-PROGRESS`: The redirect is being set up. No redirect is performed. The source table is still readable but not writable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not writable -> except for updating this state to "READY"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I think below engine responsibilities address this?
**reads from the source table are still allowed**, but **writes are blocked**. | ||
|
||
Redirect is enabled and configured at the source table via the corresponding Delta table properties: | ||
`redirectReaderWriter` and `redirectWriterOnly`. These are JSON strings specific to the implementation, but they should |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any example JSON?
Which Delta project/connector is this regarding?
Description
Add the protocol change proposal for the redirect table features (see #3702) to the RFC folder. This PR replaces #3705.
How was this patch tested?
n/a
Does this PR introduce any user-facing changes?
No.