Hi
I need help porting my lucene code from 4 to 5. In particular, I need to
customize a collector (to collect all doc Ids in the index - which can be
>30MM docs..). Below is how I achieved this in lucene 4. Is there some
guidelines how to do this in lucene 5, specially on semantics changes of
Atom
ow-to-return-custom-collector-info-tp4180502p4180877.html
Sent from the Solr - User mailing list archive at Nabble.com.
lues in the collector() method, so
where have I gone wrong trying to read the field cache (or doc values - I
have not tried to enable them and am not sure how to do so)?
--
View this message in context:
http://lucene.472066.n3.nabble.com/How-to-return-custom-collector-info-tp4180502p4180686.
nt model to get the data from the filter, then write it
>> out
>> in the process() method.
>>
>> This is my first attempt at customizing Solr so I may not be expressing
>> myself clearly. Thank you for any pointers you can provide.
>> (using Solr 4.9)
>>
>>
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/How-to-return-custom-collector-info-tp4180502.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>
>
not be expressing
> myself clearly. Thank you for any pointers you can provide.
> (using Solr 4.9)
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/How-to-return-custom-collector-info-tp4180502.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
2066.n3.nabble.com/How-to-return-custom-collector-info-tp4180502.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi
I am migrating from Lucene 3.6.1 to 4.3.0. I am however not sure how to migrate
my custom collector below. this page
http://lucene.apache.org/core/4_3_0/MIGRATE.html gives some hints but the
instructions are incomplete and looking at the source examples of custom
collectors make me want
Hi,
We want to remove some results from the result set based on the result of some
algorithms on some fields in adjacent documents. For example, if doc2 resembles
or doc1 we want to remove it. We cannot do this in a search component because
of problems with paging, maintaining rows=N results de
Hi Mikhail,
You are correct. "[+] show 6 result.." will work but
it wouldn't suit my requirements. This is a question of user experience
right?
Imagine if the product manager comes to you and says I dont want to see
"[+] show 6 result.." and I want the results to be diverse bu
Hello,
I don't believe your task can be solved by playing with scoring/collector
or shuffling.
For me it's absolutely Grouping usecase (despite I don't really know this
feature well).
> Grouping cannot solve the problem because I dont want to limit the number
of results showed based on the groupi
Tanguy,
You idea is perfect for cases where there is a too many
documents with 80-90% documents having same value for a particular field.
As an example, your idea is ideal for, lets say we have 10 documents in
total like this,
doc1 : Kellog's
doc2 : Kellog's
doc3 : Kellog's
Hello Mikhail,
Thank you for the reply. In terms of user
experience, I want to spread out the products from same brand farther from
each other, *atleast* in the first 50-100 results we display. I am thinking
about two different approaches as solution.
Hello,
I've got the problem description below. Can you explain the expected user
experience, and/or solution approach before diving into the algorithm
design?
Thanks
On Sat, Aug 18, 2012 at 2:50 AM, Karthick Duraisamy Soundararaj <
karthick.soundara...@gmail.com> wrote:
> My problem is that whe
13 matches
Mail list logo
