atiaomar1978-hub commented on PR #25102: URL: https://github.com/apache/camel/pull/25102#issuecomment-5073703403
## Bugbot follow-up — addressed in c3a05971b30 Re-ran Bugbot on the branch and fixed all three reported findings: | Severity | Issue | Fix | |----------|-------|-----| | **High** | Published docs / upgrade guide still showed `duckdb:databasePath[/table]` (e.g. `duckdb:analytics.db/events`), which no longer matches the component and would build wrong JDBC URLs | Synced `docs/components/.../duckdb-component.adoc`, catalog docs copy, and the 4.22 upgrade-guide example to `duckdb:databasePath?table=...` | | **Medium** | `CamelDuckDbDatabasePath` was documented in catalog/constants but never read in `DuckDbProducer` | Producer now reads the header and opens a short-lived connection to the override path for that exchange | | **Medium** | Endpoint reused one JDBC `Connection` across concurrent route threads without synchronization | Added `DuckDbConnectionScope` + lock around the endpoint-owned shared connection for each producer invocation; DataSource and header-override connections remain per-call and are closed after use. Docs note preferring a shared `DataSource` for concurrent producers | **Tests:** `./mvnw -pl components/camel-duckdb test failsafe:integration-test` — 18 unit + 3 IT, all green (including `databasePathHeaderOverridesEndpointDatabase`). _Cursor on behalf of atiaomar1978-hub_ -- 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]
