[
https://issues.apache.org/jira/browse/SOLR-15733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622456#comment-17622456
]
Houston Putman commented on SOLR-15733:
---------------------------------------
> we will still include a handful of TupleStream implementations in
> solrj-streaming for backcompat.
I just don't find it very useful to have an artifact that holds a few classes
and no additional dependencies in our ideal end-state.
> There has been enough pushback on this sitting in the main solrj jar that
> I've basically stopped working on it.
So I can think of two reasons for pushback:
* If you want to introduce new mathy libraries that we don't want in SolrJ,
then this is probably a good step.
* If people are complaining about excessive SolrJ work being done then I think
it's just a ridiculous complaint and we can solve the dispute without a code
change. We have a plan to move streaming out of SolrJ near the end of Solr 9,
close to when Solr 10 is cut. As long as we follow through on that plan, I
don't see how people could have any issues with you working on streaming
improvements while its still in SolrJ.
Overall I'm not going to veto this or anything, but overall I think there needs
to be a user-centered reason for splitting out solrj-streaming.
> Separate out a solrj-streaming module
> -------------------------------------
>
> Key: SOLR-15733
> URL: https://issues.apache.org/jira/browse/SOLR-15733
> Project: Solr
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Assignee: Joel Bernstein
> Priority: Major
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> The huge amount of streaming expression code under
> {{org.apache.solr.client.solrj.io}} package can be shipped as an optional
> jar. The {{solrj-jdbc}} (or {{solrj-sql}}) modules would then have a
> dependency on this...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
