lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Jelsma <markus.jel...@openindex.io>
Subject RE: /select changes between 4 and 5
Date Wed, 24 Feb 2016 16:21:09 GMT
Re: POST in general still works for queries... I just verified it: 

This is not supposed to change i hope? We rely on POST for some huge automated queries. Instead
of constantly increasing URL length limit, we rely on POST.

Regards,
Markus

-----Original message-----
> From:Yonik Seeley <yseeley@gmail.com>
> Sent: Wednesday 24th February 2016 17:06
> To: solr-user@lucene.apache.org
> Subject: Re: /select changes between 4 and 5
> 
> POST in general still works for queries... I just verified it:
> 
> curl -XPOST "http://localhost:8983/solr/techproducts/select" -d "q=*:*"
> 
> Maybe it's your content-type (since it seems like you are posting
> Python)... Were you using some sort of custom code that could
> read/accept other content types?
> 
> -Yonik
> 
> 
> On Wed, Feb 24, 2016 at 8:48 AM, Mike Thomsen <mikerthomsen@gmail.com> wrote:
> > With 4.10, we used to post JSON like this example (part of it is Python) to
> > /select:
> >
> > {
> >     "q": "LONG_QUERY_HERE",
> >     "fq": fq,
> >     "fl": ["id", "title", "date_of_information", "link", "search_text"],
> >     "rows": 100,
> >     "wt": "json",
> >     "indent": "true",
> >     "_": int(time.time())
> > }
> >
> > We just upgraded to 5.4.1, and now we can't seem to POST anything to
> > /select. I tried it out in the admin tool, and it only does GET operations
> > against /select (tried changing it to POST and moving query string to the
> > body with Firefox dev tools, but that failed).
> >
> > Is there a way to keep doing something like what we were doing or do we
> > need to limit ourselves to GETs? I think our queries are all small enough
> > now for that, but it would helpful to know for planning.
> >
> > Thanks,
> >
> > Mike
> 

Mime
View raw message