April 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3419) Add ability to set a default role across all VDBs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3419?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3419: --------------------------------------- > Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all. The notion of a default role for all vdbs only makes sense if it has a general grant all (added in 8.7). Practically speaking they are just wanting a way to ensure that data roles are enabled. Seems like this would be just as easy to satisfy with a server option that validated data roles were in use on vdb deployment otherwise reject the deployment. > Add ability to set a default role across all VDBs > ------------------------------------------------- > > Key: TEIID-3419 > URL: https://issues.jboss.org/browse/TEIID-3419 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Marc Shirley > Assignee: Steven Hawkins > > There should be an ability to either set a default role across the server, or to restrict access by default. For example, all VDBs have a default user role that is applied before the VDB specific roles are. Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3419) Add ability to set a default role across all VDBs

by Marc Shirley (JIRA)

Marc Shirley created TEIID-3419: ----------------------------------- Summary: Add ability to set a default role across all VDBs Key: TEIID-3419 URL: https://issues.jboss.org/browse/TEIID-3419 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Marc Shirley Assignee: Steven Hawkins There should be an ability to either set a default role across the server, or to restrict access by default. For example, all VDBs have a default user role that is applied before the VDB specific roles are. Alternatively, there could be a system wide flag that toggles the behavior of VDBs when no roles are defined between accessible to all or denied to all. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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.11 Component/s: LDAP Connector Affects: Documentation (Ref Guide, User Guide, etc.) > 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.11#6341)

9 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: --------------------------------------- Added a translator option - unwrapMultiValued - to expand a single array value to rows. > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIID-3411 > URL: https://issues.jboss.org/browse/TEIID-3411 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > 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.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3412) Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3412?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3412: ------------------------------------- Can you check if there are any other options? I think we need to think in general as to how we can support any "ODBC" source not just MS Access. As far UcanAccess, looks like an active project with active commit log, so that is good news. If any issues, you can check if you can work with the commiter of the to get the fixes done. If we go with UcanAcess, create extended translator in the "translator-jdbc" based "jdbc-simple" or "jdbc-ani", and further refine capabilities to match the UcanAccess support. > Change MS Access to use jackcess, since ODBC-JDBC bridge is removed in JDK 1.8 > ------------------------------------------------------------------------------ > > Key: TEIID-3412 > URL: https://issues.jboss.org/browse/TEIID-3412 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Kylin Soong > > In JDK 1.8, the ODBC-JDBC bridge is removed, so accessing MS Access using this method will not be available. An alternative, open source, driver that can be used is: http://jackcess.sourceforge.net > In nexus: > <dependency> > <groupId>com.healthmarketscience.jackcess</groupId> > <artifactId>jackcess</artifactId> > <version>2.0.9</version> > </dependency> > This may require a new translator, but won't be know until a deeper look is done. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 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... ] Work on TEIID-3411 started by Steven Hawkins. --------------------------------------------- > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIID-3411 > URL: https://issues.jboss.org/browse/TEIID-3411 > Project: Teiid > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Steven Hawkins > > 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.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3418?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3418. ----------------------------------- Resolution: Done Added a mechanism during resolve just for ODBC so that positional group by will be allowed. > Allow positional group by for odbc > ---------------------------------- > > Key: TEIID-3418 > URL: https://issues.jboss.org/browse/TEIID-3418 > Project: Teiid > Issue Type: Quality Risk > Components: ODBC > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3418) Allow positional group by for odbc

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3418: ------------------------------------- Summary: Allow positional group by for odbc Key: TEIID-3418 URL: https://issues.jboss.org/browse/TEIID-3418 Project: Teiid Issue Type: Quality Risk Components: ODBC Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.11 A remaining item for TEIID-3073 was that since tableau assumes we are postgresql they will use the pg specific positional group by references. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3414) Oracle should use hextoraw

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3414?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3414. -------------------------------- Resolution: Done > Oracle should use hextoraw > -------------------------- > > Key: TEIID-3414 > URL: https://issues.jboss.org/browse/TEIID-3414 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.2, 8.11 > > > Oracle does not support the standard varbinary literal syntax and generally needs to use the hextoraw conversion function. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3414) Oracle should use hextoraw

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3414?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3414: ---------------------------------- > Oracle should use hextoraw > -------------------------- > > Key: TEIID-3414 > URL: https://issues.jboss.org/browse/TEIID-3414 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Oracle does not support the standard varbinary literal syntax and generally needs to use the hextoraw conversion function. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2015