Thanks for all you advices and thoughts.
The client in our case is/are the tomcats. To be more precise the webapps
running in the tomcats. These should serve http request.
I'd also like to note that it's he batch-updates that in my opinion cause load
(cpu and memory (dependeing on the pdf))
https://issues.apache.org/jira/plugins/servlet/mobile#issue/LUCENE-2878
provides lucene API what you are trying to do, it's not yet in though.
There's a fork which has the change in
https://github.com/flaxsearch/lucene-solr-intervals
On 12 Sep 2014 21:24, Craig Longman clong...@iconect.com wrote:
Thanks for sharing, since in future Solr may move towards standalone server
this (undertow) could be one option.
On Sat, Sep 13, 2014 at 9:36 PM, William Bell billnb...@gmail.com wrote:
Can we get some stats? Do you have any numbers on performance?
On Sat, Sep 13, 2014 at 3:03 PM, Jayson
I have a collection with 200 fields and 300M docs running in cloud mode.
Each doc have around 20 fields. I now have a use case where I need to
replace these explicit fields with 6 dynamic fields. Each of these 200
fields will match one of the 6 dynamic field.
I am evaluating performance
Dynamic fields, once they are actually _in_ a document, aren't any
different than statically defined fields. Literally, there's no place
in the search code that I know of that _ever_ has to check
whether a field was dynamically or statically defined.
AFAIK, the only additional cost would be
*Erick*, thank you for help!
For exact match I still want:
to use stemming (e.g. for sleep I want the word forms slept, sleeping,
sleeps also to be used in searching)
to disregard case sensitivity
to disregard prepositions, conjunctions and other function words
to match only docs having all of the
FiMka wrote
After I disabled solr.StopFilterFactory for analyzer type=query Solr
stopped returning this document for the query:
http://localhost:8983/solr/lexikos/select?q=phraseExact%3A%22on+a+case-by-case%22.
Forgot to say, I have also disabled solr.StopFilterFactory for analyzer
type=index,
I keep asking people this eternal question: What training or doc are you
reading that is using this term exact match? Clearly the term is being
used by a lot of people in a lot of ambiguous ways, when exact should
be... exact.
I think we need to start using the term exact match ONLY for
Suppose I have the following fields :
text,author,title
users performs a query on all those fileds :
...?q=(text:XX OR author:XX OR title:XX)
if this query has a match in 'text' field , so highligter will generate a
hit preview based on this field , which is fine .
But suppose a query
Hi,
hl.alternateField and hl.maxAlternateFieldLength would be useful.
http://wiki.apache.org/solr/HighlightingParameters
Ahmet
On Sunday, September 14, 2014 9:35 PM, SolrUser1543 osta...@gmail.com wrote:
Suppose I have the following fields :
text,author,title
users performs a query on
How about perf if you dynamically create 5000 fields ?
Bill Bell
Sent from mobile
On Sep 14, 2014, at 10:06 AM, Erick Erickson erickerick...@gmail.com wrote:
Dynamic fields, once they are actually _in_ a document, aren't any
different than statically defined fields. Literally, there's no
Hi , thanks for the answer.
I tried to use this technique , but the desired result was not achieved.
Can you please provide an example of document to index and some sample query
?
--
View this message in context:
12 matches
Mail list logo
