Re: restlet dependencies

@Tim Potter I tried several times to get rid of the restlet dependency & keep the functionality as is. I failed miserably. I'm not saying this to discourage anyone who wants to give a try. Just letting you know that it is not as easy as it may sound On Thu, Oct 1, 2020 at 2:42 AM Houston Putman

Re: restlet dependencies

+1 to Tomas' proposal. Created SOLR-14907 to track the effort. - Houston On Wed, Sep 30, 2020 at 12:26 PM Tomás Fernández Löbbe < tomasflo...@gmail.com> wrote: > > Let's support the single file upload feature > +1, but let this behave exactly

Re: restlet dependencies

> Let's support the single file upload feature +1, but let this behave exactly as a zip file with a single file in it (regarding trusted/untrusted). We just need to change the configset handler to be able to handle non-zip files, and have a way to "locate" that file inside the configset (in case

Re: restlet dependencies

I think that me in “violent agreement” with you. Let’s understand the Annotations approach that we have, or pick something that is commonly used like JAX-RS / Jersey. > On Sep 30, 2020, at 11:41 AM, Timothy Potter wrote: > > I'm sorry, I don't understand what you mean by "make it a single

Re: restlet dependencies

I'm sorry, I don't understand what you mean by "make it a single pattern (the annotations?)" Eric? To me, the pattern is well established in the Java world: JAX-RS (with Jersey as the underlying impl. which has nice integration with Jetty). But when I suggested porting the code that uses restlet

Re: restlet dependencies

The use case of “I want to update something via a API” is I think pretty common, and it would be nice to make it a single pattern (the annotations?) with lots of examples/developer docs for the next person. > On Sep 30, 2020, at 11:04 AM, Timothy Potter wrote: > > I started looking into

Re: restlet dependencies

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

Re: 8.6.3 Release

The only one that was previously mentioned as a blocker was SOLR-14835, but from the comments on the ticket it looks like it ended up being purely a cosmetic issue. Andrzej left a comment there suggesting that we "address" this with documentation for 8.6.3 but otherwise leave it as-is. So it

Re: restlet dependencies

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

Re: restlet dependencies

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,

Re: restlet dependencies

>It is supported and documented: >https://lucene.apache.org/solr/guide/8_6/managed-resources.html I was referring to how the code works. Not how the feature works On Wed, Sep 30, 2020 at 7:46 PM Ishan Chattopadhyaya wrote: > > > * Nobody knows how it works. It's unsupported > It is supported

Re: restlet dependencies

Core reloads cause caches to be invalidated, hence the query response times shoot up momentarily. This doesn't happen when using managed synonyms etc, does it? On Wed, 30 Sep, 2020, 5:53 pm David Smiley, wrote: > Definitely don't remove in 8.x! > > > A single file configset upload would

Re: restlet dependencies

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

Re: restlet dependencies

> * 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

Re: restlet dependencies

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

Re: restlet dependencies

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

Re: restlet dependencies

Can we discuss this with ASF and get an exception for this? On Wed, 30 Sep, 2020, 11:57 am Dawid Weiss, 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 > wrote: > > > > Can we pull

Re: restlet dependencies

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 wrote: > > Can we pull in the jar inside our codebase? > > On Wed, 30 Sep, 2020, 1:19 am Dawid Weiss, wrote: >> >> >> We can upgrade if it doesn't break