[teiid-issues] [JBoss JIRA] (TEIID-3411) LDAP translator and multi-valued arrays

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076037#comment-13076037 ] 

Steven Hawkins commented on TEIID-3411:
---------------------------------------

Started additional commits in https://github.com/teiid/teiid/tree/ldap-multi-value

The current logic supports pushdown of joins with the restriction that it must be an inner join on the key.  Also added support for the engine to compensate for the partial filtering when predicates are specified against a multi-valued attribute.  So with the DDL of:

create foreign table users (dn string primary key, uid string, title string) options (nameinsource 'ou=people,dc=example,dc=com')

create foreign table user_group (user_dn string options (nameinsource 'dn'), group_dn string options (nameinsource 'memberOf', "teiid_rel:partial" true), foreign key (user_dn) references users (dn)) options (nameinsource 'ou=people,dc=example,dc=com')

Queries such as:

select user_dn, group_dn from user_group where group_dn like ?

select dn, title, group_dn from user, user_group where user.dn = user_group.dn and group_dn = ?

Will pushdown to just a ldap query against the user context and return the expected results with the post filtering on group_dn.  The changes have not yet introduced the "teiid_ldap:unnest" property, as it may make more sense to keep refining this into an engine responsibility.

There haven't been any changes yet to allow for the use of extracted rdn values for the keys rather than full dns.

> LDAP translator and multi-valued arrays
> ---------------------------------------
>
>                 Key: TEIID-3411
>                 URL: https://issues.jboss.org/browse/TEIID-3411
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: LDAP Connector
>            Reporter: Debbie Steigner
>            Assignee: Steven Hawkins
>             Fix For: 8.11
>
>
> The problem is with how multi-valued attribute from the LDAP response is handled. They don't want to have the data mapped to an array or multivalued-concat and then transformed into another table to get the unique values. There is an issue with the translator as it should handle multivalued attribute, by simply creating multiple rows for each value of the multivalued attribute.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)