[ 
https://issues.apache.org/jira/browse/CAMEL-26703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on CAMEL-26703 started by shashank.
----------------------------------------
> camel-sql - docs: fix recoveryByInstance name, default createString and 
> orphan lock conditions
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26703
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26703
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-sql
>            Reporter: shashank
>            Assignee: shashank
>            Priority: Minor
>
> Small fixes in {{sql-component.adoc}}:
> * The Clustering section says the property {{recoverByInstance}} must be set 
> to true. The property of {{ClusteredJdbcAggregationRepository}} is 
> {{recoveryByInstance}} ({{setRecoveryByInstance}}). The documented name does 
> not exist.
> * The options table of the JDBC idempotent repository shows the default 
> {{createString}} as {code}CREATE TABLE CAMEL_MESSAGEPROCESSED (processorName 
> VARCHAR(255),messageId VARCHAR(100), createdAt TIMESTAMP){code} without a 
> key. The code default ({{JdbcMessageIdRepository.DEFAULT_CREATE_STRING}}) and 
> the schema shown earlier on the same page have {{PRIMARY KEY (processorName, 
> messageId)}}, and the page says this constraint is what stops two concurrent 
> consumers from both adding the same key. A table created from the table row 
> lets two nodes both add the same message id.
> * The Orphan Lock section has the two conditions swapped: a lock whose 
> {{createdAt}} is at or after {{now - lockMaxAgeMillis}} is held by an active 
> instance, an older one is taken over ({{queryForInt}} and {{insert}} of 
> {{JdbcOrphanLockAwareIdempotentRepository}}). The page says the opposite.
> * The options table does not list {{clearString}}.
> Fix: use {{recoveryByInstance}}, show the code default with the primary key 
> in the options table, add {{clearString}}, and swap the two orphan lock 
> conditions. The catalog copy of the page is updated too.
> _Filed with Claude Code on behalf of allthingssecurity._



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to