I have a multicore solr with a lot of cores that contains a lot of data (~50M
documents), but are rarely used.
Can i load a core from configuration, but have keep it in sleep mode, where
is has all the configuration available, but it hardly consumes resources,
and based on a query or an update, it
britske wrote:
>
> just wanted to mention a possible other route, which might be entirely
> hypothetical :-)
>
> *If* you could query on internal docid (I'm not sure that it's available
> out-of-the-box, or if you can at all)
> your original problem, quoted below, could imo be simplified to ask
I'm in the process of indexing my demi data to test that, I'll have more
valid data on whether or not it made the differeve In a few days
Thanks
ב-23/07/2010, בשעה 19:42, "Jonathan Rochkind [via Lucene]" <
ml-node+990234-2085494904-316...@n3.nabble.com> כתב/ה:
> and a typical query would be:
>
I don't specify any sort order, and i do request for the score, so it is
ordered based on that.
My schema consists of these fields:
(changing now to tdate)
and a typical query would be:
fl=id,type,timestamp,score&start=0&q="Coca+Cola"+pepsi+-"dr+pepper"&fq=timestamp:[2010-07-07T00:00:00Z+T
Chris Hostetter-3 wrote:
>
> : updating your index between queries, so you may be reloading
> : your cache every time. Are you updating or adding documents
> : between queries and if so, how?
> :
> : If this is vaguely on target, have you tried firing up warmup queries
> : after you update your
1.I query my index once every 30 minutes. I save the timestamp of the newest
returned document. next time i query doe documents with timestamp between
the timestamp i saved from the previous query and NOW.
2.Sad to day it is not optimized, i'm at 60% of the disk space, and waiting
for another dis
my goal is to run a query and limit it with the timestamp of the last
document i found. will TrieDateField give me this precision? is there any
other way to achieve that?
i also see slow queries when using a filter on a field that is a simple
string(StrField), that has only 3 types of values, don
sorry for not mentioning it, we use solr 1.4.1
thanks again for any idea
--
View this message in context:
http://lucene.472066.n3.nabble.com/filter-query-on-timestamp-slowing-query-tp977280p977299.html
Sent from the Solr - User mailing list archive at Nabble.com.
I have a query that seems to be running much slower when i try to filter it.
the field is of type pdate (solr.DateField) and the filter is for example
timestamp:[2010-01-01T00:00:00Z TO NOW] (to look only for documents since
Jan 1st.
if i don't use the filter, the query returns pretty fast, but ad
that's actually what i already had in mind, just wasn't sure that specifying
the sort order of indextime eliminates the work of scoring.
--
View this message in context:
http://lucene.472066.n3.nabble.com/how-to-eliminating-scoring-from-a-query-tp968581p972325.html
Sent from the Solr - User mail
wrote:
> By specifying a sort that doesn't include score. I think it's just
> automatic
> then.
>
> It wouldn't make sense to eliminate scoring *without* sorting by some other
>
> field , you'd essentially get a random ordering.
>
>
> Best
>
in http://www.lucidimagination.com/files/file/LIWP_WhatsNew_Solr1.4.pdf
http://www.lucidimagination.com/files/file/LIWP_WhatsNew_Solr1.4.pdf under
the performance it mentions:
"Queries that don’t sort by score can eliminate scoring, which speeds up
queries"
how exactly can i do that? If i don't
Hey guys, a question about query multiple fields.
I would like to query my index with queries that contained some words that
should be stemmed and some that should not. For example, for the query:
Nike's new "running shoes", i would like to be able to get also nike, but
for "running shoes" i woul
13 matches
Mail list logo
