I started looking into removing Managed Resources in master and wanted to mention that the LTR contrib also relies on this framework (ManagedModelStore and ManagedFeatureStore, see: https://lucene.apache.org/solr/guide/8_6/learning-to-rank.html#uploading-a-model). I only mention this b/c it's been said several times in this thread that nobody uses this feature and it's only for editing config/schema like synonyms. Afaik, LTR is a broadly used feature of Solr so now I'm not so bullish on removing the ability to manage dynamic resources using a REST like API. I agree that changing resources like the synonym set could be replaced with configSet updates but I don't see how to replace the RESTful model / feature store API w/o something like Managed Resources?
>From where I sit, I think we should just remove the use of restlet in the implementation but keep the API for Solr 9 (master). @Ishan ~ you mentioned there is a way to get REST API like behavior w/o using JAX-RS / Jersey ... something about annotations? Can you point me to some example code of how that is done please? Cheers, Tim On Wed, Sep 30, 2020 at 8:29 AM David Smiley <[email protected]> wrote: > These resources are fundamentally a part of the configSet and can (in > general) affect query results and thus flushing caches (via a reload) is > appropriate. > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Wed, Sep 30, 2020 at 9:06 AM Noble Paul <[email protected]> wrote: > >> Well, I believe we should have a mechanism to upload a single file to >> a configset. >> >> > A single file configset upload would require the user to reload the >> collection, so it isn't better than managed resources. >> >> This is not true >> >> Only config/schema file changes result in core reload. >> >> On Wed, Sep 30, 2020 at 10:23 PM David Smiley <[email protected]> wrote: >> > >> > Definitely don't remove in 8.x! >> > >> > > A single file configset upload would require the user to reload the >> collection, so it isn't better than managed resources. >> > >> > Do you view that as a substantial point in favor of managed-resources? >> I view that as a trivial matter, and one I prefer to automagic and >> potentially premature reload if there are additional edits to be done (e.g. >> query-elevation or other word lists). >> > >> > ~ David Smiley >> > Apache Lucene/Solr Search Developer >> > http://www.linkedin.com/in/davidwsmiley >> > >> > >> > On Wed, Sep 30, 2020 at 5:46 AM Ishan Chattopadhyaya < >> [email protected]> wrote: >> >> >> >> > * Nobody knows how it works. It's unsupported >> >> It is supported and documented: >> https://lucene.apache.org/solr/guide/8_6/managed-resources.html >> >> >> >> > * RESTlet dependency >> >> > * Cannot be secured using standard permissions >> >> > * It's extremely complex for the functionality it offers. >> >> >> >> I agree. Whatever alternative we build should address these, before we >> consider removing managed resources. >> >> >> >> On Wed, Sep 30, 2020 at 2:52 PM Ishan Chattopadhyaya < >> [email protected]> wrote: >> >>> >> >>> The managed resources is the only reasonable way to upload synonyms >> on the fly for users today. A single file configset upload would require >> the user to reload the collection, so it isn't better than managed >> resources. I would not recommend we remove the functionality without first >> building a suitable alternative. I agree that the feature isn't built using >> proper framework or proper APIs, but it is a feature that works well. >> >>> >> >>> Usually, I support throwing features out even without existence of an >> alternative, but I do that for non essential features. In my mind, ability >> to manage synonyms elegantly is an essential feature for a search engine. >> >>> >> >>> On Wed, 30 Sep, 2020, 2:44 pm Uwe Schindler, <[email protected]> wrote: >> >>>> >> >>>> Please don't do this. >> >>>> >> >>>> In short: remove restlet stuff from master. Pull requests on master >> are executed with Gradle on GitHub hardware. >> >>>> >> >>>> Ivy stuff in 8.x is built in more or less persistent servers and >> there is no issue. >> >>>> >> >>>> What's the problem? >> >>>> >> >>>> Uwe >> >>>> >> >>>> Am September 30, 2020 8:59:06 AM UTC schrieb Ishan Chattopadhyaya < >> [email protected]>: >> >>>>> >> >>>>> Can we discuss this with ASF and get an exception for this? >> >>>>> >> >>>>> On Wed, 30 Sep, 2020, 11:57 am Dawid Weiss, <[email protected]> >> wrote: >> >>>>>> >> >>>>>> We can't have or redistribute binaries in ASL sources - that's my >> understanding. >> >>>>>> >> >>>>>> Dawid >> >>>>>> >> >>>>>> On Tue, Sep 29, 2020 at 10:02 PM Ishan Chattopadhyaya >> >>>>>> <[email protected]> wrote: >> >>>>>> > >> >>>>>> > Can we pull in the jar inside our codebase? >> >>>>>> > >> >>>>>> > On Wed, 30 Sep, 2020, 1:19 am Dawid Weiss, < >> [email protected]> wrote: >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> We can upgrade if it doesn't break anything... which I can't >> guarantee. ;) >> >>>>>> >> >> >>>>>> >> Dawid >> >>>>>> >> >>>>>> >> --------------------------------------------------------------------- >> >>>>>> To unsubscribe, e-mail: [email protected] >> >>>>>> For additional commands, e-mail: [email protected] >> >>>>>> >> >>>> >> >>>> -- >> >>>> Uwe Schindler >> >>>> Achterdiek 19, 28357 Bremen >> >>>> https://www.thetaphi.de >> >> >> >> -- >> ----------------------------------------------------- >> Noble Paul >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
