On 9 May 2012 21:04, Andrej Golovnin wrote:
> Hi Emmanuel,
>
>> Can you open a JIRA issue to clarify this in
>> http://docs.jboss.org/hibernate/search/4.1/reference/en-US/html_single/#basic-mapping
>> ?
>> Even better, can you propose the change as a GitHub pull request? :)
>
> Sure. :-)
>
>>>
>
Hi Emmanuel,
> Can you open a JIRA issue to clarify this in
> http://docs.jboss.org/hibernate/search/4.1/reference/en-US/html_single/#basic-mapping
> ?
> Even better, can you propose the change as a GitHub pull request? :)
Sure. :-)
>>
>> @Field(boost=@Boost(1.2f), norms = Norms.NO)
>> privat
On 9 mai 2012, at 00:43, Andrej Golovnin wrote:
> Hi Hardy,
>
>> It depends. Maybe you want to boost any of these fields ad index time.
>
> OK, what about the document id? It is indexed with NOT_ANALYZED_NO_NORMS.
> As far as I understand (please correct me if I'm wrong) to boost fields at
> i
Hi Sanne,
> Proposal for next versions: allow @Stereotype - like user annotations?
> We would let the user define custom annotations to stack/combine
> multiple framework annotations, possibly centralizing what the
> "default" is for your app and reduce the amount of code people have to
> pile on
Hi Hardy,
> It depends. Maybe you want to boost any of these fields ad index time.
OK, what about the document id? It is indexed with NOT_ANALYZED_NO_NORMS.
As far as I understand (please correct me if I'm wrong) to boost fields at
index time
norms must be enabled for those fields. And because H
> Proposal for next versions: allow @Stereotype - like user annotations?
> We would let the user define custom annotations to stack/combine
> multiple framework annotations, possibly centralizing what the
> "default" is for your app and reduce the amount of code people have to
> pile on each gette
On Tue, May 8, 2012 at 12:27 PM, Sanne Grinovero wrote:
> Proposal for next versions: allow @Stereotype - like user annotations?
> We would let the user define custom annotations to stack/combine
> multiple framework annotations, possibly centralizing what the
> "default" is for your app and reduc
On 8 May 2012 10:43, Guillaume Smet wrote:
> Hi,
>
> On Tue, May 8, 2012 at 10:20 AM, Hardy Ferentschik
> wrote:
>>> Sanne also suggested an alternative solution. We may introduce a new global
>>> option which would define the default value for Field#norms(). The default
>>> value of this option
Hi,
On Tue, May 8, 2012 at 10:20 AM, Hardy Ferentschik wrote:
>> Sanne also suggested an alternative solution. We may introduce a new global
>> option which would define the default value for Field#norms(). The default
>> value of this option would be obviously YES. Users like me could change it
On May 7, 2012, at 11:47 PM, Andrej Golovnin wrote:
> the default value of norms() in the Field annotation is defined to YES.
> I doubt it is always needed, e.g. if you have an Enum field, do you really
> need norms for it? The same applies to long/int, boolean, date, OID fields
> and very short
Hi all,
the default value of norms() in the Field annotation is defined to YES.
I doubt it is always needed, e.g. if you have an Enum field, do you really
need norms for it? The same applies to long/int, boolean, date, OID fields
and very short fields like a code of the country.
I have already a
11 matches
Mail list logo
