You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Ian Smith <Ia...@gossinteractive.com> on 2009/11/18 12:40:11 UTC

Index-time field boosting not working?

I have the following field configured in schema.xml:

<field name="title" type="text" indexed="true" stored="true"
omitNorms="false" boost="3.0" />

Where "text" is the type which came with the Solr distribution.  I have
not been able to get this configuration to alter any document scores,
and if I look at the indexes in Luke there is no change in the norms
(compared to an un-boosted equivalent).

I have confirmed that document boosting works (via SolrJ), but our field
boosting needs to be done in the schema.

Am I doing something wrong (BTW I have tried using "3.0f" as well, no
difference)?

Also, I have seen no debug output during startup which would indicate
that fild boosting is being configured - should there be any?

I have found no usage examples of this in the Solr 1.4 book, except a
vague discouragement - is this a deprecated feature?

TIA,

Ian

Web design and intelligent Content Management. www.twitter.com/gossinteractive 

Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower Street, Plymouth, PL1 1LG.  Company Registration No: 3553908 

This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email. 

Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses.



Re: schema-based Index-time field boosting

Posted by Chris Hostetter <ho...@fucit.org>.
: Coming in a bit late but I would like a variant that is not a No-OP.
: Think of something like title:searchstring^10 OR catch_all:searchstring
: Of course I can always add the boosting at query time but it would make
: life easier if I could define a default boost in the schema so that my
: query could just be title:searchstring OR catch_all:searchstring
: but still get the boost for the title field.

That would be a query time boost -- not an index time boost.  An index 
time boost is a very specific concept that refers to increaseing the 
fieldNorm of a field in a specific document.

What you are describing would be a query time boost, in which solr knows 
that certain query clauses should be worth more.  You can 
already do esentailly this exact same thing using the dismax parser, but i 
suppose it would also be possible to modify the LuceneQParser so that it 
could take in configuration that would tell it to apply different default 
query boosts to different fields.



-Hoss


Re: schema-based Index-time field boosting

Posted by Michael Lackhoff <mi...@lackhoff.de>.
On 23.11.2009 19:33 Chris Hostetter wrote:

> ...if there was a way to oost fields at index time that was configured in 
> the schema.xml, then every doc would get that boost on it's instances of 
> those fields but the only purpose of index time boosting is to indicate 
> that one document is more significant then another doc -- if every doc 
> gets the same boost, it becomes a No-OP.
> 
> (think about the math -- field boosts become multipliers in the fieldNorm 
> -- if every doc gets the same multiplier, then there is no net effect)

Coming in a bit late but I would like a variant that is not a No-OP.
Think of something like title:searchstring^10 OR catch_all:searchstring
Of course I can always add the boosting at query time but it would make
life easier if I could define a default boost in the schema so that my
query could just be title:searchstring OR catch_all:searchstring
but still get the boost for the title field.

Thinking this further it would be even better if it was possible to
define one (or more) fallback field(s) with associated boost factor in
the schema. Then it would be enough to query for title:searchstring and
it would be automatically expanded to e.g.
title:searchstring^10 OR title_other_language:searchstring^5 OR
catchall:searchstring
or whatever you define in the schema.

-Michael



Re: schema-based Index-time field boosting

Posted by Walter Underwood <wu...@wunderwood.org>.
An index-time boost means "this document is a better answer, regardless of the query."

To weight title matches higher than summary matches, use field boosts at query time. They work great. There is no need to modify Solr to get that behavior. 

wunder

On Dec 3, 2009, at 12:37 AM, Ian Smith wrote:

