February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-55) Salesforce connector doesn't expose standard connection pooling or caching connector properties

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-55?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-55: ------------------------------ Component/s: Salesforce Connector Fix Version/s: 6.x Affects Version/s: 6.x > Salesforce connector doesn't expose standard connection pooling or caching connector properties > ----------------------------------------------------------------------------------------------- > > Key: TEIID-55 > URL: https://jira.jboss.org/jira/browse/TEIID-55 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 6.x > Environment: SFDC Connector 5.5 GA; MM Designer 5.5.2 0037 Linux > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.x > > > The connector framework provides both caching and pooling support for connectors that implement the required interfaces. The SFDC connector code does indeed implement all of these interfaces. > In order to allow users to fine tune caching or pooling behavior for a connector binding, the connector type's CDK file must also list all of the standard connector framework caching and pooling properties. The SFDC connector does not currently expose these properties. > The SFDC connector's CDK file should be updated to include these properties. Unfortunately we don't document in the connector developer's guide what properties should be defined, but this info can be found in the definition of any of the standard JDBC connector types (Oracle ANSI, etc). These can be marked as "advanced" properties for SFDC as they are for the JDBC connector types. > The max pooled connections per user property is especially important for SFDC, because of the hard limit on 5 concurrent server side cursors per user in SFDC. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-57) Criteria ordering

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-57?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-57: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Criteria ordering > ----------------- > > Key: TEIID-57 > URL: https://jira.jboss.org/jira/browse/TEIID-57 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.x > > > Defect Tracker #24194: The order in which criteria is evaluated in MetaMatrix (and at the source) can have a large impact on performance. We should utilize costing information to order our evaluation of criteria nodes so that the cheapest most limiting criteria is evaluated first. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-54) Fix for NPE when handling LOB returned from a UDF

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-54?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-54: ------------------------------ Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Fix for NPE when handling LOB returned from a UDF > ------------------------------------------------- > > Key: TEIID-54 > URL: https://jira.jboss.org/jira/browse/TEIID-54 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Environment: All server environments. > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > Fix For: 6.0.0 > > > Refer to internal case 185912. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-51) Apache DBCP is not 1.6 compliant

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-51?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-51: ------------------------------ Component/s: Common SOAP Services Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Apache DBCP is not 1.6 compliant > -------------------------------- > > Key: TEIID-51 > URL: https://jira.jboss.org/jira/browse/TEIID-51 > Project: Teiid > Issue Type: Bug > Components: Common, SOAP Services > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > The soap server code now uses JDBC 4.0 specific calls and needs a pool that supports jdk 1.6 -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-52) Change the VM Starter command logic

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-52?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-52: ------------------------------ Component/s: Server Fix Version/s: 6.0.0 Affects Version/s: 6.x > Change the VM Starter command logic > ----------------------------------- > > Key: TEIID-52 > URL: https://jira.jboss.org/jira/browse/TEIID-52 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 6.0.0 > > > In order for the server to better control what JDK/JRE is to be run and make it more flexible for defining java options and java arguments to the VM process, new properties will be added to the host and vm properties. In order to accomplish this, the current vm starter command will be seperated out into 4 properties; java (host), java_opts(vm), java_main (vm) and java_args (vm). > Where: > java - is the executable to run, which will be the full path at installation time > java_opts - will be set at installation time to "-server -Djava-io-tmp...." > java_main - will be the SocketVMController class > java_args - will be: "MMProcess localhost true" -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-48) Better metadata for ODBC and materialization tables

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-48?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-48: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Better metadata for ODBC and materialization tables > --------------------------------------------------- > > Key: TEIID-48 > URL: https://jira.jboss.org/jira/browse/TEIID-48 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.x > > > Materialization model and ODBC tables are currently visible in the metadata tree for all users. This is not desirable, but may be necessary since some clients should have that metadata. > At the very least we should be marking these as system tables. At best we would filter metadata based upon permissions. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-46) Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-46?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-46: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > Fully-qualified names should not be required when referencing virtual procedures that have unique unqualified names > ------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-46 > URL: https://jira.jboss.org/jira/browse/TEIID-46 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Michael Walker > Priority: Minor > Fix For: 6.x > > > This problem occurs in our transformation editor, and also occurs with real-time queries (e.g. from QueryBuilder/SQLExplorer, or any client). > If you reference a non-qualified table name, e.g. "myTable", in a query, we'll attempt to resolve it if it is a unique name. > Strangely, we don't do the same thing for virtual procedures, even if they are unique. Instead, you must use the fully-qualified name. There should be no disparity. This is a usability defect. > This also happens to greatly extend the size of virtual procedure code, making it harder to read and debug. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-45) Unable to run svcmgr, it can't find a hostcontroller

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-45?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-45: ------------------------------ Component/s: Server Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Unable to run svcmgr, it can't find a hostcontroller > ---------------------------------------------------- > > Key: TEIID-45 > URL: https://jira.jboss.org/jira/browse/TEIID-45 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > Unable to run svcmgr to list out the running services. > If this is not going to be a feature of federate, this also needs to be removed from the product. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-43) command deterministic subqueries without from clauses should be merged if possible

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-43?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-43: ------------------------------ Component/s: Query Engine Fix Version/s: 6.x Affects Version/s: 6.x > command deterministic subqueries without from clauses should be merged if possible > ---------------------------------------------------------------------------------- > > Key: TEIID-43 > URL: https://jira.jboss.org/jira/browse/TEIID-43 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.x > > > Defect Tracker #24752: command deterministic subqueries without from clauses should be merged if possible: > i.e. select e1, a from pm1.g1, (select 1 a) x <=> select e1, 1 from pm1.g1 > i.e. select e1, (select 1 a) from pm1.g1 <=> select e1, 1 from pm1.g1 -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-41) Non selectable columns should be omitted from metadata

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-41?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-41: ------------------------------ Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > Non selectable columns should be omitted from metadata > ------------------------------------------------------ > > Key: TEIID-41 > URL: https://jira.jboss.org/jira/browse/TEIID-41 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24612: Non-selectable columns should not be visible in metadata. When visible they will lead to invalid sql getting generated (there was a SQL Explorer defect to that effect, but I can't find it at this time). This is not a regression in 5.5 in 5.5 -- 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

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009