oscerd opened a new pull request, #24909: URL: https://github.com/apache/camel/pull/24909
## Description Fixes [CAMEL-24200](https://issues.apache.org/jira/browse/CAMEL-24200). In `Timestream2QueryProducer.createScheduledQuery` the time-column header was written into the target configuration's **table name**: ```java if (ObjectHelper.isNotEmpty(exchange.getIn().getHeader(Timestream2Constants.TIME_COLUMN))) { String timeColumn = exchange.getIn().getHeader(Timestream2Constants.TIME_COLUMN, String.class); timestreamConfigBuilder.tableName(timeColumn); // should be .timeColumn(...) } ``` So the `timeColumn` (required on a scheduled-query target) was never set, and when `CamelAwsTimestreamTableName` was also supplied the time-column value silently **overwrote the table name** — creating the scheduled query against the wrong table, or having AWS reject it. Also removes a duplicated block that set `scheduledQueryExecutionRoleArn` twice from the same header. ## Tests Extends the existing `Timestream2QueryProducerTest.timestreamCreateScheduledQueryTest` (which already sent all three headers but only asserted the response ARN) to capture the `CreateScheduledQueryRequest` via the client mock and assert `databaseName`, `tableName` and `timeColumn` each come from their own header. Against the old code the table name would be `"time"` and the time column `null`, so the test fails without the fix. ## Backport Same code on `camel-4.18.x` and `camel-4.14.x`; will be backported after merge (fixVersions 4.22.0 / 4.18.4 / 4.14.9). --- _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]
