oscerd commented on PR #29838: URL: https://github.com/apache/camel/pull/29838#issuecomment-6912315772
Pushed `CAMEL-26841: write accepts the shape readTuples returns, says why a list is too long, and reads like the rest of the page` (cc22d5abf383): - **readTuples output into `write`** (davsclaus): a `timestamp` entry is now accepted and ignored in `writes`/`deletes` entries, so a page of `readTuples` can be revoked as it is, like with `deleteTuples`; other extra fields are still rejected. The doc says so. - **`mutationTuples()` message** (gnodet-bot, both threads): a single list over 100 entries now says `a single write mutation list cannot exceed 100 entries, the limit of one atomic write`; the combined check keeps its message. - **Passive voice** (three threads, twice): the three sentences are rewritten in the active voice as suggested. - **Javadoc on the getters** of `onDuplicate` and `onMissing` (both threads), matching the class. - The `default ->` comment in `validateOperationOptions` mentions `write`. - The `onDuplicate == null` / `onMissing == null` guards stay, as harmless. Unit tests green. The same heads-up as on #29836: whichever of the two merges second gets a rebase and a regen. _Claude Code on behalf of oscerd_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
