: curl http://192.168.7.6:8080/solr0/update --data-binary
: 'deletequerynodeid:20/query/delete'
:
: i remember it is ok when i use solr 1.1
...
: HTTP Status 400 - missing content stream
please note the Upgrading from Solr 1.1 section of the 1.2 CHANGES.txt
file, which states...
The
Hi Hoss.
I've tried that yesterday using the same approach you just said (I've
created the base fields for any language with basic analyzers) and it worked
alright.
Thanks again for you time.
Regards,
Daniel
On 20/6/07 21:00, Chris Hostetter [EMAIL PROTECTED] wrote:
: So far it sounds
SOLR-215 support multiple indices on a single Solr instance. It does *not*
support searching of multiple indices at once (e.g. parallel search) and
merging of results.
This has nothing to do with NFS, though.
Otis
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy --
Hi Mike, Brian
Thanks for helping with this, and for clearing up my misunderstanding. Solr
the python module and Solr the package being two different things, I've got
you.
The issues I have are compounded by the fact that we're hovering between
using the Unicode branch of Django and the older
: Faceting on manufacturers and categories first and than present the
: corresponding facets might be used under some circumstances, but in my case
: the category structure is quite deep, detailed and complex. So when
: the user enters a query I like to say to him Look, here are the
:
I used Solr with indexes on NFS and I do not recommend it.
It was either 100 or 1000 times slower than local disc
for indexing, I forget which. Unusable.
This is not a problem with Solr/Lucene, I have seen the
same NFS performance cost with other search engines.
wunder
On 6/21/07 3:22 AM, Otis
Otis,
Thanks for the link and the work !
Maybe around september, I will need this patch, if it's not already
commit to the Solr sources.
I will also need multiple indexes searches, but understand that there is
no simple, fast and genereric solution in solr context. Maybe I should
lose solr
On 6/21/07, Frédéric Glorieux [EMAIL PROTECTED] wrote:
I will also need multiple indexes searches,
Do you mean:
1) Multiple unrelated indexes with different schemas, that you will
search separately... but you just want them in the same JVM for some
reason.
2) Multiple indexes with different
great, thanks Yonik.
On 6/20/07, Yonik Seeley [EMAIL PROTECTED] wrote:
On 6/21/07, Jeff Rodenburg [EMAIL PROTECTED] wrote:
As an aside, it would be nice to record these issues more granularly in
JIRA. Could we get a component created for our client library, similar
to
java/php/ruby?
Done.
Because score desc is the default Lucene Solr behavior when no explicit
sort is specified, QueryParsing.parseSort() returns a null sort so that the
non-sort versions of the query execution routines get called. However the
caller SolrPluginUtils.parseSort issues that warning whenever it gets a
A little background:
I originally conceived of query operation chains (based on some of my
previous hacking in mechanical investing stock screens: select all
stocks; take top 10% lowest PE; then take the top 20 highest growth
rate; then sort descending by 13 week relative strength).
So, I
Hi Sonic,
I will also need multiple indexes searches,
Do you mean:
2) Multiple indexes with different schemas, search will search across
all or some subset and combine the results (federated search)
Exactly that. I'm comming from a quite old lucene based project, called SDX
On 6/21/07, Frédéric Glorieux [EMAIL PROTECTED] wrote:
I will also need multiple indexes searches,
Do you mean:
2) Multiple indexes with different schemas, search will search across
all or some subset and combine the results (federated search)
Exactly that. I'm comming from a quite old
I just started running the scripts and
The commit script seems to run fine, but it says there was an error. I
looked into it, and the scripts expect 1.1 style response:
result status=0/result
1.2 /update returns:
?xml version=1.0 encoding=UTF-8?
response
lst name=responseHeader
Thanks Yonik to share your reflexion,
This doesn't sound like true federated search,
I'm affraid to not understand federated search, you seems to have a
precise idea behind the head.
since you have a number
of fields that are the same in each index that you search across, and
you treat
After further reading, especially
http://people.apache.org/~hossman/apachecon2006us/faceted-searching-with-solr.pdf
(Thanks Hoss)
Depending on update patterns and index sizes, you can probably get
better efficiency with multiple indexes, but not really more
functionality (in your case),
aha，，same question i found few days ago.
i m sorry to forget submit it.
2007/6/22, Yonik Seeley [EMAIL PROTECTED]:
On 6/21/07, Ryan McKinley [EMAIL PROTECTED] wrote:
I just started running the scripts and
The commit script seems to run fine, but it says there was an error. I
looked into
: I guess we should look for 'status=0' ?
that wouldn't quite work.
: Or, if you get a response code of 200, it's a success unless
: you see status=nonzero
we could always make it an option in the scripts.conf file -- what
substring to match on ... just in case people want to write their own
: generating XML feed file and feeding to the Solr server. However, I was
: also looking into implementing having sub-categories within the
: categories if that make sense. For example, in the shopper.com we have
: the categories of by price, manufactures and so on and with in them,they
: are
19 matches
Mail list logo