> Aaaaaaaargh!  OK, I would like a document with (eg.) a title containing
> a term to score higher than one on (eg.) a summary containing the same
> term, all other things being "equal".  You seem to be arguing against
> field boosting in general, and I don't understand why!
> 
> May as well let this drop since we don't seem to be talking about the
> same thing . . . but thanks anyway,
> 
> Ian.
> -----Original Message-----
> From: Chris Hostetter [mailto:hossman_lucene@fucit.org] 
> Sent: 30 November 2009 23:05
> To: solr-user@lucene.apache.org
> Subject: RE: schema-based Index-time field boosting 
> 
> 
> : I am talking about field boosting rather than document boosting, ie. I
> : would like some fields (say eg. title) to be "louder" than others,
> : across ALL documents.  I believe you are at least partially talking
> : about document boosting, which clearly applies on a per-document
> basis.
> 
> index time boosts are all the same -- it doesn't matter if htey are
> field boosts or document boosts -- a document boost is just a field
> boost for every field in the document.
> 
> : If it helps, consider a schema version of the following, from
> : org.apache.solr.common.SolrInputDocument:
> : 
> :   /**
> :    * Adds a field with the given name, value and boost.  If a field
> with
> : the name already exists, then it is updated to
> :    * the new value and boost.
> :    *
> :    * @param name Name of the field to add
> :    * @param value Value of the field
> :    * @param boost Boost value for the field
> :    */
> :   public void addField(String name, Object value, float boost ) 
> 
> 	...
> 
> : Where a constant boost value is applied consistently to a given field.
> : That is what I was mistakenly hoping to achieve in the schema.  I
> still
> : think it would be a good idea BTW.  Regards,
> 
> But now we're right back to what i was trying to explain before: index
> time boost values like these are only used as a multiplier in the
> fieldNorm.  when included as part of the document data, you can specify
> a fieldBoost for fieldX of docA that's greater then the boost for fieldX
> of docB and that will make docA score higher then docB when fieldX
> contains the same number of matches and is hte same length -- but if you
> apply a constant boost of B to fieldX for every doc (which is what a
> feature to hardcode boosts in schema.xml might give you) then the net
> effect would be zero when scoring docA and docB, because the fieldNorm's
> for fieldX in both docs would include the exact same multiplier.
> 
> 
> 
> -Hoss
> 


Re: schema-based Index-time field boosting

Posted by Erik Hatcher <er...@gmail.com>.
Ian - now you're talking *term* boosting, which is a dynamic query- 
time factor, not something specified at index time.

Here's what I suggest as a starting point for this sort of thing, in  
Solr request format:

    http://localhost:8983/solr/select? 
defType=dismax&q=apple&qf=name^2+manu

Where the term "apple" is queried against both the name and  
manu(facturer) fields.  And matches in the name field get boosted by a  
factor of 2.  This is using the dismax query parser.

Using index-time boosts are becoming less and less favorable - rarely  
any need to do that given the more flexible dynamic control you can  
have over scoring at query-time.

And I'm sure Hoss isn't arguing against field boosting, given he's one  
of the gurus behind the magic of dismax.  He's simply saying if you  
apply a constant boost to all documents, you've effectively done  
nothing.

	Erik

On Dec 3, 2009, at 3:37 AM, Ian Smith wrote:

> Aaaaaaaargh!  OK, I would like a document with (eg.) a title  
> containing
> a term to score higher than one on (eg.) a summary containing the same
> term, all other things being "equal".  You seem to be arguing against
> field boosting in general, and I don't understand why!
>
> May as well let this drop since we don't seem to be talking about the
> same thing . . . but thanks anyway,
>
> Ian.
> -----Original Message-----
> From: Chris Hostetter [mailto:hossman_lucene@fucit.org]
> Sent: 30 November 2009 23:05
> To: solr-user@lucene.apache.org
> Subject: RE: schema-based Index-time field boosting
>
>
> : I am talking about field boosting rather than document boosting,  
> ie. I
> : would like some fields (say eg. title) to be "louder" than others,
> : across ALL documents.  I believe you are at least partially talking
> : about document boosting, which clearly applies on a per-document
> basis.
>
> index time boosts are all the same -- it doesn't matter if htey are
> field boosts or document boosts -- a document boost is just a field
> boost for every field in the document.
>
> : If it helps, consider a schema version of the following, from
> : org.apache.solr.common.SolrInputDocument:
> :
> :   /**
> :    * Adds a field with the given name, value and boost.  If a field
> with
> : the name already exists, then it is updated to
> :    * the new value and boost.
> :    *
> :    * @param name Name of the field to add
> :    * @param value Value of the field
> :    * @param boost Boost value for the field
> :    */
> :   public void addField(String name, Object value, float boost )
>
> 	...
>
> : Where a constant boost value is applied consistently to a given  
> field.
> : That is what I was mistakenly hoping to achieve in the schema.  I
> still
> : think it would be a good idea BTW.  Regards,
>
> But now we're right back to what i was trying to explain before: index
> time boost values like these are only used as a multiplier in the
> fieldNorm.  when included as part of the document data, you can  
> specify
> a fieldBoost for fieldX of docA that's greater then the boost for  
> fieldX
> of docB and that will make docA score higher then docB when fieldX
> contains the same number of matches and is hte same length -- but if  
> you
> apply a constant boost of B to fieldX for every doc (which is what a
> feature to hardcode boosts in schema.xml might give you) then the net
> effect would be zero when scoring docA and docB, because the  
> fieldNorm's
> for fieldX in both docs would include the exact same multiplier.
>
>
>
> -Hoss
>


