directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Seelmann <m...@stefan-seelmann.de>
Subject Re: Error: I do not know how to handle NameAndOptionalUID normalization
Date Mon, 19 Mar 2018 20:57:12 GMT
On 03/19/2018 05:32 PM, Emmanuel L├ęcharny wrote:
> To be more specific :
> 
> when the schema partition is initialized, we read all the associated
> files. Many of them
> 
> For instance, when we read the apacheDnsDomainName ldif file, which is in :
> 
> ou=schema
>   |
>   +-- cn=apachedns
>         |
>         +-- ou=attributeTypes
>                |
>                +-- m-oid=1.3.6.1.4.1.18060.0.4.2.2.6.ldif
> 
> we get that entry :
> 
> 
> dn:m-oid=1.3.6.1.4.1.18060.0.4.2.2.6,ou=attributeTypes,cn=apachedns,ou=schema
> m-usage: USER_APPLICATIONS
> m-oid: 1.3.6.1.4.1.18060.0.4.2.2.6
> m-name: apacheDnsSoaMName
> m-description: The domain name of the name server that was the primary
> source of data for this zone
> m-obsolete: FALSE
> m-equality: caseIgnoreIA5Match
> m-supattributetype: apacheDnsDomainName
> entryParentId: bc4ca0cc-66e5-4c8e-8f16-b0d5f77e0ac9
> m-singlevalue: TRUE
> createTimestamp: 20150708131906.591Z
> m-syntax: 1.3.6.1.4.1.1466.115.121.1.26
> m-nousermodification: FALSE
> m-collective: FALSE
> objectclass: metaAttributeType
> objectclass: metaTop
> objectclass: top
> entryUUID: bac4890c-08a4-4957-bca3-f441674c2569
> creatorsname: uid=admin,ou=system
> entryCSN: 20150708131902.875000Z#000001#000#000000
> 
> 
> At this piont, we need to process the following attributes and their
> values :
> 
> 
> m-supattributetype: apacheDnsDomainName
> 
> where the apacheDnsDomainName is not present in the SchemaManager,
> because the apachedns schema is not enabled. This generates the error
> you can see, which is not actually an error, but a problem with a non
> existant schema element definition.
> 
> Now, the question is : should we make that a warning instead of an
> error? (Note that in this very case, we continue to process the schema,
> it's a non blocking error).
> 
> wdyt ?

Is that a chicken-egg problem? To initialize the scheama partition we
need the schema?

How does it work for the enabled schemas? Are they present before the
schema partition is loaded?

We init the SchemaManager with the SchemaLoader. Can't we just enable
all schemas for initializing the schema partition?

Kind Regards,
Stefan


Mime
View raw message