oscerd commented on PR #3085:
URL: https://github.com/apache/camel-kamelets/pull/3085#issuecomment-6011585400

   Status check on the dependency, since I said I would re-test once 
CAMEL-25027 was in the snapshot.
   
   **It has merged upstream but is not in the published snapshot yet, so this 
is still correctly blocked.**
   
   apache/camel#27289 merged as `78e9ccbd27b4` at **2026-10-05 17:04**:
   
   ```
   CAMEL-25027: camel-langchain4j-ingest - Add media modality (#27289)
   +    private IngestModality modality = IngestModality.TEXT;
   +    private String contentType;
   ```
   
   The latest published `4.23.0-SNAPSHOT` of `camel-langchain4j-ingest` is 
build **19**, timestamped `20261005.103640` — 10:36 the same day, about six and 
a half hours *before* that merge. Its component catalog lists 15 properties and 
neither new one:
   
   ```
   pipelineName, documentIdHeader, embeddingBatchSize, embeddingModel, 
embeddingStore,
   maxOverlapSize, maxSegmentSize, lazyStartProducer, documentSplitter,
   idempotentRepository, maxDocumentSize, documentFilter, excludeId, includeId, 
...
   
   grep -c '"modality"'    -> 0
   grep -c '"contentType"' -> 0
   ```
   
   So the next snapshot deploy should unblock it. Nothing to do here but wait 
for that; the draft status is still right.
   
   Worth noting one thing the merged upstream change confirms about this PR: 
the component declares `modality` with `defaultValue = "TEXT"`. Since this 
Kamelet declares the property with no default and forwards it as 
`{{?modality}}`, an unset `modality` is omitted from the endpoint URI entirely 
and the component's own `TEXT` default applies. That is the right arrangement — 
the two defaults cannot drift, because the Kamelet does not restate one.
   
   I will re-run the new Citrus test once the option shows up in a published 
snapshot.
   
   ---
   _Claude Code on behalf of Andrea Cosentino_
   


-- 
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]

Reply via email to