[
https://issues.apache.org/jira/browse/SOLR-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945432#comment-16945432
]
Jan Høydahl edited comment on SOLR-13661 at 10/6/19 7:30 PM:
-------------------------------------------------------------
{quote}New features can be introduced in any release, irrespective of how big a
feature is
{quote}
Of course. But being a totally new way of distributing Solr and having huge
impact on the whole user and wider dev community, I think it makes totally
sense to introduce pkg mgmt in a major release as beta, and use the following
releases to adjust and settle the APIs and solicit feedback from 3rd party
plugin devs etc. But I agree that, if handled carefully and labeled
"experimental", we may introduce this in a series of 8.x point releases, and
perhaps start moving features from core into packages in master, targeting a
slim solr-core in 9.0, which is a major "feature" in itself.
{quote}This change is not backward incompatible or it does not affect users of
current versions
{quote}
In an earlier comment you said:
{quote}This new design totally disallows per core classloaders. This can be a
problem for users who use Solr with core level libs
{quote}
Can you elaborate on that? Is it simply so that a collection using packages
cannot also use "<lib>"? Of course there is a simple cure, to move those <lib>
jars into SOLR_HOME/lib but it could also be an argument to wait until 9.0 and
remove <lib> support at the same time...
was (Author: janhoy):
{quote}New features can be introduced in any release, irrespective of how big a
feature is
{quote}
Of course. But being a totally new way of distributing Solr and having huge
impact on the whole user and wider dev community, I think it makes totally
sense to introduce pkg mgmt in a major release as beta, and use the following
releases to adjust and settle the APIs and solicit feedback from 3rd party
plugin devs etc. But I agree that, if handled carefully and labeled
"experimental", we may introduce this in a series of 8.x point releases, and
perhaps start moving features from core into packages in master, targeting a
slim solr-core in 9.0, which is a major "feature" in itself.
{quote}This change is not backward incompatible or it does not affect users of
current versions
{quote}
You mentioned that "<lib>" is incompatible with your class loader work. Can you
elaborate on that? Is it simply so that a collection using packages cannot also
use "<lib>"?
> A package management system for Solr
> ------------------------------------
>
> Key: SOLR-13661
> URL: https://issues.apache.org/jira/browse/SOLR-13661
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Ishan Chattopadhyaya
> Priority: Blocker
> Labels: package
> Attachments: plugin-usage.png, repos.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Here's the design doc:
> https://docs.google.com/document/d/15b3m3i3NFDKbhkhX_BN0MgvPGZaBj34TKNF2-UNC3U8/edit?usp=sharing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
