Try running the query you're using in DIH from command line on the DB host and
on the solr host to see what kind of times you get from the DB itself and from
the network, you're bottleneck might be there. If you find that's not it, take
a look at this post regarding high performance DIH imports
Thanks, Jonathan. Your explanation is very helpful.
Can you explain exactly what you mean by "phrases created from the entire
query"?
On Thu, Oct 7, 2010 at 7:13 PM, Jonathan Rochkind wrote:
> What you said in your own quoted message is correct. qs is slop applied to
> phrases explicitly in t
David, here is an example.
* Original query: foo bar baz
* "phrases created from the entire query": "foo bar baz"
Otis
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
Lucene ecosystem search :: http://search-lucene.com/
- Original Message
> From: David Boxenhorn
> To
With a brand new setup, per the demo/tutorial, with fields slightly changed in
the config and data, posting XML records results in a simple qiery being able
to find records.
But records imported via a plain jane DIH request can only be found using
'q=*:*' queries.
There's no filtering, token
The phrase that jumps out is "with fields slightly modified". I'm
guessing that your modifications are off by a little. Here's what
I'd check first:
1> check the case. Sometimes the DB <-> field link is case
sensitive.
2> Look in your index via the admin page and look at your actual
fields as repor
Thanks. This worked. Really appreciate the pointer.
~ Titash
Ahmet Arslan wrote:
list
On Mon, Oct 4, 2010 at 4:58 PM, Upayavira wrote:
> On Mon, 2010-10-04 at 00:25 +0530, Arunkumar Ayyavu wrote:
>> I'm looking at setting up multiple masters for redundancy (for index
>> updates). I found the thread in this link
>> (http://www.lucidimagination.com/search/document/68ac303ce8425506/mu
Thanks for answering on a Sunday :-)
What happens if the query returns extra fields that are not specified in the
config.xml?
And does the unque field have to be named 'id'?
Dennis Gearon
Signature Warning
It is always a good idea to learn from your own mistakes. It is usually
Walter Underwood wrote:
> I think this is a bad idea. The tf.idf algorithm will already put a higher
> weight on "hammers" than on "blue", because "hammers" will be more rare than
> "blue". Plus, you are making huge assumptions about the queries. In a search
> for "Canon camera", "Canon" is an a
Dennis,
The unique field does not have to be named "id".
Fields are specified in schema.xml. There is no config.xml, although there is
solrconfig.xml.
If a query is returning fields that you do not have defined in schema.xml, it's
time to stop working on weekends! ;) Seriously, though, that ca
Arun,
Yes, changing the solrconfig.xml to point to the new master could require a
restart.
However, if you use logical addresses (VIPs in the Load Balancer or even local
hostname aliases if you don't have a LB) then you just need to point those
VIPs/aliases to new IPs and the Solr slave won't h
h,
I am talking about the query for the DIH (Data Import Handler?) that
queries the database to find records/documents to index. We originally were
trying to import aout 20 fields, but have whittled down the schema file (my bad
calling in config) to only try a few fields.
I myself hav
Hi All,
I am currently working on a couple of bug fixes for the Solr PECL extension
that will be available in the next release 0.9.12 sometime this month.
http://pecl.php.net/package/solr
Documentation of the current API and features for the PECL extension is
available here
http://www.php.net/s
13 matches
Mail list logo
