[
https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3411:
---------------------------------------
Pulled the initial commit from 6_2-8.7.x as the work is not complete with respect to
customer needs.
The desired state is to express an intersection table based upon a multi-valued attribute.
The proposed DDL for this would include extension metadata to specify the attribute to be
expanded into rows as well as an option to extract a part of the value (cn for example
rather than a fully qualified name). This is more explicit than the initial check-in for
this issue (which was motivated to just give a quick solution - as managing extension
metadata can be more difficult than just enabling a translator property).
And they also want support for filtering operations against the multi-valued attribute -
which was not supported by the initial commit as all multi-attribute are still returned
for each top level entity that matches the filter.
Update support is not expected however, but could be supported if we require the
intersection table to only represent the foreign key columns.
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)