RE: schema-based Index-time field boosting

Posted by Ian Smith <Ia...@gossinteractive.com>.
Aaaaaaaargh!  OK, I would like a document with (eg.) a title containing
a term to score higher than one on (eg.) a summary containing the same
term, all other things being "equal".  You seem to be arguing against
field boosting in general, and I don't understand why!

May as well let this drop since we don't seem to be talking about the
same thing . . . but thanks anyway,

Ian.
-----Original Message-----
From: Chris Hostetter [mailto:hossman_lucene@fucit.org] 
Sent: 30 November 2009 23:05
To: solr-user@lucene.apache.org
Subject: RE: schema-based Index-time field boosting 


: I am talking about field boosting rather than document boosting, ie. I
: would like some fields (say eg. title) to be "louder" than others,
: across ALL documents.  I believe you are at least partially talking
: about document boosting, which clearly applies on a per-document
basis.

index time boosts are all the same -- it doesn't matter if htey are
field boosts or document boosts -- a document boost is just a field
boost for every field in the document.

: If it helps, consider a schema version of the following, from
: org.apache.solr.common.SolrInputDocument:
: 
:   /**
:    * Adds a field with the given name, value and boost.  If a field
with
: the name already exists, then it is updated to
:    * the new value and boost.
:    *
:    * @param name Name of the field to add
:    * @param value Value of the field
:    * @param boost Boost value for the field
:    */
:   public void addField(String name, Object value, float boost ) 

	...

: Where a constant boost value is applied consistently to a given field.
: That is what I was mistakenly hoping to achieve in the schema.  I
still
: think it would be a good idea BTW.  Regards,

But now we're right back to what i was trying to explain before: index
time boost values like these are only used as a multiplier in the
fieldNorm.  when included as part of the document data, you can specify
a fieldBoost for fieldX of docA that's greater then the boost for fieldX
of docB and that will make docA score higher then docB when fieldX
contains the same number of matches and is hte same length -- but if you
apply a constant boost of B to fieldX for every doc (which is what a
feature to hardcode boosts in schema.xml might give you) then the net
effect would be zero when scoring docA and docB, because the fieldNorm's
for fieldX in both docs would include the exact same multiplier.



-Hoss


RE: schema-based Index-time field boosting

Posted by Chris Hostetter <ho...@fucit.org>.
: I am talking about field boosting rather than document boosting, ie. I
: would like some fields (say eg. title) to be "louder" than others,
: across ALL documents.  I believe you are at least partially talking
: about document boosting, which clearly applies on a per-document basis.

index time boosts are all the same -- it doesn't matter if htey are field 
boosts or document boosts -- a document boost is just a field boost for 
every field in the document.

: If it helps, consider a schema version of the following, from
: org.apache.solr.common.SolrInputDocument:
: 
:   /**
:    * Adds a field with the given name, value and boost.  If a field with
: the name already exists, then it is updated to
:    * the new value and boost.
:    *
:    * @param name Name of the field to add
:    * @param value Value of the field
:    * @param boost Boost value for the field
:    */
:   public void addField(String name, Object value, float boost ) 

	...

: Where a constant boost value is applied consistently to a given field.
: That is what I was mistakenly hoping to achieve in the schema.  I still
: think it would be a good idea BTW.  Regards,

