Hi,
I have implemented a search, where all the facet's are offered as checkbox
style filters along with a fulltext search to first narrow down the result set.
For this I have implemented the search to run the fulltext search with the
facets. If additional checkbox filters have been deselected,
Hi,
maybe you would like to have a look at solr.ShingleFilterFactory [1] to
expand your autosuggest to more than one term.
-Sascha
[1]
http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.ShingleFilterFactory
Blargy wrote:
Thanks for your help and especially your analyzer..
Hi,
I'm not sure if debugQuery=on is a feasible solution in a productive
environment, as generating such extra information requires a reasonable
amount of computation.
-Sascha
Jon Baer wrote:
Does the standard debug component (?debugQuery=on) give you what you need?
Additionally, I don't think this gets us what we want with multiValued
fields. It tells if a multiValued field matched, but not which value
out of the multiple values matched. I am beginning to suspect that
this information can't be returned and we may have to restructure our
schema.
-Tim
On
On 2010-05-15 02:46, Blargy wrote:
Thanks for your help and especially your analyzer.. probably saved me a
full-import or two :)
Also, take a look at this issue:
https://issues.apache.org/jira/browse/SOLR-1316
--
Best regards,
Andrzej Bialecki
___. ___ ___ ___ _ _
Andrzej is this ready for production usage?
Hopefully in the future we can include user click through rates to boost
those terms/phrases higher
- This could be huge!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autosuggest-tp818430p819762.html
Sent from the Solr - User
Maybe I should have phrased it as: Is this ready to be used with Solr 1.4?
Also, as Grang asked in the thread, what is the actual status of that patch?
Thanks again!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Autosuggest-tp818430p819765.html
Sent from the Solr - User
Sorry my response wasn't to actually use debugQuery on for production it was
more of wondering if it (the component) gave you the insight data you were
looking for, on a side note Im also interested in this type of component
because there are a number of projects I have worked on recently where
Connection spooling is specified by the underlying apache commons
connection manager when you create the Server.
The SUSS does socket pooling by default and is the preferred way to do
concurrent indexing. There are some quirks in the Server
implementation set, and SUSS avoids them. Unless you are
Okay, I will do so in future, if another problem like this occurs.
At the moment, everything is fine after I followed your suggestions.
Kind regards
- Mitch
--
View this message in context:
http://lucene.472066.n3.nabble.com/Short-DismaxRequestHandler-Question-tp775913p820355.html
Sent from
Here's the problem with mixing dissimilar text: relevance. Your text
relevance depends on a document's delta with all other documents in
the index. If you index nothing but technical papers, searching a
technical term will find what you expect. If you mix technical papers
and movie titles, text
Can you provide us some more information on what you really want to do?
Like the examples in the wiki said, the returned value of the function query
is multiplied with the score - you can boost your returned value from the
function query, if you like to do so.
Kind regards
- Mitch
--
View this
One my tricks for studying a deep project is to look at bug
fixes/release notes/new features. Understanding one little bug fix
will cause you to learn a subset of the code. Once you have that
structure in your head, exploring more bugs features on the Jira
will fill out that structure.
Lance
On
There is a known problem (that I can't find at the moment) where an
uploaded file is retained while the next one is processed. When these
two successive files are both huge, the coexistence of two giant
causes an OOM.
Do you have this problem on the first file, second file, or at some time later?
Wait. If the default op is OR, I thought this query:
(+category:xyz +price:[100 TO *]) -category:xyz
meant with xyz and range, OR without xyz because without a plus or
minus, OR really means SHOULD (which, bizzarely, is not a keyword).
(+category:xyz +price:[100 TO *]) (-category:xyz)
Is this
The general recommendation is to watch the caches during normal user
searches and keep increasing the size until evictions start happening.
This may or may not work for your situation.
The problem is that the eviction rate does not show lifetime in
cache. So if 90% of the cache sits there
16 matches
Mail list logo