Hi all,
I can successfully get the commands through using curl utility but
when I try to use Apache's HttpClient's post method, then things start not
working well.
The results come back with an error code of 200 even while the xml results
that are streamed back has a status of 0. At the co
: The results come back with an error code of 200 even while the xml results
: that are streamed back has a status of 0. At the colr jar execution the
: console reads
:
: Apr 4, 2006 12:14:16 AM org.apache.solr.core.SolrCore update
: INFO: add 0 125.
200 indicates HTTP success, and the status of
> i added a call to core.close() to the end of your main function and the
> problem went away.
It worked. Thank you!
Koji
On 4/4/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
> i added a call to core.close() to the end of your main function and the
> problem went away.
>
> Aparently calling SolrCore.close() isn't just a good idea, it's
> neccessary. i'm not entirely sure why.
There is an Executor that the core uses
I would like to have highlighting of selected field(s) in Solr search
results. Certainly a custom request handler can do this, but I'm
curious if the standard handler and configuration should evolve to
handle the common need for search term highlighting, and if so how
would that ideally lo
On 4/4/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
> I would like to have highlighting of selected field(s) in Solr search
> results. Certainly a custom request handler can do this, but I'm
> curious if the standard handler and configuration should evolve to
> handle the common need for search ter
> It's probably best to focus on the ideal interface first (query
> parameters as input format, and desired XML output format).
We might also want to keep termvectors in mind when thinking about
this stuff... seems like they are related (per-field optional/extra
data).
-Yonik
Thanks a lot Chris,
Glad I didn't waste sleep over it.
-sam
Chris Hostetter wrote:
: My (our) query plugin uses specialized SolrCache's in lieu of the meta
: data records. For each new searcher installed each fields possible
: values will be determined and stored in a cache (off the top of my head,
Are you determining the field values based on all in
: What I'd really like to see is an XML query language so I can toss all
: the hackish URL query arguments and really move much of the query plugin
: logic out into the query itself instead of in the Java code.
: customers. We'll introduce dynamic attribute bucketing. Rather than
: produce a l
For the record, i know next to nothing about highlighting in Lucene. i
can't remember if i read that chapter in LIA or not :)
: curious if the standard handler and configuration should evolve to
: handle the common need for search term highlighting, and if so how
+1
: would that ideally look i
11 matches
Mail list logo
