erms, then using
> payloads
> > > would be the most straightforward i suppose. You still need a custom
> > > similarity and custom query parser. Payloads work for us very well.
> > >
> > > M
> > >
> > >
> > >
> > >
r us very well.
> >
> > M
> >
> >
> >
> > -Original message-
> > > From:Ahmet Arslan
> > > Sent: Monday 12th January 2015 19:50
> > > To: solr-user@lucene.apache.org
> > > Subject: Re: Extending solr analysis in index time
> >
rk for us very well.
>
> M
>
>
>
> -Original message-
> > From:Ahmet Arslan
> > Sent: Monday 12th January 2015 19:50
> > To: solr-user@lucene.apache.org
> > Subject: Re: Extending solr analysis in index time
> >
> > Hi Ali,
> >
>
anuary 2015 19:50
> To: solr-user@lucene.apache.org
> Subject: Re: Extending solr analysis in index time
>
> Hi Ali,
>
> Reading your example, if you could somehow replace idf component with your
> "importance weight",
> I think your use case looks like TF
Hi Ali,
Reading your example, if you could somehow replace idf component with your
"importance weight",
I think your use case looks like TFIDFSimilarity. Tf component remains same.
https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
I also sugges
Could you clarify what you mean by "Lucene reverse index"? That's not a
term I am familiar with.
-- Jack Krupansky
On Mon, Jan 12, 2015 at 1:01 AM, Ali Nazemian wrote:
> Dear Jack,
> Thank you very much.
> Yeah I was thinking of function query for sorting, but I have to problems
> in this case,
Dear Jack,
Thank you very much.
Yeah I was thinking of function query for sorting, but I have to problems
in this case, 1) function query do the process at query time which I dont
want to. 2) I also want to have the score field for retrieving and showing
to users.
Dear Alexandre,
Here is some more
Won't function queries do the job at query time? You can add or multiply
the tf*idf score by a function of the term frequency of arbitrary terms,
using the tf, mul, and add functions.
See:
https://cwiki.apache.org/confluence/display/solr/Function+Queries
-- Jack Krupansky
On Sun, Jan 11, 2015 at
Actually, let me take that back. I seem to remember an example where
somebody used URP to do a pre-analysis of the field. That implies
access to Solr core. So it might be possible.
But I still think you need to review the business level issues, as you
are going into increasingly hacky territory.
No you cannot anything outside specific document being indexed at that point.
What are you actually trying to achieve on the business level?
Regards,
Alex.
Sign up for my Solr resources newsletter at http://www.solr-start.com/
On 11 January 2015 at 14:59, Ali Nazemian wrote:
> Dear Ale
Dear Alexandre,
I did not tried updaterequestprocessor yet. Can I access to term
frequencies at this level? I dont want to calculate term frequencies once
more while lucene already calculate them in reverse index?
Thank you very much.
On Jan 11, 2015 7:49 PM, "Alexandre Rafalovitch"
wrote:
> Yo
Your description uses the terms Solr/Lucene uses but perhaps not in
the same way we do. That might explain the confusion.
It sounds - on a high level - that you want to create a field based on
a combination of a couple of other fields during indexing stage. Have
you tried UpdateRequestProcessors?
Dear Jack,
Hi,
I think you misunderstood my need. I dont want to change the default
scoring behavior of Lucene (tf-idf) I just want to have another field to do
sorting for some specific queries (not all the search business), however I
am aware of Lucene payload.
Thank you very much.
On Sun, Jan 11
You would do that with a custom similarity (scoring) class. That's an
expert feature. In fact a SUPER-expert feature.
Start by completely familiarizing yourself with how TF*IDF similarity
already works:
http://lucene.apache.org/core/4_10_3/core/org/apache/lucene/search/similarities/TFIDFSimilarit
14 matches
Mail list logo
