; Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch
> Lucene ecosystem search :: http://search-lucene.com/
>
>
>
> - Original Message
> > From: Bharat Jain
> > To: solr-user@lucene.apache.org
> > Sent: Fri, July 30, 2010 10:40:19 AM
> > Subjec
Subject: Re: question about relevance
>
> Hi,
>Thanks a lot for the info and your time. I think field collapse will work
> for us. I looked at the https://issues.apache.org/jira/browse/SOLR-236 but
> which file I should use for patch. We use solr-1.3.
>
> Thanks
>
Hi,
Thanks a lot for the info and your time. I think field collapse will work
for us. I looked at the https://issues.apache.org/jira/browse/SOLR-236 but
which file I should use for patch. We use solr-1.3.
Thanks
Bharat Jain
On Fri, Jul 30, 2010 at 12:53 AM, Chris Hostetter
wrote:
>
> : 1. Th
: 1. There are user records of type A, B, C etc. (userId field in index is
: common to all records)
: 2. A user can have any number of A, B, C etc (e.g. think of A being a
: language then user can know many languages like french, english, german etc)
: 3. Records are currently stored as a document
Well you are correct Erik that this is a database-ish thing try to achieve
in solr and unfortunately the sin :) had been committed by somebody else :)
and now we are running into relevancy issues.
Let me try to state the problem more casually.
1. There are user records of type A, B, C etc. (userI
I'm having trouble getting my head around what you're trying to accomplish,
so if this is off base you know why .
But what it smells like is that you're trying to do database-ish things in
a SOLR index, which is almost always the wrong approach. Is there a
way to index redundant data with each doc
Hello All,
I have a index which store multiple objects belonging to a user
for e.g.
-> Identifies user
object type e.g. userBasic or userAdv
> MAPS to userBasicInfoObject
-> MAPS to userAdvInfoObject
Now when I am doing some query I get multipl
