February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-42) Correlated subqueries in XML criteria

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-42?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-42: ------------------------------ Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Correlated subqueries in XML criteria > ------------------------------------- > > Key: TEIID-42 > URL: https://jira.jboss.org/jira/browse/TEIID-42 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 7.x > > > Defect Tracker #24338: Correlated subqueries in xml criteria do not resolve correctly. The xml query resolver should be rewritten to be built upon the SimpleQueryResolver -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-40) ResultSet caching should not default to unlimited

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-40?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-40: ------------------------------ Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > ResultSet caching should not default to unlimited > ------------------------------------------------- > > Key: TEIID-40 > URL: https://jira.jboss.org/jira/browse/TEIID-40 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Fix For: 6.1.0 > > > Defect Tracker #24581: This should be looked at in the context of all the other caching changes. Defaulting to unlimited size/age is very dangerous. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-38) supported non-deterministic functions are evaluated prior to push-down

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-38?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-38: ------------------------------ Component/s: Query Engine Fix Version/s: 6.1.0 Affects Version/s: 6.x > supported non-deterministic functions are evaluated prior to push-down > ---------------------------------------------------------------------- > > Key: TEIID-38 > URL: https://jira.jboss.org/jira/browse/TEIID-38 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #24735: We currently will not actually push down non-deterministic functions even if they are supported, since the evaluateexpressionvisitor will replace them with constant values. For example rand will be pre-evaluated before being sent to sqlserver (however sqlserver does not correctly support non-deterministic functions anyway). We may need to actually not support non-deterministic functions in sqlserver or other sources that do not handle them properly. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-37) Parse function for XSD datatypes for Web service procedures

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-37?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-37: ------------------------------ Component/s: XML Planner/Processor Fix Version/s: 7.x Affects Version/s: 6.x > Parse function for XSD datatypes for Web service procedures > ----------------------------------------------------------- > > Key: TEIID-37 > URL: https://jira.jboss.org/jira/browse/TEIID-37 > Project: Teiid > Issue Type: Bug > Components: XML Planner/Processor > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #22201: for Web Service procedures and other places where xml document values are incoming, a function such as: > parseXSDType(<string: raw value>, <string: xsdtype>) is needed to convert the raw value into the expected runtime type for the given xsdtype. This alleviates the need for embedding potentially problematic formatting strings into the transformations. > See the logic that was already added for the output side of xsd types for defect 20717. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-35) Fix to SizeUtility to support 64-bit VMs correctly

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-35?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-35: ------------------------------ Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Fix to SizeUtility to support 64-bit VMs correctly > -------------------------------------------------- > > Key: TEIID-35 > URL: https://jira.jboss.org/jira/browse/TEIID-35 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Fix For: 6.0.0 > > > Refer to internal case JBEDSP-712. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-36) MMXADataSource needs to notify when it is no longer valid

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-36?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-36: ------------------------------ Component/s: JDBC Driver Fix Version/s: 6.x Affects Version/s: 6.x > MMXADataSource needs to notify when it is no longer valid > --------------------------------------------------------- > > Key: TEIID-36 > URL: https://jira.jboss.org/jira/browse/TEIID-36 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.x > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The MMXADataSource does not properly notify listeners when the connection has become invalid. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-32) Support null values in proc relational joins

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-32?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-32: ------------------------------ Component/s: Query Engine Fix Version/s: 7.x Affects Version/s: 6.x > Support null values in proc relational joins > -------------------------------------------- > > Key: TEIID-32 > URL: https://jira.jboss.org/jira/browse/TEIID-32 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 7.x > > > Defect Tracker #24719: For dependent procedure executions to support null values we need to support criteria of the form: > (value is not null and input = value) or (value is null and input is null) > Currently this will not plan correctly because we do not recognize that the halfs of the conjunct are mutually exclusive and will not require 'or' support if the value is a reference and will have a known value. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-34) Trying to stop hostcontroller, message indicates it could not find a previous instance of hostcontroller to shut down

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-34?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-34: ------------------------------ Component/s: Server Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Trying to stop hostcontroller, message indicates it could not find a previous instance of hostcontroller to shut down > --------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-34 > URL: https://jira.jboss.org/jira/browse/TEIID-34 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 6.0.0 > > > Unable to kill hostcontroller after starting it up. > Jan 27, 2009 09:05:02.278 [main|0] INFO <CONTROLLER|0> startserver -shutdown killHostController resolved config van-halberts-macbook-pro.local > ------------------------------------------------------- > GMS: address is 192.168.1.108:49225 > ------------------------------------------------------- > Did not find previous instance of host controller to shutdown > van-halberts-macbook-pro:bin vanhalbert$ -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-30) Wrong file in the file descriptor field causes weird error

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-30?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-30: ------------------------------ Component/s: Misc. Connectors Fix Version/s: 6.1.0 Affects Version/s: 6.x > Wrong file in the file descriptor field causes weird error > ---------------------------------------------------------- > > Key: TEIID-30 > URL: https://jira.jboss.org/jira/browse/TEIID-30 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.1.0 > > > Defect Tracker #23789: When an non-descriptor file was entered into the text connector file descriptor field, the detail error shown on startup of the connector was: com.metamatrix.common.application.exception.ApplicationLifecycleException[0]: ConnectorException: com.metamatrix.core.MetaMatrixCoreException$StatusHolder@1c93217 > which provides no information as to what went wrong. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-31) For SQL Server source, Operand data type numeric is invalid for modulo operator

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-31?page=com.atlassian.jira.plugi... ] Ramesh Reddy updated TEIID-31: ------------------------------ Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.x > For SQL Server source, Operand data type numeric is invalid for modulo operator > ------------------------------------------------------------------------------- > > Key: TEIID-31 > URL: https://jira.jboss.org/jira/browse/TEIID-31 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 6.x > Reporter: Paul Nittel > Priority: Minor > Fix For: 6.0.0 > > > Defect Tracker #15110: (This was origianally logged under 9792, but that alluded to disabling the MOD operator.) > Using the model project set attached, I built a VDB for testing result set caching. The MOD function is not available to SQL server data sources. Here's the beginning of the stack trace (rest is attached). > com.metamatrix.jdbc.MMSQLException: [MetaMatrix][SQLServer JDBC Driver][SQLServer]Operand data type numeric is invalid for modulo operator. > at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:46) > at com.metamatrix.jdbc.MMSQLException.create(MMSQLException.java:33) > at com.metamatrix.jdbc.MMStatement.setException(MMStatement.java:325) > at com.metamatrix.jdbc.MMStatement.deliverMessage(MMStatement.java:437) > at com.metamatrix.jdbc.MMStatement.access$000(MMStatement.java:54) > at com.metamatrix.jdbc.MMStatement$1.deliverMessage(MMStatement.java:412) > at com.metamatrix.common.comm.platform.socket.SocketClientWorker.deliverMessage(SocketClientWorker.java:38) > at com.metamatrix.common.comm.platform.socket.SocketClientWorker.process(SocketClientWorker.java:34) > at com.metamatrix.common.queue.QueueWorker.processIndirect(QueueWorker.java:95) > at com.metamatrix.common.queue.QueueWorker.run(QueueWorker.java:65) -- 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, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009