But now we're right back to what i was trying to explain before: index 
time boost values like these are only used as a multiplier in the 
fieldNorm.  when included as part of the document data, you can specify a 
fieldBoost for fieldX of docA that's greater then the boost for fieldX 
of docB and that will make docA score higher then docB when fieldX 
contains the same number of matches and is hte same length -- but if you 
apply a constant boost of B to fieldX for every doc (which is what a 
feature to hardcode boosts in schema.xml might give you) then the net 
effect would be zero when scoring docA and docB, because the fieldNorm's 
for fieldX in both docs would include the exact same multiplier.



-Hoss


RE: schema-based Index-time field boosting

Posted by Ian Smith <Ia...@gossinteractive.com>.
Hi Chris, thanks for replying! 


OK, now I'm going to take the bait ;)


I am talking about field boosting rather than document boosting, ie. I
would like some fields (say eg. title) to be "louder" than others,
across ALL documents.  I believe you are at least partially talking
about document boosting, which clearly applies on a per-document basis.

If it helps, consider a schema version of the following, from
org.apache.solr.common.SolrInputDocument:

  /**
   * Adds a field with the given name, value and boost.  If a field with
the name already exists, then it is updated to
   * the new value and boost.
   *
   * @param name Name of the field to add
   * @param value Value of the field
   * @param boost Boost value for the field
   */
  public void addField(String name, Object value, float boost ) 
  {
    SolrInputField field = _fields.get( name );
    if( field == null || field.value == null ) {
      setField(name, value, boost);
    }
    else {
      field.addValue( value, boost );
    }
  }

Where a constant boost value is applied consistently to a given field.
That is what I was mistakenly hoping to achieve in the schema.  I still
think it would be a good idea BTW.  Regards,

Ian.

-----Original Message-----
From: Chris Hostetter [mailto:hossman_lucene@fucit.org] 
Sent: 23 November 2009 18:34
To: solr-user@lucene.apache.org
Subject: RE: schema-based Index-time field boosting 


: Yeah, like I said, I was mistaken about setting field boost in
: schema.xml - doesn't mean it's a bad idea though.  At any rate, from
: your penultimate sentence I reckon at least one of us is still
confused
: about field boosting, feel free to reply if you think it's me ;)

Yeah ... i think it's you.  like i said...

: field boosting only makes sense if it's only applied to some of the
: documents in the index, if every document has an index time boost on
: fieldX, then that boost is meaningless.

...if there was a way to oost fields at index time that was configured
in the schema.xml, then every doc would get that boost on it's instances
of those fields but the only purpose of index time boosting is to
indicate that one document is more significant then another doc -- if
every doc gets the same boost, it becomes a No-OP.

(think about the math -- field boosts become multipliers in the
fieldNorm
-- if every doc gets the same multiplier, then there is no net effect)



-Hoss


Web design and intelligent Content Management. www.twitter.com/gossinteractive 

Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower Street, Plymouth, PL1 1LG.  Company Registration No: 3553908 

This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email. 

Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses.



RE: schema-based Index-time field boosting

Posted by Chris Hostetter <ho...@fucit.org>.
: Yeah, like I said, I was mistaken about setting field boost in
: schema.xml - doesn't mean it's a bad idea though.  At any rate, from
: your penultimate sentence I reckon at least one of us is still confused
: about field boosting, feel free to reply if you think it's me ;)

Yeah ... i think it's you.  like i said...

: field boosting only makes sense if it's only applied to some of the
: documents in the index, if every document has an index time boost on
: fieldX, then that boost is meaningless.

...if there was a way to oost fields at index time that was configured in 
the schema.xml, then every doc would get that boost on it's instances of 
those fields but the only purpose of index time boosting is to indicate 
that one document is more significant then another doc -- if every doc 
gets the same boost, it becomes a No-OP.

(think about the math -- field boosts become multipliers in the fieldNorm 
-- if every doc gets the same multiplier, then there is no net effect)



-Hoss


RE: schema-based Index-time field boosting

