May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2953) DB2: doesn't work with composite key

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2953?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2953. ----------------------------------- Fix Version/s: 8.7.1 8.8 Resolution: Done Removed the relevant support from the db2 translator. > DB2: doesn't work with composite key > ------------------------------------- > > Key: TEIID-2953 > URL: https://issues.jboss.org/browse/TEIID-2953 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: DB2 with Teiid 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > If I run a sql with composite key in DB2, Teiid translates it to something incorrect DB2 sql. > However, it works for postgres, mysql, and oracle. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2953) DB2: doesn't work with composite key

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2953?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2953: --------------------------------------- Support looks like it was inappropriately enabled with TEIID-2558, so that will be reverted with this issue. > DB2: doesn't work with composite key > ------------------------------------- > > Key: TEIID-2953 > URL: https://issues.jboss.org/browse/TEIID-2953 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: DB2 with Teiid 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > > If I run a sql with composite key in DB2, Teiid translates it to something incorrect DB2 sql. > However, it works for postgres, mysql, and oracle. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2953) DB2: doesn't work with composite key

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2953?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2953: ---------------------------------- I am using DB2 10.1 > DB2: doesn't work with composite key > ------------------------------------- > > Key: TEIID-2953 > URL: https://issues.jboss.org/browse/TEIID-2953 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: DB2 with Teiid 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > > If I run a sql with composite key in DB2, Teiid translates it to something incorrect DB2 sql. > However, it works for postgres, mysql, and oracle. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2953) DB2: doesn't work with composite key

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2953?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2953: --------------------------------------- What is the specific version of DB2? We have the translator marked as supporting the array type, which allows for this comparison. > DB2: doesn't work with composite key > ------------------------------------- > > Key: TEIID-2953 > URL: https://issues.jboss.org/browse/TEIID-2953 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Environment: DB2 with Teiid 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > > If I run a sql with composite key in DB2, Teiid translates it to something incorrect DB2 sql. > However, it works for postgres, mysql, and oracle. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2953) DB2: doesn't work with composite key

by Ivan Chan (JIRA)

