[teiid-issues] [JBoss JIRA] Commented: (TEIID-217) LDAP Connector should provide a way to retrieve all values of an attribute that appears multiple times within a search result
[
https://jira.jboss.org/jira/browse/TEIID-217?page=com.atlassian.jira.plug...
]
Michael Walker commented on TEIID-217:
--------------------------------------
FYI, I implemented the multivalued-concat approach ( return a single row with an ordered,
delimited list of all values) as a test, and it generally works, with the caveat that
returning all values can take a long time. For example
select group_dn, user_dn from groups where user_dn like '%abc%
where the user DN is the multi-valued attribute, can be time-consuming if the user is in a
large number of groups, and those groups have many members. It's worth noting that in
this example, the LIKE criteria is pushed down, so the list of groups can be quickly
returned. However, it's the population of the user_dn string that takes a long time,
since each grab of the next multivalued attribute is a separate outcall.
Perhaps this can be tuned, just thought I'd add it to the case notes, ping me if you
want the implementation details.
LDAP Connector should provide a way to retrieve all values of an
attribute that appears multiple times within a search result
-----------------------------------------------------------------------------------------------------------------------------
Key: TEIID-217
URL: https://jira.jboss.org/jira/browse/TEIID-217
Project: Teiid
Issue Type: Feature Request
Components: LDAP Connector
Affects Versions: 6.0.0
Reporter: Michael Walker
Priority: Minor
Fix For: 6.3
If an attribute appears more than once, we should have some way to return all values.
Currently, we only return one value, with no rhyme, reason, or determinism as to which one
gets returned. Implementing this is difficult when multiple attributes appear more than
once, of course. But a simple example of where this problem rears it's head is in
modeling LDAP groups. Groups typically have repeating attributes to represent each member,
and it would be nice to query all members of a given group, but impossible to do so with
the current logic.
A sophisticated solution would create a normalized view of a DN, breaking out
multi-valued attributes into a separate table that could be joined by a primary key. A
simple solution might allow attributes to be flagged as "multi-valued", in which
case, they could be maintained in a single denormalized table that represents all values
in the DN.
If we build an importer for LDAP, we should consider how to best handle this issue in the
importer design.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira