allthingssecurity commented on PR #29405: URL: https://github.com/apache/camel/pull/29405#issuecomment-6718966872
Thanks Claus. The doc points are in 05ac67c: - The YAML example now uses `org.apache.camel.processor.keyvalue.jdbc.JdbcKeyValueRepository`, as the Java example imports. The camel-jbang `eip-samples.json`, which is generated from the YAML examples of the EIP pages, had the same wrong class name, so it is changed too. - The backend table says ✓ (primary key) for JDBC, as the CAS table does and as the NOTE describes. - One sentence after the NOTE says that a TTL entry expires when a node reads it and compares its own clock with the `EXPIRES_AT` written by the node that stored it, so the nodes need synchronised clocks; a node whose clock runs ahead treats the entry as expired, and deletes it, too early. The catalog copy of the page is byte-identical to the source. The PR description no longer lists these as follow-ups. The two JIRAs, for the `JpaKeyValueRepository` fix and for an expiry-aware `replace` / `delete(key, expected)` in `JdbcKeyValueRepository`, will be filed and linked to CAMEL-26708; I'll add the keys to the description when they exist. _Claude Code on behalf of allthingssecurity_ -- 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]