Posted by Ian Smith <Ia...@gossinteractive.com>.
Yeah, like I said, I was mistaken about setting field boost in
schema.xml - doesn't mean it's a bad idea though.  At any rate, from
your penultimate sentence I reckon at least one of us is still confused
about field boosting, feel free to reply if you think it's me ;)

Ian.

-----Original Message-----
From: Chris Hostetter [mailto:hossman_lucene@fucit.org] 
Sent: 21 November 2009 01:54
To: solr-user@lucene.apache.org
Subject: RE: schema-based Index-time field boosting 


: The field boost attribute was put there by me back in the 1.3 days,
when
: I somehow gained the mistaken impression that it was supposed to work!
: Of course, despite a lot of searching I haven't been able to find
: anything to back up my position ;)

solr has never supported anything like a "boost" paramter on fields in
schema.xml 


: Of course, by now I am convinced that this might be a really good
: feature - I might get the chance to look into it in the near future -
: can anyone think of reasons why this might not work in practice?

field boosting only makes sense if it's only applied to some of the
documents in the index, if every document has an index time boost on
fieldX, then that boost is meaningless.

are you looking for query time boosting on fields?  like what dismax
provides with the "qf" param?



-Hoss


Web design and intelligent Content Management. www.twitter.com/gossinteractive 

Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower Street, Plymouth, PL1 1LG.  Company Registration No: 3553908 

This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email. 

Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses.



RE: schema-based Index-time field boosting

Posted by Chris Hostetter <ho...@fucit.org>.
: The field boost attribute was put there by me back in the 1.3 days, when
: I somehow gained the mistaken impression that it was supposed to work!
: Of course, despite a lot of searching I haven't been able to find
: anything to back up my position ;)

solr has never supported anything like a "boost" paramter on fields in 
schema.xml 

: Of course, by now I am convinced that this might be a really good
: feature - I might get the chance to look into it in the near future -
: can anyone think of reasons why this might not work in practice?

field boosting only makes sense if it's only applied to some of the 
documents in the index, if every document has an index time boost on 
fieldX, then that boost is meaningless.

are you looking for query time boosting on fields?  like what dismax 
provides with the "qf" param?



-Hoss


RE: schema-based Index-time field boosting

Posted by Ian Smith <Ia...@gossinteractive.com>.
Hi David, thanks for replying,

The field boost attribute was put there by me back in the 1.3 days, when
I somehow gained the mistaken impression that it was supposed to work!
Of course, despite a lot of searching I haven't been able to find
anything to back up my position ;)

Unfortunately our code (intentionally) has no idea what index it is
writing to so only a schema-based approach is really going to work for
us.

Of course, by now I am convinced that this might be a really good
feature - I might get the chance to look into it in the near future -
can anyone think of reasons why this might not work in practice?

Regards,

Ian.

-----Original Message-----
From: Smiley, David W. [mailto:dsmiley@mitre.org] 
Sent: 19 November 2009 19:29
To: solr-user@lucene.apache.org
Subject: Re: Index-time field boosting not working?

Hi Ian.  Thanks for buying my book.

The "boost" attribute goes on the field for the XML message you're
sending to Solr.  In your example you mistakenly placed it in the
schema.

FYI I use index time boosting as well as query time boosting.  Although
index time boosting isn't something I can change on a whim, I've found
it to be far easier to control the scoring than say function queries
which would be the query time substitute if the boost is a function of
particular field values.

~ David Smiley
Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/


On Nov 18, 2009, at 6:40 AM, Ian Smith wrote:

> I have the following field configured in schema.xml:
> 
> <field name="title" type="text" indexed="true" stored="true"
> omitNorms="false" boost="3.0" />
> 
> Where "text" is the type which came with the Solr distribution.  I 
> have not been able to get this configuration to alter any document 
> scores, and if I look at the indexes in Luke there is no change in the

