June 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-404) 1-way and 2-way SSL to MMx must support different keystore file names within a cluster

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-404?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-404: ------------------------------- Fix Version/s: 6.3.0 (was: 6.1.1) > 1-way and 2-way SSL to MMx must support different keystore file names within a cluster > -------------------------------------------------------------------------------------- > > Key: TEIID-404 > URL: https://jira.jboss.org/jira/browse/TEIID-404 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.1.0 > Reporter: Larry O'Leary > Fix For: 6.3.0 > > > Defect Tracker #24283: File naming conventions require a keystore file to be prefixed with the machine's host name. This creates a problem when deploying certificates for use with SSL to a MetaMatrix System as the keystore on each MetaMatrix Server has a different name. Currently, the MMConsole only allows you to set a key store file name that will be used system wide. > We will need the ability to define a key store file name on a per host and possibly a per VM basis. This could be accomplished in many different manners. > The recommended implementation would be to simply move the SSL Resource configuration to the process and host level. This would allow an administrator to continue to use the Console to configure SSL. > At the host level, the administrator could set the default key store file name to be used for all VM(s) deployed to that host. At the VM level, the administrator could set a key store file name value that will override the default host level key store file name property. > This should also be done for the client trust store property to support 2-way SSL. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-405) Allow importing a VDB file from a URL (not just the local file system)

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-405?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-405: ------------------------------- Fix Version/s: 6.3.0 (was: 6.1.1) > Allow importing a VDB file from a URL (not just the local file system) > ---------------------------------------------------------------------- > > Key: TEIID-405 > URL: https://jira.jboss.org/jira/browse/TEIID-405 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Reporter: Randall Hauch > Fix For: 6.3.0 > > > The Console currently has the ability to import a VDB file from the local file system. A great enhancement to this would be the ability to import a VDB from a URL, allowing an administrator to import a VDB file that is located anywhere accessible via a URL (e.g., SVN, DNA, WebDAV, etc.), without requiring the administrator to fetch the file locally first. Of course, fetching it locally is still a valid (and not difficult) workaround. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-162) Delete and update support in temp table

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-162?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-162: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Delete and update support in temp table > --------------------------------------- > > Key: TEIID-162 > URL: https://jira.jboss.org/jira/browse/TEIID-162 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.3.0 > > > Defect Tracker #23925: Delete and update are currently not supported in temp table. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-155) Revisit TransformationMetadataFacade cache sizes

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-155?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-155: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Revisit TransformationMetadataFacade cache sizes > ------------------------------------------------ > > Key: TEIID-155 > URL: https://jira.jboss.org/jira/browse/TEIID-155 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.3.0 > > > Defect Tracker #24593: Cases 5004 and 5835 have shown significant performance issues with resolving. While much of the performance impact was addressed with the 5.5 resolving refactor there is still a large performance hit for resolving that seems largely dependent upon metadata cache. We should investigate additional strategies (for example unified cache or writing more entries per index file read) as a way to increase performance. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-150) Improve nested loop (in merge join) matching

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-150?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-150: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Improve nested loop (in merge join) matching > --------------------------------------------- > > Key: TEIID-150 > URL: https://jira.jboss.org/jira/browse/TEIID-150 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.3.0 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Nested loop evaluation should be based upon available blocks rather than fully iterating the inner side. The simplest approach is to just match a single block from the left and right at a time. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-199) Integration with JBoss Identity project

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-199?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-199: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Integration with JBoss Identity project > --------------------------------------- > > Key: TEIID-199 > URL: https://jira.jboss.org/jira/browse/TEIID-199 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: Steven Hawkins > Fix For: 6.3.0 > > > There is a project underway, JBoss Identity (https://jira.jboss.org/jira/browse/JBID), that aims to provide common identity management support across many JBoss projects/products. According to the project leader's blog (http://anil-identity.blogspot.com/2008/12/federated-identity-support-with...), JBoss Application Server, JBoss Portal, JBoss SOA, JBoss Rules/Drools, and JBoss Seam are all on board with this approach. We should see if it makes sense for us to jump on the bandwagon. > The end goal of using the JBoss Identity stuff would be to replace the custom membership domain provider for authentication, and also to leverage it to provide SAML-based authorization for (ideally fine grained) access to Federate virtual databases. > SAML-based authorization has been a frequent request by prospects/customers for the closed source MetaMatrix product that is an ancestor to Federate. > I'm deliberately logging this one in the Federate project rather than the JBEDSP product JIRA since JBoss Identity itself is also still in project-only status. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-222) Procedural relational execution should support disjunctive criteria

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-222?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-222: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Procedural relational execution should support disjunctive criteria > ------------------------------------------------------------------- > > Key: TEIID-222 > URL: https://jira.jboss.org/jira/browse/TEIID-222 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.3.0 > > > Defect Tracker #24820: Disjunctive criteria should be supported for procedure execution, i.e. select * from proc where input1 = 1 or input2 = 2. Note that for this to work it will to know the possible values for missing parameters in each of the disjuncts, which is covered by defect 24821. Otherwise each disjunct must fully specify all parameters, i.e. (input1 = 1 and input2 = 2) or (input1 = 2 and input2 = 3) -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-160) Remove redundant self-joins

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-160?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-160: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Remove redundant self-joins > --------------------------- > > Key: TEIID-160 > URL: https://jira.jboss.org/jira/browse/TEIID-160 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.3.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Query minimization should be used to remove self-joins on unique columns. This could be added as part of RuleRemoveOptionalJoins (but the rule may need to be run again after join planning). -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-20) Audit logs should roll-over (not just grow)

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-20?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-20: -------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Audit logs should roll-over (not just grow) > ------------------------------------------- > > Key: TEIID-20 > URL: https://jira.jboss.org/jira/browse/TEIID-20 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.1.0 > Reporter: Paul Nittel > Fix For: 6.3.0 > > > Defect Tracker #16477: At present, the audit logs continue to grow until the server is shut down and restarted. At that time, it either creates a new file or appends to the current file. > The audit logs should roll-over in the same manner as the process logs. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-278) Upgrade Axis2 to Axis2 1.4

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-278?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-278: --------------------------------- Fix Version/s: 6.3.0 (was: 6.x) > Upgrade Axis2 to Axis2 1.4 > -------------------------- > > Key: TEIID-278 > URL: https://jira.jboss.org/jira/browse/TEIID-278 > Project: Teiid > Issue Type: Task > Components: Console, XML Connector > Affects Versions: 6.0.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 6.3.0 > > > Need to upgrade from Axis2 1.3 to Axis2 1.4 to take advantage of bug fixes and performance improvements. -- 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

16 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 2009