We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to https://github.com/risingwavelabs/risingwave/blob/main/src/source/src/table.rs#L86, we may not know which writes will win when there are multiple ones. (pk conflict, and due to https://github.com/risingwavelabs/rfcs/pull/4/files#diff-73ca4924ee3c22e62b50a34acb513c5252bc3d5c44075d5b0398a2387f6d5c4dR32, the first writes win and the rest will be ignored)?
from the same session seems to be a reasonable setting
from the same session
The text was updated successfully, but these errors were encountered:
A quick but working workaround might be always scheduling the DML to a fixed node and choosing a fixed parallelism here. 🥵
Sorry, something went wrong.
https://github.com/risingwavelabs/rfcs/pull/4/files#diff-73ca4924ee3c22e62b50a34acb513c5252bc3d5c44075d5b0398a2387f6d5c4dR54 seems there was a plan
This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.
close in favor of #7213
No branches or pull requests
Due to https://github.com/risingwavelabs/risingwave/blob/main/src/source/src/table.rs#L86,
we may not know which writes will win when there are multiple ones.
(pk conflict, and due to https://github.com/risingwavelabs/rfcs/pull/4/files#diff-73ca4924ee3c22e62b50a34acb513c5252bc3d5c44075d5b0398a2387f6d5c4dR32, the first writes win and the rest will be ignored)?
from the same session
seems to be a reasonable settingThe text was updated successfully, but these errors were encountered: