September 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1251) Fully qualified order by key can resolve incorrectly

by Steven Hawkins (JIRA)

Fully qualified order by key can resolve incorrectly ---------------------------------------------------- Key: TEIID-1251 URL: https://jira.jboss.org/browse/TEIID-1251 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 A query such as: SELECT pm1.g1.e1 e2 FROM pm1.g1 group by pm1.g1.e1 ORDER BY pm1.g1.e2 Will resolve incorrectly to reference e2 rather than throwing an exception. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1246) Determine access strategy for SYS/pg_catalog

by Steven Hawkins (JIRA)

Determine access strategy for SYS/pg_catalog -------------------------------------------- Key: TEIID-1246 URL: https://jira.jboss.org/browse/TEIID-1246 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.1 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.1.1 The SYS and pg_catalog schema mainly exist for metadata reporting. It would probably be good to make the always be accessable. The only issue is what the access policy should be for the system procedures: GETCHARACTERVDBRESOURCE GETBINARYVDBRESOURCE GETVDBRESOURCEPATHS GETXMLSCHEMAS refreshMatVeiw refreshMatVeiwRow The first three are probably no longer useful as general procedures. I'm not familiar with any customer usage. Unless someone adds custom files to a VDB, the only thing that could be retrieved are the visible model xmis and schemas. The fourth procedure is really just a helper method to get at schemas associated with a particular document model. These resources would already be accessible via getXXXVDBResource. Again I'm not aware of customer usage for this procedure. Since they are read-only and restricted to only visible entries we could just as easily always allow access to the GET procedures, or we could just as easily remove them all since they aren't particularly useful. That leaves us with the refresh procedures. Theses do perform update actions and should be restricted. One possibility is to restrict their usage based upon the permissions of the target view. The other option is to move them into a sub schema e.g. SYS.admin.refreshMatView that would be subject to access restrictions, and can be more easily targeted by explicit roles. If we went the role route, then the tooling could have a button to "create admin role" that would create a role named admin with all permissions including permissions against SYS.admin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIID-1264) Make "build" project manage all the responsibility of the assemblies

by Ramesh Reddy (JIRA)

Make "build" project manage all the responsibility of the assemblies -------------------------------------------------------------------- Key: TEIID-1264 URL: https://jira.jboss.org/browse/TEIID-1264 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Affects Versions: 7.1 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1.1 Use the new assembly plugin and move the assembly building into build project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1198) Allow specifying the VDB version as part of the VDB name in the JDBC URL connection string.

by Ramesh Reddy (JIRA)

Allow specifying the VDB version as part of the VDB name in the JDBC URL connection string. ------------------------------------------------------------------------------------------- Key: TEIID-1198 URL: https://jira.jboss.org/browse/TEIID-1198 Project: Teiid Issue Type: Sub-task Components: JDBC Driver Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.1 Currently when a user connects to a VDB of particular version they use the format jdbc:teiid:<vdb>@mm://host:port;version=?;user=.. additionally support jdbc:teiid:<vdb.version>@mm://host:port;user=.. in which case both the above URL are same. This format is required by the ODBC client. As in ODBC the "Connection Settings" are called after the connection is made. The version information is required at the time of the connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1199) Use consistent names for security concepts

by Steve Hawkins (JIRA)

Use consistent names for security concepts ------------------------------------------ Key: TEIID-1199 URL: https://jira.jboss.org/browse/TEIID-1199 Project: Teiid Issue Type: Quality Risk Components: Common Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 The documentation and config should not use entitlements. Also the vdb.xsd should use data-role instead of data-policy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1133) Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url.

by Ramesh Reddy (JIRA)

Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url. --------------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1133 URL: https://jira.jboss.org/browse/TEIID-1133 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.0 When SF query executed in the error message shows up in the in the log file. The query still works fine. Error creating SSL Socket Factory for client invoker: Error initializing socket factory SSL context: Can not find truststore url. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1187) Refine vdb version logic

by Steve Hawkins (JIRA)

Refine vdb version logic ------------------------ Key: TEIID-1187 URL: https://jira.jboss.org/browse/TEIID-1187 Project: Teiid Issue Type: Quality Risk Components: Server Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1 We no longer have a built in configuration repository and we rely on container scans to do deploys, so we have lost the ability to internally control the notion of a deployed vdb version. We should strive for the following: 1. Overwrite of a deployed vdb should not invalidate or otherwise corrupt current connections. 2. Switching to a different vdb as the new default for a particular name should not require two deployments of the same vdb. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1055) Secure profile service access

by Ramesh Reddy (JIRA)

Secure profile service access ----------------------------- Key: TEIID-1055 URL: https://jira.jboss.org/jira/browse/TEIID-1055 Project: Teiid Issue Type: Task Components: AdminApi Affects Versions: 7.0 Reporter: Ramesh Reddy Fix For: 7.0 As of 7.0 M3 release, the "Profile Service" access is not secure. Currently the JOPR plug-in and Teiid Admin API, force users to authenticate with "jmx-console" security domain, both these do not prevent the direct access to the "Profile Service" EJB directly. Profile Service can be deployed as secure EJB, such that it would require a login context to be authenticated before user has access to this bean. This needs to be configured and tested. Also document, how to configure the profile service as secure service. Also, AdminFactory class, which provides Admin connections, need to work with secure "Profile Service". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
8
0 / 0

[JBoss JIRA] Created: (TEIID-1213) Procedure results should be cachable as well

by Steve Hawkins (JIRA)

Procedure results should be cachable as well -------------------------------------------- Key: TEIID-1213 URL: https://jira.jboss.org/browse/TEIID-1213 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.1 Reporter: Steve Hawkins Assignee: Steve Hawkins Fix For: 7.1.1 Virtual procedure invocations should be cached in a mechanism similar to materialized views. This is to fully replace the MetaMatrix functionality of source query caching. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1221) Query Processing Uncorrelated subquery evaluation - Not saving state causing re-execution without closing prior connection

by Warren Gibson (JIRA)

Query Processing Uncorrelated subquery evaluation - Not saving state causing re-execution without closing prior connection -------------------------------------------------------------------------------------------------------------------------- Key: TEIID-1221 URL: https://jira.jboss.org/browse/TEIID-1221 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.1 Environment: Teiid 7.1 Final; PostgreSQL83 DB Reporter: Warren Gibson Assignee: Steve Hawkins Query Testing - The following query is causing an issue which stops further processing. SELECT stringkey, (SELECT intkey from BQT1.SmallA as b where Intnum = 22) FROM BQT1.SmallA order by stringkey. Steve H stated this is related to uncorrelated subquery evaluation - Not saving state from one execution to the next which is causing a re-execute without closing the prior connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2010