[
https://issues.apache.org/jira/browse/SOLR-16158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524493#comment-17524493
]
Eric Pugh commented on SOLR-16158:
----------------------------------
Is this really such a breaking change that it has to wait for a major version?
10.0 is (guessing) 12 to 18 months away, are we really doing our users a
service by saying that this couldn't happen in the 9.x line? I hate to see
some fairly obvious improvements to what seem fairly "internal" to Solr take
forever to come to fruition.
If you use the embedded Solr, and you are upgrading versions, well it moving
around or being renamed is probably okay and not a big deal. I think the back
compat really comes into play when we are changing API's or query syntaxs and
maybe we should be freer even then to make changes!
> Separate Solr Embedded from solr-core
> -------------------------------------
>
> Key: SOLR-16158
> URL: https://issues.apache.org/jira/browse/SOLR-16158
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Embedded
> Affects Versions: main (10.0)
> Reporter: Houston Putman
> Priority: Major
>
> Solr Embedded is a very useful way of running Solr within an application or
> test.
> However, it does not really need to be included in Solr Core. It should be in
> a separate module under {{/solr/embedded}}, so that Solr Core does not need
> to depend on Jetty Server jars.
> This can only really go into 10.0, since it will be a breaking change.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
