her?
Could you please provide us the output of your scores and your
Explanation's?
Regards,
Em
Am 22.02.2012 08:17, schrieb Yuval Kesten:
> Hi Em,
> 1. Regarding the performances - the similarity class (And my subtype as well)
> gets the IDF and TF and SQUARED SUMS calculations as inpu
I
get from the Explanation.
> Here is part of my code:
Could you provide us the code where you are setting the Similarity, please?
Kind regards,
Em
Am 21.02.2012 16:18, schrieb Yuval Kesten:
> Hi,
> I want to use Lucene with the following scoring logic:
> When I index my documents I want to
.
This should have the same impact on the min should match as a stopword, no?
What if I remove a stopword but add another token when synonyms come in?
Just some thoughts :).
Regards,
Em
Am 07.10.2011 19:37, schrieb Em:
> Hi Hoss,
>
> I read your article.
>
> I have to review t
Hi Hoss,
I read your article.
I have to review the solr-code but with the help of your pseudo-code I
think I understand what goes on now.
Thank you!
Regards,
Em
Am 05.10.2011 20:19, schrieb Chris Hostetter:
>
> : > Presumably this query would fail, since you've only got
obably Solr is
intelligent enough to reduce the parameter to the maximum value if it is
too large.
I'll wait a little bit, before reposting my question on the Solr list.
Regards,
Em
Am 05.10.2011 12:51, schrieb Ian Lea:
> Sorry - you did say StopFilter or SynonymFilter but I started talking
MM was set to 4 (too many), than this means all queries have to
match?
If so, what is the problem in Solr with Stopwords and the Dismax-Parser?
Regards,
Em
Am 05.10.2011 11:39, schrieb Uwe Schindler:
> Hi,
>
> The TooManyClausesException is thrown by BooleanQuery.add(Clause). Because
>
especially in Solr (since I am not sure, I am a little bit confused when
I made a code review).
Thank you!
Regards,
Em
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h
ad a little bit more about this contribution to compare it
with existing approaches in Solr.
Thanks!
Em
Am 22.09.2011 09:08, schrieb Shai Erera:
> Hi Mihai,
>
> thanks for clarifying the question. The facet module supports that quite
> easily actually. I've included a sample cod
er it would be better in sense of performance and in
sense of usability, if you refine your results as soon as a user decides
that he/she needs to add a new date-detail to the query.
Hope this helps,
Em
Am 21.09.2011 21:44, schrieb Mihai Caraman:
> 2011/9/21 Shai Erera
>
>> What d
Thanks, Erik.
If PhraseQuery does not keep track of all matching spans, how does it do
its work (in comparison to SpanNearQuery)?
Regards,
Em
Am 21.09.2011 19:52, schrieb Erik Hatcher:
> SpanNearQuery does more work than PhraseQuery - it keeps track of all
> matching spans, whereas Phras
Hi Erik,
could you explain why PhraseQuery performs better than SpanNearQuery?
Some time has passed since I read about it, however I think it was
exactly the other way round.
Thanks!
Em
Am 21.09.2011 15:56, schrieb Erik Hatcher:
> PhraseQuery suffices for the stated requirement of boost
Àkos,
have a look at SpanNearQuery. This is what you want.
If you own the 2nd Edition of Lucene in Action have a look at their
examples. It illustrates how to combine them with the classical queries.
Regards,
Em
Am 21.09.2011 13:46, schrieb Akos Tajti:
> Dear List,
>
> for m
Yes, it's part of Solr. And even in Solr there was no documentation in
the API - at last when I searched for it the last time.
Regards,
Em
Am 13.06.2011 12:56, schrieb Denis Bazhenov:
> It seems so. Interestingly I can't find any mentions of
> WordDelimiterTokenFilter using go
Hi,
sounds like the WordDelimiterTokenFilter from Solr, doesn't it?
Regards,
Em
Am 13.06.2011 12:06, schrieb Denis Bazhenov:
> Some time ago I need to tune our home grown search engine based on lucene to
> perform well on product searches. Product search is search where users come
r an own
parse()-method.
Please, let me know if you see some other possibilities.
Regards,
Em
--
View this message in context:
http://lucene.472066.n3.nabble.com/Telling-query-time-QueryParser-how-to-work-by-a-TokenFilter-tp3042678p3047408.html
Sent from the Lucene - Java Users mailing list archiv
.
I know that I need a customized queryParser. However I don't want to
reimplement all that stuff that already works just to make the parser aware
of a new attribute.
Can you point me to some methods or best-practices to jump into the
queryParsers implementation?
Regards,
Em
--
View thi
-container (I prefer Tomcat
over Jetty for production, but some people even say that Jetty is okay)
and that's it.
Regards,
Em
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail:
s for whatever reason, when restarting it and
reopening the index-writer: Does the IW deletes the flushed file, because it
is not mentioned in the segmentInfo - file or how does Lucene handle this
internally?
Regards,
Em
--
View this message in context:
http://lucene.472066.n3.nabble.com/NRT-consis
dex-directory and to consume those differences to keep indices consistent.
How is this possible within a NRT-System? Is there any possibility to
consume snapshots of the internal buffer of the index writer to send them to
the slave?
Regards,
Em
--
View this message in context:
http://lucene.4720
19 matches
Mail list logo
