lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noble Paul <noble.p...@gmail.com>
Subject Re: Breaking Java back-compat in Solr
Date Mon, 04 Jan 2016 17:37:04 GMT
IMHO
It's OK if the user has to go through recompile/modify their custom
component as long as it is obvious as to what is changed and we give
clear documentation on how to upgrade

On Mon, Jan 4, 2016 at 11:00 PM, Yonik Seeley <yseeley@gmail.com> wrote:
> On Mon, Jan 4, 2016 at 12:07 PM, Alexandre Rafalovitch
> <arafalov@gmail.com> wrote:
>> Solr plugin story is muddy enough as it is. Plugins are hard to find,
>> share. So, in my eyes, breaking them is not a big effect as if we had
>> a big active registry.
>
> I think private plugins / components are more the issue here (a custom
> qparser, search component, update processor).
> The basic question is: should people using these be able to upgrade
> from 5.4 to 5.5 without having to change and recompile their code?
>
> -Yonik
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>



-- 
-----------------------------------------------------
Noble Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message