Federico Mariani created CAMEL-24047:
----------------------------------------

             Summary: camel-sql - verifyTableName rejects schema-qualified 
aggregation repository names (unreleased regression)
                 Key: CAMEL-24047
                 URL: https://issues.apache.org/jira/browse/CAMEL-24047
             Project: Camel
          Issue Type: Bug
          Components: camel-sql
            Reporter: Federico Mariani


The table-name validation added to JdbcAggregationRepository in December 2025 
(commit 1d2568f00236, unreleased) checks the repository name against 
{{[a-zA-Z_][a-zA-Z0-9_]*}}. This rejects schema-qualified names such as 
{{myschema.aggregation}}, quoted identifiers, and names starting with a digit - 
all of which worked before. The failure is thrown from {{verifyTableName}} at 
first use ({{doStart}} row count, {{add()}}, {{get()}}), not at configuration 
time, and {{getRepositoryNameCompleted()}} inherits the problem.

Existing configurations pointing the repository at a non-default schema will 
break when 4.22 is released, and there is no upgrade guide entry.

Suggested fix: allow an optional schema qualifier (e.g. 
{{([a-zA-Z_][a-zA-Z0-9_]*\.)?[a-zA-Z_][a-zA-Z0-9_]*}}), and document the 
restriction in the 4.22 upgrade guide.

Reproducer attached: JdbcAggregationRepositorySchemaQualifiedNameTest.java (H2) 
- fails on current main with {{IllegalArgumentException: Invalid repository 
name: myschema.camel_agg}}; must pass after the fix.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to