Ivan Chan created TEIID-2953: -------------------------------- Summary: DB2: doesn't work with composite key Key: TEIID-2953 URL: https://issues.jboss.org/browse/TEIID-2953 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7 Environment: DB2 with Teiid 8.7 Reporter: Ivan Chan Assignee: Steven Hawkins If I run a sql with composite key in DB2, Teiid translates it to something incorrect DB2 sql. However, it works for postgres, mysql, and oracle. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2952) Crypto exception with client/server running on different java versions

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2952?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2952: --------------------------------- Fix Version/s: 7.7.10 > Crypto exception with client/server running on different java versions > ---------------------------------------------------------------------- > > Key: TEIID-2952 > URL: https://issues.jboss.org/browse/TEIID-2952 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Server > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1, 8.8, 7.7.10 > > > The DiffieHellman key generation logic varies by platform with the handling of leading 0's in the secret. 1.6 seems to strip while most 1.7 vms do not. A related Java bug is http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8014618 which indicates Sun/OpenJDK JRE 7u17 - 8b94 are affected. > If there is conflicting handling between the client/server then approximately 1 out of 256 connection attempts will fail with a bad padding exception, since the client/server will be operating against different symmetric keys. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2952) Crypto exception with client/server running on different java versions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2952?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2952: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1096229 > Crypto exception with client/server running on different java versions > ---------------------------------------------------------------------- > > Key: TEIID-2952 > URL: https://issues.jboss.org/browse/TEIID-2952 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Server > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.7.1, 8.8 > > > The DiffieHellman key generation logic varies by platform with the handling of leading 0's in the secret. 1.6 seems to strip while most 1.7 vms do not. A related Java bug is http://bugs.java.com/bugdatabase/view_bug.do?bug_id=8014618 which indicates Sun/OpenJDK JRE 7u17 - 8b94 are affected. > If there is conflicting handling between the client/server then approximately 1 out of 256 connection attempts will fail with a bad padding exception, since the client/server will be operating against different symmetric keys. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2944) getIndexInfo should return statistical information

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2944?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2944. ----------------------------------- Fix Version/s: 8.8 Resolution: Done Updated getIndexInfo to return table cardinalities when approximate info is requested. But we are still setting the non-stat index cardinality to 0 regardless. > getIndexInfo should return statistical information > -------------------------------------------------- > > Key: TEIID-2944 > URL: https://issues.jboss.org/browse/TEIID-2944 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > DatabaseMetaData.getIndexInfo can return statistical indexes with cardinality information and/or cardinality can be returned on the other index info for the table. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2948) Implement Access Controls on management operations in Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2948?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2948. --------------------------------- Resolution: Done Based on instructions, * Translator and Transport have been defined as application based resources * All the sensitive information in the configuration is marked as such. So a person with out in sufficient privileges will not be able to see certain properties * Marked all the operations on Teiid that do modifications to runtime state as such, which will be considered as write sensitive operations and authorized as such Note that RBAC features are by default turned OFF in EAP. However in the case when the user turns these on, Designer and other tooling such as web-console need to use users with sufficient privileges to carry out tasks. Otherwise they will end up with errors. Only 8.7.x branch currently has RBAC as it is supported only in > EAP 6.2, latest master does not contain RBAC feature. > Implement Access Controls on management operations in Teiid > ----------------------------------------------------------- > > Key: TEIID-2948 > URL: https://issues.jboss.org/browse/TEIID-2948 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > EAP 6.2 and above provides facilities to implement access controls on the management operations. Teiid should implement them on the management operations so that they can be controlled by access level of the user. > Unfortunately this is not in EAP 6.1.Alpha, so it becomes hard to pull the changes upstream into 8.8 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2948) Implement Access Controls on management operations in Teiid

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2948?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2948: ------------------------------------- On 5/7/14, 9:21 AM, Ramesh Reddy wrote: > Thanks again, this is very good. The one thing I still do not get it is the following statement > >> The core operation execution logic knows whether the operation step >> handler is trying to address, read, or write. > > I can understand for attributes, and application resources the above can be possible. But the operations are like procedure, apart from addressing, core logic will have no way of knowing a custom operations like "get-translators" in Teiid whether it is performing read/write. I am confused as how to control those as they only need "execute" permission. The control is via the implementation of the OperationContext interface. An OperationStepHandler needs to go through the OperationContext to do most anything. The API of the various OC methods allows us to see if the intent is to read or write. There are readXXX and readXXXForUpdate methods, former are reads, latter are writes. The getServiceTarget(boolean modify) method lets us determine if the intent is to write via the "modify" param. The removeService methods are of course writes. If there is something your handlers do that isn't covered by that, please let me know some details. The OC also has some "authorize" methods, but they were added to cover some use cases in the core, I don't like the API much, and I'd much prefer if subsystems don't use those. The above covers the actual permission enforcement during operation execution. We also want to include information about access control in the response data for read-resource-description and read-operation-description. This information allows clients like the console to tailor their UI. For this we can't use the actual actions of the OSH; we need to rely on the resource/attribute/operation description. For operations, you can provide necessary information via the following methods in SimpleOperationDefinitionBuilder: setReadOnly() -- tells us the op will only read. setRuntimeOnly() -- tells us the op will not deal with the persistent config. This is only relevant for write ops, as we have no roles that can read runtime but not persistent config or vice versa. For an attribute, the API for registering it with the ManagementResourceRegistration tells us whether is is read-only or read-write. The builders for AttributeDefinitions also include a setStorageRuntime() method -- if you use that we know that an attribute is not persisted to the xml config file, so we can let the Operator role modify it. > Implement Access Controls on management operations in Teiid > ----------------------------------------------------------- > > Key: TEIID-2948 > URL: https://issues.jboss.org/browse/TEIID-2948 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1 > > > EAP 6.2 and above provides facilities to implement access controls on the management operations. Teiid should implement them on the management operations so that they can be controlled by access level of the user. > Unfortunately this is not in EAP 6.1.Alpha, so it becomes hard to pull the changes upstream into 8.8 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014