[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Syncrepl nits with operational attributes (ITS#3289)
>For the moment you can just explicitly list
>creatorsName/CreateTimeStamp/etc in the syncrepl attrs, and omit
>anything else.
Yes, that seems to be the sensible option for now, i.e.:
attrs="*,creatorsName,createTimestamp,modifiersName,modifyTimestamp"
>Perhaps we need to add a "attrs=!foo" config syntax to strip certain
>attributes from the incoming records. I don't really like this approach
>because it requires too much manual intervention.
Agreed.
>Maybe better would be for syncrepl to have a hardcoded list of
>attributes that it ignores - e.g., all values that we know are
>dynamically generated (like hasSubordinates) and all values that are
>DSA-specific (e.g. subschemaSubentry), so that attrs=*,+ will work
>without hassles.
Another approach that we use is to not return computed (dynamic)
operational attributes if the sync control is present. But I also
think that you do not want dynamic attributes to in any case be
printed to disk.
-- Luke