Hi, Between 4.x and 4.x+1 version breaking changes are accepted, so if there is a breaking change is not something done as a mistake.
The reason for accepting breaking changes in this context, it's because we are dependant on too many 3rd parties library and so it Is possible to have breaking changes between dependency upgrades. We have migration guides for listing this kind of changes. Cheers Il lun 29 set 2025, 19:34 James Dyer <[email protected]> ha scritto: > I recently worked on a project involving Camel-Solr in which I forked > the component from Camel 4.9 to make necessary enhancements. I was > about to issue a PR to contribute back one of these enhancements. In > Camel 4.9, the Solr Component would always return a SolrDocumentList > when querying, whereas I needed the parent QueryResponse so that I > could access facets, etc. My PR would have introduced a new header > that allows users to specify which object to return. > > However, in preparing this PR I noticed that as of Camel 4.11, the > component seems to now always return the QueryResponse. Although this > is excellent news for my use-case, I wonder if this was an > unintentional backwards-incompatible change? >
