oscerd opened a new pull request, #26078:
URL: https://github.com/apache/camel/pull/26078
The realtime consumer sets the document change type as a raw string literal:
```java
if (changeType != null) {
message.setHeader("CamelGoogleFirestoreChangeType", changeType.name());
}
```
Every other header the component reads or writes is a `@Metadata`-annotated
constant in
`GoogleFirestoreConstants`, so it reaches the component metadata. This one
is not: the generated
`google-firestore.json` documented 16 headers and this was not among them,
so the one header specific to
the realtime mode — the one telling the route whether a document was
`ADDED`, `MODIFIED` or `REMOVED` — was
invisible in the catalog, in the component documentation and in the
endpoint-DSL header accessors. The
literal has been there since the component was contributed in CAMEL-23020.
The constant is added and used. **The header name is deliberately
unchanged**: `CamelGoogleFirestoreChangeType`
is already emitted by the released component, so renaming it to match the
`...Response*` prefix of the other
consumer headers would break routes that read it today. Only the metadata is
new — no behaviour change, and
no upgrade-guide entry.
### On tests
There is nothing behavioural to test here: the artifact this fixes is the
generated metadata, and that is
committed in this PR (`google-firestore.json` gains the header at index 14,
group `consumer`) and verified
by CI's own regeneration check. The existing 11 unit tests still pass.
### Verification
* `mvn clean install` on `components/camel-google/camel-google-firestore`,
green.
* Full reactor `mvn clean install -DskipTests -Dquickly`, green, with the
regenerated catalog mirror
committed.
* The endpoint-DSL header accessors were regenerated with
`mvn generate-sources -pl camel-componentdsl,camel-endpointdsl`, since the
`regen` profile that produces
them is disabled by `-Dquickly`.
---
_Claude Code on behalf of oscerd_
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
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]
