June 2015 - teiid-issues - Jboss List Archives

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

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3411: --------------------------------- > 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.12 > > > 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)

10 years, 9 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3411: --------------------------------------- The feature is complete on the ldap-multi-value branch. The translator property has been removed and all behavior will be driven by extension metadata. There are two new engine level constructs and 3 new ldap extension properties. This work will be pulled into 8.12 as it was too late for 8.11. Here's an example of the usage: {code} CREATE foreign table users (username string primary key options (nameinsource 'cn'), surname string options (nameinsource 'sn'), ...) options (nameinsource 'ou=users,dc=example,dc=com'); CREATE foreign table groups (groupname string primary key options (nameinsource 'cn'), description string, ...) options (nameinsource 'ou=groups,dc=example,dc=com'); CREATE foreign table membership (username string options (nameinsource 'cn'), groupname options (nameinsource 'memberOf', SEARCHABLE 'equality_only', "teiid_rel:partial_filter" true, "teiid_ldap:unwrap" true, "teiid_ldap:dn_prefix" 'ou=groups,dc=example,dc=com', "teiid_ldap:rdn_type" 'cn'), foreign key (username) references users (username), foreign key (groupname) references groups (groupname)) options (nameinsource 'ou=users,dc=example,dc=com'); {code} Inner join support would be allowed between users and membership. SEARCHABLE 'equality_only' - indicates that only equality predicates should be pushed down. Needed for openldap and apacheds as dn attributes have search restrictions, may not be needed by others. "teiid_rel:partial_filter" true - indicates to the engine that if a predicate is pushed down and the value is projected out that it may contain more entries than expected and the relevant predicates need re-evaluated in the engine. "teiid_ldap:unwrap" true - indicates to the ldap translator that the multivalued attribute should be expanded into multiple rows To us rdn values, rather than dn for keys there are also the properties: "teiid_ldap:rdn_type" 'cn' - indicates the rdn to extract. If the entry suffix does not match this rdn type, then no row will be produced. "teiid_ldap:dn_prefix" 'ou=groups,dc=example,dc=com' - if rdn_type is specified, this indicates that the values should match this prefix, no row will be produced for a non-matching entry These latter two properties may need some refinement in their implementation as we're simply using the LdapName class for the value parsing, which may be unnecessarily heavy weight. As for backporting, I will try to squash these into a single commit for the merge to master, or you can just take the original commit 6a3de7f and the two commits on the branch. > 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.12 > > > 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)

10 years, 9 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3411: ---------------------------------- Fix Version/s: 8.12 (was: 8.11) > 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.12 > > > 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)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3523) Statement -> executeBatch method throws an NPE

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-3523?page=com.atlassian.jira.plugin... ] Juraj Duráni updated TEIID-3523: -------------------------------- Priority: Blocker (was: Major) > Statement -> executeBatch method throws an NPE > ---------------------------------------------- > > Key: TEIID-3523 > URL: https://issues.jboss.org/browse/TEIID-3523 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.3 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Attachments: server.log > > > The method executeBatch() of class Statement throws an NPE. Please see the log in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3523) Statement -> executeBatch method throws an NPE

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-3523: ----------------------------------- Summary: Statement -> executeBatch method throws an NPE Key: TEIID-3523 URL: https://issues.jboss.org/browse/TEIID-3523 Project: Teiid Issue Type: Bug Affects Versions: 8.7.3 Reporter: Juraj Duráni Assignee: Steven Hawkins The method executeBatch() of class Statement throws an NPE. Please see the log in the attachment. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3411?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3411: --------------------------------------- I have the extraction or rdn values working as well (currently based upon rdn type and dn prefix values - we could also use a pattern). From what I can see of openldap and apacheds they only support equality matches against a dn value, so we'll need an additional restriction either in the form or searchability or extension metadata to refine to something more narrow than searchable. > 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)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3510) Move the Embedded examples into separate repository

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3510?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-3510. -------------------------------- Resolution: Done > Move the Embedded examples into separate repository > ---------------------------------------------------- > > Key: TEIID-3510 > URL: https://issues.jboss.org/browse/TEIID-3510 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 8.11 > > > Create a separate repository for embedded examples, define a maven BOM file for the dependencies management of all examples, and prepare for further refinement like add xa datasources support, add OAuth/REST service, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3522) Provide Data Aggregation Extension to OData V4

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3522: ----------------------------------- Summary: Provide Data Aggregation Extension to OData V4 Key: TEIID-3522 URL: https://issues.jboss.org/browse/TEIID-3522 Project: Teiid Issue Type: Feature Request Components: OData Reporter: Ramesh Reddy Assignee: Ramesh Reddy OData V4 specification defines extension for Data Aggregation http://docs.oasis-open.org/odata/odata-data-aggregation-ext/v4.0/cs01/oda... Teiid should provide support for this extension. There is Olingo support on this yet. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3506) Move downloads off of sourceforge

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3506?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3506: --------------------------------------- > Looks like these two are still pointing to the sourceforge. That has been corrected. > So, we not not going to use maven based downloads? There didn't seem to be a consensus, so I defaulted to using a separate instance (also we've had trouble with nexus). It does look like all the artifacts are being uploaded though, so it would be fine to use it instead. > Move downloads off of sourceforge > --------------------------------- > > Key: TEIID-3506 > URL: https://issues.jboss.org/browse/TEIID-3506 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We need to move our downloads off of sourceforge onto an infrastructure we have more control over. This can be as simple as just pointing to the maven artifacts (which means that the server uber dist needs added) or we can start using the jboss.org download site. > More than likely we'll leave the old downloads in place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3506) Move downloads off of sourceforge

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3506?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3506: ------------------------------------- Looks like these two are still pointing to the sourceforge. Teiid Runtime 8.11 CR1 and 8.11 CR1 With EAP So, we not not going to use maven based downloads? > Move downloads off of sourceforge > --------------------------------- > > Key: TEIID-3506 > URL: https://issues.jboss.org/browse/TEIID-3506 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > > We need to move our downloads off of sourceforge onto an infrastructure we have more control over. This can be as simple as just pointing to the maven artifacts (which means that the server uber dist needs added) or we can start using the jboss.org download site. > More than likely we'll leave the old downloads in place. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015