Hi Karl,
the Solr output connector does not seem to work with Solr 9.x according
to our tests. We are going to either update or develop a new connector
but there is a problem concerning the libraries required. A solr 9.x
connector will of course involve a solrj 9.x lib but also the update of
the following libs in MCF:
- zookeeper from 3.4.10 to >= 3.7.0 (current 3.8.0)
- httpcomponent.httpclient.version from 4.5.3 to 4.5.13
- httpcomponent.httpcore.version from 4.4.6 to 4.4.15
- httpcomponent.httpmime.version from 4.5.3 to 4.5.13
Those updates should not cause problems to other connectors in MCF, the
real problem here concerns the current Solr connector as I am not sure
that an updated version would be compatible with a Solr < 9.x.
There is also the modified solr clients using the custom multi-parts
http post methods that will cause some troubles to be ported on Solrj 9
.x according to me.
If I am not wrong, historically those custom clients were developed to
avoid errors with the embedded Tika of Solr for some documents. But
IMHO, it has become a challenge that is not worth the effort: the way to
go should be to have the documents processed by Tika BEFORE the Solr
indexation. Not to mention that the tika embedded in Solr is too old
(1.28.1) and will most certainly be removed someday (as stated in this
tickethttps://issues.apache.org/jira/browse/SOLR-13973). Thus, I think
it is not worth it to port the custom solr clients in the new connector.
This would ease the creation of the Solr 9 output connector.
Whatever happens, if we want to maintain output connectors for different
versions of Solr, and IF the Solr 9 output connector is not compatible
with previous versions of Solr (still needs to be checked), we'll end up
with several versions of the libs in ManifoldCF. To be honest, I do not
see a proper way to deal with the libs conflicts between the two
connectors...
What do you think ?
Regards,
Julien
