Thanks. He was right.
I've noticed that the HTTPClient has no connection timeout
(http://jakarta.apache.org/commons/httpclient/preference-api.html#HTTP_connection_parameters)
setted, maybe there is a way to set it out-of-the-client (any
suggestion?), but it would help this connection timeout to be
: Has anyone thought of adding the docsum time to the qtime or possibly
: adding separate timing information for the real 'solr query time'.
it's pretty much impossible to include in the response a value which
indicates the total amount of time needed to generate the response...
1) the response
On 8-Jun-07, at 10:57 AM, Will Johnson wrote:
Has anyone thought of adding the docsum time to the qtime or possibly
adding separate timing information for the real 'solr query time'.
While my bosses are very pleased that most searches seem to take
~5ms it
does seem a bit misleading.
docsum
Has anyone thought of adding the docsum time to the qtime or possibly
adding separate timing information for the real 'solr query time'.
While my bosses are very pleased that most searches seem to take ~5ms it
does seem a bit misleading.
I'll take a crack at a patch unless there is a reason not to
On 3/22/07, Thierry Collogne (JIRA) <[EMAIL PROTECTED]> wrote:
I think that is all. If I forgot something, post it here. One remark. The
setHighlightSurroundingTags method can only take simple tags,
no tags containing quotes or such.
Out of curiosity, why is this? Solr should be able to handl
On 1/25/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: IMO, we should strive to be nice and not repeat keys when the
: NamedList is more of the Map variety than the List.
we should try .. but we can't garuntee .. i don't have any compelling
cases where i've needed to reuse the same name, but
: IMO, we should strive to be nice and not repeat keys when the
: NamedList is more of the Map variety than the List.
we should try .. but we can't garuntee .. i don't have any compelling
cases where i've needed to reuse the same name, but i've certainly written
plenty of code that puts multiple
On 1/25/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I'm using a slightly modified version of the json.org code. It stores
: things in a LinkedHashMap (to maintain order) and formats dates
: explicitly.
Uh... watch out with that ... a LinkedHashMap is first and for most a Map,
so it doesn't
: > > * I'm using wt=JSON rather then XML. (It maps to a hash easier)
: I'm using a slightly modified version of the json.org code. It stores
: things in a LinkedHashMap (to maintain order) and formats dates
: explicitly.
Uh... watch out with that ... a LinkedHashMap is first and for most a Map
On 1/25/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
> > new SolrPing().process( server );
>
> doesn't
>
>server.ping();
>
> look cleaner?
>
I can't argue with you there!
I may be taking Hoss's point #4 on
https://issues.apache.org/jira/
On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
> new SolrPing().process( server );
doesn't
server.ping();
look cleaner?
I can't argue with you there!
I may be taking Hoss's point #4 on
https://issues.apache.org/jira/browse/SOLR-20#action_12464641 too
seriously. My revised version is
On Jan 24, 2007, at 6:53 PM, Ryan McKinley wrote:
new SolrPing().process( server );
doesn't
server.ping();
look cleaner?
//Ed
This might seem outlandish but have you considered modeling a server
instead of a client? Then you can send request messages to it and get
back response messages.
SolrSelectResponse response = server.select(selectOptions);
I like the model, but the I want to be able easily write a client f
On Jan 24, 2007, at 4:05 PM, Ken Krugler wrote:
SolrQueryResponse rsp = (SolrQueryResponse)client.process( req );
vs
SolrQueryResponse rsp = queryRequest.execute( client );
This might seem outlandish but have you considered modeling a server
instead of a client? Then you can send request mes
On 1/24/07, Ken Krugler <[EMAIL PROTECTED]> wrote:
Hi Ryan,
>The big API question/style i'm struggling with is
>
>SolrResponse rsp = client.process( req );
> vs
>SolrResponse rsp = req.execute( client ); // execute may not be the
>right word
>
>The first one is more natural, and is how things
Hi Ryan,
The big API question/style i'm struggling with is
SolrResponse rsp = client.process( req );
vs
SolrResponse rsp = req.execute( client ); // execute may not be the
right word
The first one is more natural, and is how things are actually
processed. The second one allows eliminates
> * I'm using wt=JSON rather then XML. (It maps to a hash easier)
Heh... I quickly checked out the code, but didn't see where you were parsing
the code, or where the JSONObject class referenced is.
Anyway, if you want the *best* JSON parser on the planet, check out
http://www.nabble.com/Apache-
17 matches
Mail list logo
