[
https://issues.apache.org/jira/browse/DIRSERVER-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413027#comment-15413027
]
John Peter edited comment on DIRSERVER-2162 at 8/9/16 6:32 AM:
---------------------------------------------------------------
Yes you are write. Jira is reformatting that to bold. So it has the asterix on
both ends.
If I leave the asterix in the beginning but remove it from the end it helps a
bit but not much. The problem still is that if I have the (objectClass=person)
part in it the search takes much much longer. If I use (objectClass=*) the
search result is instant.
was (Author: jmrpet):
Yes you are write. Jira is reformatting that to bold. So it has the asterix on
both ends.
If I leave the asterix in the beginning but remove it from the end it helps a
bit but not much. The problem still is that if I have the (objectClass=person)
part in it the search takes much much longer. If I use (objectClass=*) the
search result is istant.
> Searcing for users using ObjectClass=person takes long
> ------------------------------------------------------
>
> Key: DIRSERVER-2162
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2162
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M20
> Reporter: John Peter
>
> When we do the below query the result takes long. Around 10-50 seconds.
> Search base: ou=users,dc=xxx,dc=fi
> Filter (&(cn=*USERNAME*)(objectClass=person))
> Scope: Subtree
> However the below query returns the result immediately
> Search base: ou=users,dc=xxx,dc=fi
> Filter (&(cn=*USERNAME*)(objectClass=*))
> Scope: Subtree
> Looking at the Partition settings it has Indexed attributes ObjectClass and
> cn.
> First both queries took long. Then we added cn to the index and rebooted
> apacheDS and the second query got fast.
> It seems like a bug that using ObjectClass in the query makes it slow all
> tough it is in the index.
> It seems something similar was reported before DIRSERVER-2048, but it says
> it's fixed in M20 which we are using.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)