oscerd commented on PR #29839: URL: https://github.com/apache/camel/pull/29839#issuecomment-6912502765
Rebased on `main` (import conflict with CAMEL-26896 in `OpenFgaProducer`) and pushed `CAMEL-26842: Track only the streams that opened a request, label the stream options as producer options, and tidy the comments and docs` (47d0e0c4cf0f): - **Blocker, `activeStreams` growth**: the iterator now takes an `onOpen` callback next to `onClose`, and the producer registers an iterator only when `open()` actually starts the request; an iterator that is never iterated holds no connection and is never tracked, while opened streams are still closed on producer stop. `OpenFgaStreamedListObjectsTest.tracksOnlyIteratorsThatOpenedARequest` processes 25 exchanges without iterating and checks the set stays empty, then one that opens and closes. - The stale "Java 17 baseline" comment in `OpenFgaEndpoint.doStop` now says what is and is not closed. - `OpenFgaConfiguration`: the appended sentence of the `openFgaClient` description is wrapped and says a positive `readTimeout`; `streamMaxResults`, `streamMaxLineLength` and `streamingClient` are `producer,advanced`. - Imports instead of FQCNs in `OpenFgaStreamedListObjectsTest` and `OpenFgaIT`. - The streaming splitter example has a YAML tab. - The component JSON and its catalog copy are regenerated; the component and endpoint DSL factories follow from the CI regen step, since those generators need the whole reactor to run locally. The `addOnCompletion` alternative is left as documented behaviour (the iterator stays usable after the exchange), since the lazy registration removes the growth. Unit tests green locally. Heads-up kept: this and #29840 touch `OpenFgaConfiguration` and the generated files; the second to merge gets a rebase. _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]