> norms (compared to an un-boosted equivalent).
> 
> I have confirmed that document boosting works (via SolrJ), but our 
> field boosting needs to be done in the schema.
> 
> Am I doing something wrong (BTW I have tried using "3.0f" as well, no 
> difference)?
> 
> Also, I have seen no debug output during startup which would indicate 
> that fild boosting is being configured - should there be any?
> 
> I have found no usage examples of this in the Solr 1.4 book, except a 
> vague discouragement - is this a deprecated feature?
> 
> TIA,
> 
> Ian
> 
> Web design and intelligent Content Management. 
> www.twitter.com/gossinteractive
> 
> Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower 
> Street, Plymouth, PL1 1LG.  Company Registration No: 3553908
> 
> This email contains proprietary information, some or all of which may
be legally privileged. It is for the intended recipient only. If an
addressing or transmission error has misdirected this email, please
notify the author by replying to this email. If you are not the intended
recipient you may not use, disclose, distribute, copy, print or rely on
this email. 
> 
> Email transmission cannot be guaranteed to be secure or error free, as
information may be intercepted, corrupted, lost, destroyed, arrive late
or incomplete or contain viruses. This email and any files attached to
it have been checked with virus detection software before transmission.
You should nonetheless carry out your own virus check before opening any
attachment. GOSS Interactive Ltd accepts no liability for any loss or
damage that may be caused by software viruses.
> 
> 


Re: Index-time field boosting not working?

Posted by "Smiley, David W." <ds...@mitre.org>.
Hi Ian.  Thanks for buying my book.

The "boost" attribute goes on the field for the XML message you're sending to Solr.  In your example you mistakenly placed it in the schema.

FYI I use index time boosting as well as query time boosting.  Although index time boosting isn't something I can change on a whim, I've found it to be far easier to control the scoring than say function queries which would be the query time substitute if the boost is a function of particular field values.

~ David Smiley
Author: http://www.packtpub.com/solr-1-4-enterprise-search-server/


On Nov 18, 2009, at 6:40 AM, Ian Smith wrote:

> I have the following field configured in schema.xml:
> 
> <field name="title" type="text" indexed="true" stored="true"
> omitNorms="false" boost="3.0" />
> 
> Where "text" is the type which came with the Solr distribution.  I have
> not been able to get this configuration to alter any document scores,
> and if I look at the indexes in Luke there is no change in the norms
> (compared to an un-boosted equivalent).
> 
> I have confirmed that document boosting works (via SolrJ), but our field
> boosting needs to be done in the schema.
> 
> Am I doing something wrong (BTW I have tried using "3.0f" as well, no
> difference)?
> 
> Also, I have seen no debug output during startup which would indicate
> that fild boosting is being configured - should there be any?
> 
> I have found no usage examples of this in the Solr 1.4 book, except a
> vague discouragement - is this a deprecated feature?
> 
> TIA,
> 
> Ian
> 
> Web design and intelligent Content Management. www.twitter.com/gossinteractive 
> 
> Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower Street, Plymouth, PL1 1LG.  Company Registration No: 3553908 
> 
> This email contains proprietary information, some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this email, please notify the author by replying to this email. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on this email. 
> 
> Email transmission cannot be guaranteed to be secure or error free, as information may be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. This email and any files attached to it have been checked with virus detection software before transmission. You should nonetheless carry out your own virus check before opening any attachment. GOSS Interactive Ltd accepts no liability for any loss or damage that may be caused by software viruses.
> 
> 


RE: Index-time field boosting not working?

Posted by Ian Smith <Ia...@gossinteractive.com>.
Hi Otis, thanks for replying,

