[
https://issues.apache.org/jira/browse/DIRSTUDIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494294
]
Matt Green commented on DIRSTUDIO-95:
-------------------------------------
The LS tool is a fantastic piece of work. Can you tell me what you are
targeting its user base for?
The reason I am asking this is because 100K LDAP entries is not really that
large of a request --
The reason that I am using the LS tool is that I am searching on a filter and
asking for a set of attributes returned for each entry matching the filter.
If ldapsearch is used and the entry has all attributes then they are all
returned but if the entry does not have all attributes then only the attributes
present are returned.
The LS tool is great in that even if the entry does not have the attribute
present it still returns comma delimited place holder for where the missing
attribute value would be for that entry.
For example if this represents the attributes requested from ldap query "cn,
givenname, sn, telephonenumber, description" on the below entries
dn: uid=matt, ou=people, o=cc.com
cn: matt green
givenname: matt
sn: green
telephonenumber: 789.456.1234
description: operator
dn: uid=dave, ou=people, o=cc.com
cn: dave green
givenname: dave
sn: green
description: manager
Your tools CSV output provide this
"matt green", "matt", "green", "789.456.1234", "operator"
"dave green", "dave", "green", ,"manager"
I am trying to provide a simple tool for admins to use for data manipulation
and extraction. The tool needs to be able to operate on datasets up to 250K
entries and be able to output
the results in a comma delimited/quoted format. The Softterra browser can
perform on the dataset size but does not have the fantastic other qualities
that LS has. Is there anything
that can be done to enable this type of capability?
I work with LDAP directories of all sorts in fairly large organizations and
typically have to work on large number of entries at a time which usually end
up having to construct a
combination of shell and native ldap commands that take alot of time to
construct. If the intent of LS is to be a tool to be used by main stream LDAP
engineers it would seem
reasonable to architect this ability into this great product. I do realize that
this is a .8 version so please take this as a recommendation for future
direction. In the meantime it looks like I
have to go back to ldapsearch, grep, awk and sed land :-(
Thanks again to all for your prompt resonse to my questions -- matt
> Not returning large queries
> ---------------------------
>
> Key: DIRSTUDIO-95
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-95
> Project: Directory LDAP Studio
> Issue Type: Bug
> Components: ldapstudio-browser
> Affects Versions: 0.8.0
> Environment: Client where software installed: Windows XP sp2
> LDAP host: Sun Directory 5.1 sp2
> Reporter: Matt Green
> Attachments: mgreen, My LS configuration.jpg, screenshot-1.jpg
>
>
> When performing a query against the LDAP server (consumer) the number of
> returned entries returned from a search looks to be page limiting the results
> to approximately 500 entries. The requirement is for a filter to return over
> 100K entries ...that is not working. The directory instance is set to allow
> the return of 300K entries and a search time out of 3600 seconds.
> The initial search results may return < 500 users in a search time of <10
> seconds.
> Have a look and let me know what you find. >> Matt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
