I just looked at the documentation on creating an index for my id attribute
and am a little confused. I'm looking at the Indexing Attributes section of
the tuning
guide<http://directory.apache.org/apacheds/1.5/91-performance-tuning.html>,
and the documentation does not seem to match up with what I'm seeing in my
1.5.4 installation.
In the tuning docs it says that I need to add an entry to my server.xml file
similar to the following...
<property name="indexedAttributes">
<set>
<bean
class="org.apache.directory.server.core.partition.impl.btree.MutableIndexConfiguration">
<property
name="attributeId"><value>1.2.6.1.4.1.18060.1.1.1.3.1</value></property>
<property name="cacheSize"><value>100</value></property>
</bean>
However, in my server.xml file it looks like an index is setup in the
following way...
<indexedAttributes>
<jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.1"
cacheSize="100"/>
<jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.2"
cacheSize="100"/>
Is this document incorrect, or am I missing something? Thanks.
- Kevin
On Mon, Mar 9, 2009 at 9:18 AM, Emmanuel Lecharny <[email protected]>wrote:
> Kevin Kovach wrote:
>
>> Emmanuel,
>>
>> I went with caceExactMatch and that seems to have helped. I'm going to do
>> a
>> little more testing with removing and re-adding the equality rule to make
>> sure, then see what I can do about creating a JIRA with all the relevant
>> information. Thanks for the help.
>>
>> - Kevin
>>
>>
>> On Sat, Mar 7, 2009 at 10:01 PM, Emmanuel Lecharny <[email protected]
>> >wrote:
>>
>>
>>
>>> Kevin Kovach wrote:
>>>
>>>
>>>
>>>> Sure. Here it is.
>>>>
>>>> dn: m-oid=MYOID.1.15, ou=attributeTypes, cn=custom, ou=schema
>>>> objectclass: metaAttributeType
>>>> objectclass: metaTop
>>>> objectclass: top
>>>> m-oid: MYOID.1.15
>>>> m-name: myid
>>>> m-syntax: 1.3.6.1.4.1.1466.115.121.1.15
>>>> m-singleValue: TRUE
>>>>
>>>>
>>>>
>>>>
>>> Sounds pretty standard... Could you add a
>>>
>>> m-equality: caseIgnoreMatch
>>>
>>> element, and see if you get better results ? I suspect that without any
>>> comparator, you might get the kind of error you had.
>>>
>>> Also what would be valuable is to create a JIRA, including the schema and
>>> the data your are using, plus the error you get. I don't think that the
>>> server behavior is correct and at least, the error message is
>>> inapropriate.
>>>
>>> Thanks !
>>>
>>>
>> Another thing : check that you have an Index on the ObjectClass object.
> That could help too. (surprizingly, this index is not always present...)
>
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>
--
"He has all the virtues I dislike and none of the vices I admire."
-- Winston Churchill