Well I'm pretty sure it was there (and documented) in the 1.3 era.
Strangely, it is still accepted in the Eclipse HTML editor, even for
attribute completion (if you can, try it).  But if it is truly
deprecated, we will have to reassess part of our system design :(

If you or anyone else here has any historical perspective on this, I'd
be interested to hear about it.

Regards,

Ian,

-----Original Message-----
From: Otis Gospodnetic [mailto:otis_gospodnetic@yahoo.com] 
Sent: 18 November 2009 22:55
To: solr-user@lucene.apache.org
Subject: Re: Index-time field boosting not working?

Can "boost" attribute really be specified for a field in the schema?  I
wasn't aware of that, and I don't see it on
http://wiki.apache.org/solr/SchemaXml .

Maybe you are mixing it with
http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.2
2field.22 ?

Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR



----- Original Message ----
> From: Ian Smith <Ia...@gossinteractive.com>
> To: solr-user@lucene.apache.org
> Sent: Wed, November 18, 2009 6:40:11 AM
> Subject: Index-time field boosting not working?
> 
> I have the following field configured in schema.xml:
> 
> 
> omitNorms="false" boost="3.0" />
> 
> Where "text" is the type which came with the Solr distribution.  I 
> have not been able to get this configuration to alter any document 
> scores, and if I look at the indexes in Luke there is no change in the

> norms (compared to an un-boosted equivalent).
> 
> I have confirmed that document boosting works (via SolrJ), but our 
> field boosting needs to be done in the schema.
> 
> Am I doing something wrong (BTW I have tried using "3.0f" as well, no 
> difference)?
> 
> Also, I have seen no debug output during startup which would indicate 
> that fild boosting is being configured - should there be any?
> 
> I have found no usage examples of this in the Solr 1.4 book, except a 
> vague discouragement - is this a deprecated feature?
> 
> TIA,
> 
> Ian
> 
> Web design and intelligent Content Management. 
> www.twitter.com/gossinteractive
> 
> Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower 
> Street, Plymouth, PL1 1LG.  Company Registration No: 3553908
> 
> This email contains proprietary information, some or all of which may 
> be legally privileged. It is for the intended recipient only. If an 
> addressing or transmission error has misdirected this email, please 
> notify the author by replying to this email. If you are not the 
> intended recipient you may not use, disclose, distribute, copy, print
or rely on this email.
> 
> Email transmission cannot be guaranteed to be secure or error free, as

> information may be intercepted, corrupted, lost, destroyed, arrive 
> late or incomplete or contain viruses. This email and any files 
> attached to it have been checked with virus detection software before 
> transmission. You should nonetheless carry out your own virus check 
> before opening any attachment. GOSS Interactive Ltd accepts no 
> liability for any loss or damage that may be caused by software
viruses.


Re: Index-time field boosting not working?

Posted by Otis Gospodnetic <ot...@yahoo.com>.
Can "boost" attribute really be specified for a field in the schema?  I wasn't aware of that, and I don't see it on http://wiki.apache.org/solr/SchemaXml .

Maybe you are mixing it with http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22field.22 ?

Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR



----- Original Message ----
> From: Ian Smith <Ia...@gossinteractive.com>
> To: solr-user@lucene.apache.org
> Sent: Wed, November 18, 2009 6:40:11 AM
> Subject: Index-time field boosting not working?
> 
> I have the following field configured in schema.xml:
> 
> 
> omitNorms="false" boost="3.0" />
> 
> Where "text" is the type which came with the Solr distribution.  I have
> not been able to get this configuration to alter any document scores,
> and if I look at the indexes in Luke there is no change in the norms
> (compared to an un-boosted equivalent).
> 
> I have confirmed that document boosting works (via SolrJ), but our field
> boosting needs to be done in the schema.
> 
> Am I doing something wrong (BTW I have tried using "3.0f" as well, no
> difference)?
> 
> Also, I have seen no debug output during startup which would indicate
> that fild boosting is being configured - should there be any?
> 
> I have found no usage examples of this in the Solr 1.4 book, except a
> vague discouragement - is this a deprecated feature?
> 
> TIA,
> 
> Ian
> 
> Web design and intelligent Content Management. www.twitter.com/gossinteractive 
> 
> Registered Office: c/o Bishop Fleming, Cobourg House, Mayflower Street, 
> Plymouth, PL1 1LG.  Company Registration No: 3553908 
> 
> This email contains proprietary information, some or all of which may be legally 
> privileged. It is for the intended recipient only. If an addressing or 
> transmission error has misdirected this email, please notify the author by 
> replying to this email. If you are not the intended recipient you may not use, 
> disclose, distribute, copy, print or rely on this email. 
> 
> Email transmission cannot be guaranteed to be secure or error free, as 
> information may be intercepted, corrupted, lost, destroyed, arrive late or 
> incomplete or contain viruses. This email and any files attached to it have been 
> checked with virus detection software before transmission. You should 
> nonetheless carry out your own virus check before opening any attachment. GOSS 
> Interactive Ltd accepts no liability for any loss or damage that may be caused 
> by software viruses.