On 2/21/2015 6:33 PM, Walter Underwood wrote:
> Never do POST for a read-only request. Never. That only guarantees that you
> cannot reproduce the problem by looking at the logs.
>
> If your design requires extremely long GET requests, you may need to re-think
> your design.
I agree with those
Am an expert? Not sure, but I worked on an enterprise search spider and search
engine for about a decade (Ultraseek Server) and I’ve done customer-facing
search for another 6+ years.
Let the server reject URLs it cannot handle. Great servers will return a 414,
good servers will return a 400, br
On 2/21/2015 1:46 AM, steve wrote:
> Careful with the GETs! There is a real, hard limit on the length of a GET url
> (in the low hundreds of characters). That's why a POST is so much better for
> complex queries; the limit is in the hundreds of MegaBytes.
The limit on a GET command (including th
ot;
> From: wun...@wunderwood.org
> Subject: Re: Performing DIH on predefined list of IDS
> Date: Sat, 21 Feb 2015 09:50:46 -0800
> To: solr-user@lucene.apache.org
>
> The HTTP protocol does not set a limit on GET URL size, but individual web
> servers usually do. You should get a r
gt;
>> Date: Sat, 21 Feb 2015 01:42:03 -0700
>> From: osta...@gmail.com
>> To: solr-user@lucene.apache.org
>> Subject: Re: Performing DIH on predefined list of IDS
>>
>> Yes, you right, I am not using a DB.
>> SolrEntityProcessor is using a GET method
And I'm familiar with the setup and configuration using Python, JavaScript, and
PHP; not at all with Java.
> Date: Sat, 21 Feb 2015 01:52:07 -0700
> From: osta...@gmail.com
> To: solr-user@lucene.apache.org
> Subject: RE: Performing DIH on predefined list of IDS
>
> Tha
That's right, but I am not sure that if it is works with Get I will able to
use Post without changing it.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Performing-DIH-on-predefined-list-of-IDS-tp4187589p4187838.html
Sent from the Solr - User mailing list archi
> To: solr-user@lucene.apache.org
> Subject: Re: Performing DIH on predefined list of IDS
>
> Yes, you right, I am not using a DB.
> SolrEntityProcessor is using a GET method, so I will need to send
> relatively big URL ( something like a hundreds of ids ) hope it will be
>
from any point in case of failure.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Performing-DIH-on-predefined-list-of-IDS-tp4187589p4187835.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 2/20/2015 3:46 PM, Shawn Heisey wrote:
> If the URL parameter is "idlist" then you can use
> ${dih.request.idlist} in your SELECT statement.
I realized after I sent this that you are not using a database ... the
list would simply go in the query you send to the other server. I don't
know wheth
On 2/20/2015 2:57 PM, SolrUser1543 wrote:
> That's the reason that I want to run on predefined list of IDs.
> In this case I will able to restart from any point and to know about filed
> IDs.
You can include information on a URL parameter and then use that URL
parameter inside your dih config.
6.n3.nabble.com/Performing-DIH-on-predefined-list-of-IDS-tp4187589p4187753.html
Sent from the Solr - User mailing list archive at Nabble.com.
... )
>
> The question is what do you think about it? Or all of this could be done
> another way and I am trying to reinvent the wheel?
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Performing-DIH-on-predefined-list-of-I
S . (
> like id:(1 2 3 ... 100) then id:(101 102 ... 200) etc... )
>
> The question is what do you think about it? Or all of this could be done
> another way and I am trying to reinvent the wheel?
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Performing-DIH-on-predefined-list-of-IDS-tp4187589.html
> Sent from the Solr - User mailing list archive at Nabble.com.
ucene.472066.n3.nabble.com/Performing-DIH-on-predefined-list-of-IDS-tp4187589.html
Sent from the Solr - User mailing list archive at Nabble.com.
15 matches
Mail list logo
