|
Home > Archive > Apache Directory Project > October 2006 > WARN: Attribute does not have normalizer
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WARN: Attribute does not have normalizer
|
|
| Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@ 2006-10-17, 1:11 pm |
| I just installed the latest V1.0 release on Windows.
I'm running DS embedded in jBoss. I am experiencing a number of log4j warnings that I did not see in RC3.
The first batch or WARNs seem to relate to the Bootstrap schema loader and the second batch relate to the creation of the system partition.
What have I done wrong?
<snip>
BootstrapAttributeTypeRegistry) Attribute teletexTerminalIdentifier does not have normalizer : using NoopNormalizer
BootstrapAttributeTypeRegistry) Attribute photo does not have normalizer : using NoopNormalizer
BootstrapAttributeTypeRegistry) Attribute facsimileTelephoneNumber does not have normalizer : using NoopNormalizer
BTreePartition) Using default cache size of 100 for index on attribute objectClass
BTreePartition) Using default cache size of 100 for index on attribute 1.2.6.1.4.1.18060.1.1.1.3.4
BTreePartition) Using default cache size of 100 for index on attribute 1.2.6.1.4.1.18060.1.1.1.3.1
<snip>
TIA
Simon T
| |
| Emmanuel Lecharny 2006-10-17, 1:11 pm |
| Hi !
So far, you haven't done anything wrong. The warnings are just here to warn
about the fact that, as we don't have declared any normalizer for sme
attributes, ADS will just use a kind of Identity normalizer (ie, a
normalizer that don't normalize  . It's always possible to declare some
normalizer into the schema files, but I'm not sure this is necessary to
normalize a photo (!?), for instance.
FYI, normalizer are used to transform an attribute value in a way that allow
comparizons between values. For instance, if an attribute is case
insensitive, then the normalization will transform the value to a lower
cased string, and every further comparizons will be done using lower cased
comparizons.
I think that you just get more logs just because 1.0 is just a little bit
more verbose.
Emmanuel
On 10/17/06, Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@public.gmane.org <
Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@public.gmane.org> wrote:
>
> I just installed the latest V1.0 release on Windows.
>
> I'm running DS embedded in jBoss. I am experiencing a number of log4j
> warnings that I did not see in RC3.
>
> The first batch or WARNs seem to relate to the Bootstrap schema loader and
> the second batch relate to the creation of the system partition.
>
> What have I done wrong?
>
> <snip>
> BootstrapAttributeTypeRegistry) Attribute teletexTerminalIdentifier does
> not have normalizer : using NoopNormalizer
> BootstrapAttributeTypeRegistry) Attribute photo does not have normalizer :
> using NoopNormalizer
> BootstrapAttributeTypeRegistry) Attribute facsimileTelephoneNumber does
> not have normalizer : using NoopNormalizer
> BTreePartition) Using default cache size of 100 for index on attribute
> objectClass
> BTreePartition) Using default cache size of 100 for index on attribute
> 1.2.6.1.4.1.18060.1.1.1.3.4
> BTreePartition) Using default cache size of 100 for index on attribute
> 1.2.6.1.4.1.18060.1.1.1.3.1
> <snip>
>
>
> TIA
>
> Simon T
>
--
Cordialement,
Emmanuel Lécharny
| |
| Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@ 2006-10-17, 1:11 pm |
| Emmanuel
Thanks for the prompt reply.
1. IMHO, a level of INFO would be better for the 'normalizer' entries - would you agree? My users are equally sensitive to both ERROR and WARN log entries.
2. I think the BTreePartition WARNs could be avoided if the code that creates the system partition explicitly sets the cache size on the index attributes.
I know this as I create a custom partition and it was generating WARN messages! I see from the Spring configuration file that it sets the index
attributes. Is there a way to ensure the system partition sets the index attributes when I'm not using Spring?
Thanks
Simon T
17 October 2006 13:53
To: "Apache Directory Developers List" <dev-aYN4UCa7k1r1N9kud6OZbmD2FQJk+8+b@public.gmane.org>
cc:
From: "Emmanuel Lecharny" <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: WARN: Attribute does not have normalizer
Hi !
So far, you haven't done anything wrong. The warnings are just here to warn about the fact that, as we don't have declared any normalizer for sme attributes, ADS will just use a kind of Identity normalizer (ie, a normalizer that don't normalize . It's always possible to declare some normalizer into the schema files, but I'm not sure this is necessary to normalize a photo (!?), for instance.
FYI, normalizer are used to transform an attribute value in a way that allow comparizons between values. For instance, if an attribute is case insensitive, then the normalization will transform the value to a lower cased string, and every further comparizons will be done using lower cased comparizons.
I think that you just get more logs just because 1.0 is just a little bitmore verbose.
Emmanuel
On 10/17/06, Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@public.gmane.org <Simon.Temple@saaconsultants.com> wrote:
I just installed the latest V1.0 release on Windows.
I'm running DS embedded in jBoss. I am experiencing a number of log4j warnings that I did not see in RC3.
The first batch or WARNs seem to relate to the Bootstrap schema loader and the second batch relate to the creation of the system partition.
What have I done wrong?
<snip>
BootstrapAttributeTypeRegistry) Attribute teletexTerminalIdentifier does not have normalizer : using NoopNormalizer
BootstrapAttributeTypeRegistry) Attribute photo does not have normalizer : using NoopNormalizer
BootstrapAttributeTypeRegistry) Attribute facsimileTelephoneNumber does not have normalizer : using NoopNormalizer
BTreePartition) Using default cache size of 100 for index on attribute objectClass
BTreePartition) Using default cache size of 100 for index on attribute 1.2.6.1.4.1.18060.1.1.1.3.4
BTreePartition) Using default cache size of 100 for index on attribute 1.2.6.1.4.1.18060.1.1.1.3.1
<snip>
TIA
Simon T
--
Cordialement,
Emmanuel Lécharny
| |
| Emmanuel Lecharny 2006-10-17, 7:11 pm |
| >
> 1. IMHO, a level of INFO would be better for the 'normalizer' entries
> - would you agree? My users are equally sensitive to both ERROR and WARN
> log entries.
>
Yep, this can be changed. Can you fill a JIRA for that, so we won't loose
the request ?
2. I think the BTreePartition WARNs could be avoided if the code that
> creates the system partition explicitly sets the cache size on the index
> attributes.
>
Sure. INFO seems much more adequat for defaulting a value.
I know this as I create a custom partition and it was generating WARN
> messages! I see from the Spring configuration file that it sets the index
> attributes. Is there a way to ensure the system partition sets the
> index attributes when I'm not using Spring?
>
Hmmm. AFAIR, index are always defaulted for some attributes in system
partition like ObjectClass, but not for any other attribute (I may be wrong,
this has to be doublec checked). If you don't use Spring, but embed ADS?
then you will have to set those index programaticaly. I'm not an expert in
this part of the server, but I'm sure someone else can confirm that.
Emmanuel
Thanks
>
> Simon T
>
>
> *17 October 2006 13:53
> To: "Apache Directory Developers List" <dev-aYN4UCa7k1r1N9kud6OZbmD2FQJk+8+b@public.gmane.org>
> cc:
> From: "Emmanuel Lecharny" <elecharny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> Subject: Re: WARN: Attribute does not have normalizer*
>
> Hi !
>
> So far, you haven't done anything wrong. The warnings are just here to
> warn about the fact that, as we don't have declared any normalizer for sme
> attributes, ADS will just use a kind of Identity normalizer (ie, a
> normalizer that don't normalize . It's always possible to declare some
> normalizer into the schema files, but I'm not sure this is necessary to
> normalize a photo (!?), for instance.
>
> FYI, normalizer are used to transform an attribute value in a way that
> allow comparizons between values. For instance, if an attribute is case
> insensitive, then the normalization will transform the value to a lower
> cased string, and every further comparizons will be done using lower cased
> comparizons.
>
> I think that you just get more logs just because 1.0 is just a little bit
> more verbose.
>
> Emmanuel
>
> On 10/17/06, Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@public.gmane.org <
> Simon.Temple-bNHniqfy2KDk7dXyY5I9mNBPR1lH4CV8@public.gmane.org> wrote:
>
>
>
> --
> Cordialement,
> Emmanuel Lécharny
>
--
Cordialement,
Emmanuel Lécharny
|
|
|
|
|