Do not use index time boosting, please. When something is deprecated,
the usual process is that that functionality is supported for one
major version after deprecation, then the devs are free to remove it.
Index time boosting is not supported in 7.0 even though it is in 6x,
from CHANGES.txt, the
Tue, Nov 14, 2017 at 5:32 PM, Amrit Sarkar
wrote:
> Hi Venkat,
>
> FYI: Index time boosting has been deprecated from latest versions of Solr:
> https://issues.apache.org/jira/browse/LUCENE-6819.
>
> Not sure which version you are on, but best consider the comments on the
>
Hi Venkat,
FYI: Index time boosting has been deprecated from latest versions of Solr:
https://issues.apache.org/jira/browse/LUCENE-6819.
Not sure which version you are on, but best consider the comments on the
JIRA before using it.
Amrit Sarkar
Search Engineer
Lucidworks, Inc.
415-589-9269
Hello Guys,
I would like to understand how index time boosting works in Solr. and how
it is relates to ommitNorms property in schema.xml.
and i am trying to understand how it works internally , if you have any
documentation please provide.
Thanks,
Venkat.
Hi
I'm using solr-4.7.2 and trying to set boost at field level at index time
in atomic updates(tried though xml update handler). But its not happening.
Also if you index the full doc with index time boost and update any other
field partially then also the boost value of other field changes to 1.0.
Hi all,
We are trying to deboost some documents while indexing depending on their
text available some thing like this
>
> * *
>
>
>
>
>
> my questions
1.are we going right or not?
2.in order to get the difference how can we deboost this
thank you james for the feedback - i appreciate it.
ultimately - i was trying to decide if i was missing the boat by ONLY using
query time boosting, and i should really be using index time boosting.
but after your reply, reading the solr book, and looking at the lucene dox -
it looks like index
m]
Sent: Tuesday, May 22, 2012 3:06 PM
To: solr-user@lucene.apache.org
Subject: RE: index-time boosting using DIH
thanks for the reply,
so to use the $docBoost pseudo-field name, would you do something like below
- and would this technique likely inc
-time-boosting-using-DIH-tp3985508p3985527.html
Sent from the Solr - User mailing list archive at Nabble.com.
@lucene.apache.org
Subject: index-time boosting using DIH
hello all,
can i use the technique described on the wiki at:
http://wiki.apache.org/solr/SolrRelevancyFAQ#index-time_boosts
if i am populating my core using a DIH?
looking at the posts on this subject and the wiki docs - leads me to believe
interface for
importing data?
thank you
--
View this message in context:
http://lucene.472066.n3.nabble.com/index-time-boosting-using-DIH-tp3985508.html
Sent from the Solr - User mailing list archive at Nabble.com.
--Original Message-
From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com]
Sent: Donnerstag, 28. Juli 2011 12:37
To: solr-user@lucene.apache.org
Subject: Re: Index time boosting with DIH
On Thu, Jul 28, 2011 at 3:56 PM, Bürkle, David wrote:
> Can someone point me to an example fo
On Thu, Jul 28, 2011 at 3:56 PM, Bürkle, David wrote:
> Can someone point me to an example for using index time boosting with the
> DataImportHandler.
>
>
You can use the special flag variable $docBoost to add a index time boost.
http://wiki.apache.org/solr/DataImportHandler#Spec
Can someone point me to an example for using index time boosting with the
DataImportHandler.
Thanks Iorixxx... Boosting is working while using DIH to import XML.
Thanks,
SRD
--
View this message in context:
http://lucene.472066.n3.nabble.com/Index-time-boosting-is-not-working-with-boosting-value-in-document-level-tp1649072p1693423.html
Sent from the Solr - User mailing list archive at
> Thanks a ton Eric and Iorixxx.
> Since I used DIH to import XML data, boosting was not
> reflected in score.
> When I used /update to import XML data, boosting was
> considered for scoring
> and able to see the intended data on top 10 results.
> Could you please let me know how to make boosting v
reflected in
score while using DIH to index XML docs?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Index-time-boosting-is-not-working-with-boosting-value-in-document-level-tp1649072p1686445.html
Sent from the Solr - User mailing list archive at Nabble.com.
> Eric,
> Score is not coming properly even after
> giving boost value in document
> and field level.
> Please find the solrconfig.xml,
> schema.xml, data-config.xml, the feed and
> the score & query.
> Doc with id 'ABCDEF/L' is boosted and doc
> with id 'MA147LL/A' is not
> boosted, but b
5
0.27466023
IW-02
iPod & iPod Mini USB 2.0 Cable
0.24276763
F8V7067-APL-KIT
Belkin Mobile Power Cord for iPod w/ Dock
0.1942141
MA147LL/A
Apple 60 GB iPod with Video Playback Black
0.1942141
ABCDEF/L
Apple 60 GB iPod with Video Playback Black
--
View this message in context:
http://lucene
e help on this issue?
>
>
>
>
> multiValued="true" omitNorms="false"/>
> multiValued="true"/>
> multiValued="true"/>
>
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Index-time-boosting-is-not-working-with-boosting-value-in-document-level-tp1649072p1649072.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
http://lucene.472066.n3.nabble.com/Index-time-boosting-is-not-working-with-boosting-value-in-document-level-tp1649072p1649072.html
Sent from the Solr - User mailing list archive at Nabble.com.
lly^10) etc?
>
> How would i do it to say boost title by 5 - is that even possible within a
> function query?
>
> i will try just giving some crazy boost values to the most important fields
> and hope that it improves the problem.
>
> joe
>
>
> --
> View this messa
ving some crazy boost values to the most important fields
and hope that it improves the problem.
joe
--
View this message in context:
http://lucene.472066.n3.nabble.com/Index-time-boosting-tp1411105p1412259.html
Sent from the Solr - User mailing list archive at Nabble.com.
Have you tried running the queries through with &debugQuery=true?
It may well be that, for certain documents, the lower-boosted fields
are still overwhelming the contribution to scoring from the higher-boosted
fields for the documents in question.
The problem is that index-time boosting is fa
annot switch to dismax parser at this late stage so cannot
do query time boosting unless theres another way of doing it on the standard
parser.
thanks
joe
--
View this message in context:
http://lucene.472066.n3.nabble.com/Index-time-boosting-tp1411105p1411105.html
Sent from the Solr - Us
: I had working index time boosting on documents like so:
:
: Everything was great until I made some changes that I thought where no
: related to the doc boost but after that my doc boosting appears to be
: missing.
:
: I'm having a tough time debugging this and didn't have th
Hi,
I had working index time boosting on documents like so:
Everything was great until I made some changes that I thought where no
related to the doc boost but after that my doc boosting appears to be
missing.
I'm having a tough time debugging this and didn't have the sense to versi
Whitman wrote:
> I can set the boost of a field or doc at index time using the boost attr in
> the update message, e.g.
> pet
>
> But that won't work for multivalued fields according to the RelevancyFAQ
>
> pet
> animal
>
> ( I assume it applies the last boost pa
I can set the boost of a field or doc at index time using the boost attr in
the update message, e.g.
pet
But that won't work for multivalued fields according to the RelevancyFAQ
pet
animal
( I assume it applies the last boost parsed to all terms? )
Now, say I'd like to do index-tim
; > at http://wiki.apache.org/solr/UpdateXmlMessages
> >
> > On Mon, Sep 15, 2008 at 2:25 PM, Luca Molteni <[EMAIL PROTECTED]>
> wrote:
> >
> > > Hello, dear Solr Users,
> > >
> > > I'm starting to learn Solr and Lucene, since I want
is
> at http://wiki.apache.org/solr/UpdateXmlMessages
>
> On Mon, Sep 15, 2008 at 2:25 PM, Luca Molteni <[EMAIL PROTECTED]> wrote:
>
> > Hello, dear Solr Users,
> >
> > I'm starting to learn Solr and Lucene, since I want to use this
> technology
> &
, but I found some trouble in the "index-time boosting"
> section
> of the documentation, I'm probably missing something, but since I can't
> figure out all by myself, I decided to wrote here.
>
> For example, in the scoring faq:
>
> http://wiki.apache.org/
Hello, dear Solr Users,
I'm starting to learn Solr and Lucene, since I want to use this technology
in my project, but I found some trouble in the "index-time boosting" section
of the documentation, I'm probably missing something, but since I can't
figure out all by myself
pyField text to:
[text] i like to commute commuting thoughts
we, the Archive, want query hits in title to boost ^100.
if we do q=commute (which searches "text")
with index-time boosting, solr/lucene won't know
the hit due to "title" should effect a much higher ranking
co
effect we'd like.
[example documentA]
[description] i like to commute
[title] commuting thoughts
copyField text to:
[text] i like to commute commuting thoughts
we, the Archive, want query hits in title to boost ^100.
if we do q=commute (which searches "text")
with index-time b
ok, great to know -- all this is invaluable.
i'm stashing away "ideas" like this for the future (because..)
i think for now i'll stick with XSL transforming the fields to lowercase
because we already need this small XSLT from our item XML to
XML that solr can index.
-t
Chris Hostetter wrote:
oh, and yes, i've always understood, thankfully, that queries
of
"q=commute&fl=title"
and
"q=title:commute&fl=title"
are *quite* different
(but that is probably mostly due to my prior experience with
lucene with our current broken SE 8-)
-t
Mike Klaas wrote:
On 12/5/06, Tracey Jaquith
Hi Mike,
OK, I guess my "problem" is more of a partially still coming up
to speed / partially wanting to be lazy.
If I make a dismax handler called "dissed", I'd like it to "work"
whether or not i pass in "commute" or "title:commute" to the query.
(Now I *do* realize those are two completely dif
On 12/5/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Indeed--those are different queries. The "fl" parameter controlled
: the stored fields returned by Solr; it does not affect which documents
: are returned. The first query asks for the titles of all documents
: containing the word "commu
: so for my dwindling number of remaining "string" types, in my XSL
: transform (on the input to index the doc) i'll lowercase them all, too 8-)
I don't beleive that is strictly neccessary, these two field types should
be functionally equivilent...
...so i'm p
: > (For example, I do "indent=on&fl=title&q=commute" in a wget and grep the
: > results
: > for and then grep -i for commute, there are 23 hits. But doing
: > "&q=title:commute" only returns one of those hits..)
:
: Indeed--those are different queries. The "fl" parameter controlled
: the sto
wow, that makes sense now. my bad.
OK, great. further testing shows "you mean what you say" -- not
only verbatim, but case sensitive.
so for my dwindling number of remaining "string" types, in my XSL
transform (on the input to index the doc) i'll lowercase them all, too
8-)
thanks!!
--t
Yo
On 12/5/06, Tracey Jaquith <[EMAIL PROTECTED]> wrote:
Now I have one new mystery that's popped up for me.
With std req handler, this simple query
q=title:commute
is *not* returning me all documents that have the word "commute" in the
title.
There must be some other filter/clause or something
On 12/5/06, Tracey Jaquith <[EMAIL PROTECTED]> wrote:
Now I have one new mystery that's popped up for me.
With std req handler, this simple query
q=title:commute
is *not* returning me all documents that have the word "commute" in the
title.
There must be some other filter/clause or something
Hi Yonik!
Yonik Seeley wrote:
On 12/5/06, Tracey Jaquith <[EMAIL PROTECTED]> wrote:
Quick intro. Server Engineer at Internet Archive.
I just spent a mere 3 days porting nearly our entire site to use your
*wonderful* project!
I, too, am looking for a kind of "boosting".
If I understand your re
One last thing to keep in mind is the tradeoffs:
Querying a single all encompasing "text" field will be faster, but the
scoring won't be as relevant. The types of queries dismax generates
can get you better relevance, at the cost of performance.
-Yonik
On 12/5/06, Chris Hostetter <[EMAIL PROTEC
: > [We are most interested in always having "title", "description", and a
: > few other
: > fields boosted. We have both user queries of phrases/words as well as
: > "field-specific" queries (eg: "mediatype:moves AND collection:prelinger")
: > so my thought is std might be better than dismax.
On 12/5/06, Tracey Jaquith <[EMAIL PROTECTED]> wrote:
Quick intro. Server Engineer at Internet Archive.
I just spent a mere 3 days porting nearly our entire site to use your
*wonderful* project!
I, too, am looking for a kind of "boosting".
If I understand your reply here, if i reindex *all* my
Hi all,
[initially I replied to a thread which went to Mike Klass email so after
his helpful
reply, I'm trying to merge this back into the list discussion]
Quick intro. Server Engineer at Internet Archive.
I just spent a mere 3 days porting nearly our entire site to use your
*wonderful* proj
: We'll start with "OR", because I think an all-terms default is a really
: bad idea. If someone is searches for "X-Men 3: The Final Battle", we
: need to show them "X-Men 3: The Last Stand".
BooleanQuery.setMinimumNumberShouldMatch can help reduce the cruft with
this approach .. the dismax handl
: Is fq documented anywhere??? It's very useful for speeding up complex
i just added it to CommonQueryParameters
-Hoss
On Oct 20, 2006, at 2:34 PM, Walter Underwood wrote:
We have a well-developed browsing design, so I'd rather not mix
facets in with that. Two other things work against using facets:
most of our queries are known-item searches, and I think that
facets work best when there is very broad agreement
On 10/20/06 11:17 AM, "Yonik Seeley" <[EMAIL PROTECTED]> wrote:
> That definitely seems doable.
> How big is your index?
Currently, the index is 65,000 movies plus actors and directors. A pretty
small corpus.
> What's the form of your queries (AND, or sloppy phrase queries I'd imagine?)
We'll s
On 10/20/06, Walter Underwood <[EMAIL PROTECTED]> wrote:
On 10/20/06 10:24 AM, "Mike Klaas" <[EMAIL PROTECTED]> wrote:
> Finally, it can be much faster to search a single field rather than
> multiple fields. One hacky way of achieving this is to make a field
> which receives a single copy of co
On 10/20/06, Walter Underwood <[EMAIL PROTECTED]> wrote:
On 10/20/06 10:24 AM, "Mike Klaas" <[EMAIL PROTECTED]> wrote:
> Finally, it can be much faster to search a single field rather than
> multiple fields. One hacky way of achieving this is to make a field
> which receives a single copy of co
On 10/20/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
On 10/20/06, Mike Klaas <[EMAIL PROTECTED]> wrote:
> Finally, it can be much faster to search a single field rather than
> multiple fields. One hacky way of achieving this is to make a field
> which receives a single copy of contents and eight
On 10/20/06 10:24 AM, "Mike Klaas" <[EMAIL PROTECTED]> wrote:
> Finally, it can be much faster to search a single field rather than
> multiple fields. One hacky way of achieving this is to make a field
> which receives a single copy of contents and eight copies of title.
> This is imperfect, as i
On 10/20/06, Mike Klaas <[EMAIL PROTECTED]> wrote:
Index-time boosts can be set per-document or per-document-field.
There is no facility for setting the boost of a part of text added to
a field (as you suggest above) (which is really a shame, as such
functionality would lend huge flexibility to i
On 10/20/06, Walter Underwood <[EMAIL PROTECTED]> wrote:
I'm trying to figure out how to set per-field boosts in Solr at index time.
For example, if I want the title to be boosted by a factor of 8, I could
do that in a query, or I could add the title text with a boost of 8 to the
default text fie
rray for each indexed field). Since they contain
one byte per document, you can easily tell how many documents are in
each segment by a simple glance at these files.
For other engines I've worked with, this gives a lot more performance at
the cost of some flexibility -- you need to reind
I'm trying to figure out how to set per-field boosts in Solr at index time.
For example, if I want the title to be boosted by a factor of 8, I could
do that in a query, or I could add the title text with a boost of 8 to the
default text field along with the body text (with a boost of 1).
For other
61 matches
Mail list logo
