[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)