oscerd opened a new pull request, #26014:
URL: https://github.com/apache/camel/pull/26014
Backport of #26007 to `camel-4.22.x`.
Straight cherry-pick of `e143e48790f1` — applied with no conflicts and no
manual edits.
## What it does
The `google-bigquery-sql` endpoint accepts two placeholder forms that behave
differently: `@name` is bound as a BigQuery named query parameter, while
`${name}` is spliced into the query text verbatim. Both are needed, because
BigQuery named parameters can bind values but cannot bind identifiers, so a
dataset or table name can only be supplied through `${name}`.
The documentation described `${name}` only as "extracted from message
headers and formed the translated query", which does not convey that the
substitution is literal text rather than parameter binding, and gave no
guidance to use `@name` for values.
This adds a `Query Placeholders` section documenting the split, and reports
at WARN level when a `${name}` substitution does not have the shape of a
BigQuery identifier. Only the placeholder name is logged, never the substituted
value.
The substitution behaviour itself is unchanged, so no upgrade-guide entry is
needed (and per project convention upgrade guides live on `main` regardless).
## Verification
- Cherry-pick clean, 5 files, +195 −8.
- The regenerated catalog doc copy is byte-identical to the component doc,
so it matches what a build regenerates — no regen drift.
- Module build green: 9 unit tests, 0 failures.
_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]
