July 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-722) Determining the Teiid runtime instace identity could be error prone

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-722?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-722: ------------------------------- Summary: Determining the Teiid runtime instace identity could be error prone (was: Determining the Teiid runtime instace identiry could be error prone) > Determining the Teiid runtime instace identity could be error prone > ------------------------------------------------------------------- > > Key: TEIID-722 > URL: https://jira.jboss.org/jira/browse/TEIID-722 > Project: Teiid > Issue Type: Bug > Components: Embedded, Server > Affects Versions: 6.1.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.2.0 > > > The current way instance id generated for the uniquely identifying the runtime engine could be wrong. Now that "processname" is available in the property, that name should be used as the identifier instead of int identifier now. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-723) Autoincrement incorrectly imported for SQL Server 2008

by Michael RiedmÃ¼ller (JIRA)

Autoincrement incorrectly imported for SQL Server 2008 ------------------------------------------------------ Key: TEIID-723 URL: https://jira.jboss.org/jira/browse/TEIID-723 Project: Teiid Issue Type: Bug Affects Versions: 6.1.0 Environment: Windows XP, Eclipse 3.4.2, SQL Server 2008, JDBC driver by Microsoft Reporter: Michael RiedmÃ¼ller Assignee: Steven Hawkins Table attributes with type int and autoincrement set to true are imported with data type "int identity", autoincrement is NOT set in the properties. This should be data type "int" and autoincrement set to 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-633) Error in Teiid Designer TestServerRuntimeMetadata unit test

by Barry LaFond (JIRA)

Error in Teiid Designer TestServerRuntimeMetadata unit test ----------------------------------------------------------- Key: TEIID-633 URL: https://jira.jboss.org/jira/browse/TEIID-633 Project: Teiid Issue Type: Bug Reporter: Barry LaFond Assignee: Steven Hawkins This ticket is related to TEIIDDES-198. The current Designer indexer performs a toUpperCase() on schema file names. This causes a problem in the TransformationMetadata.getXMLSchemas() method. TEIIDDES-198 is handling the removing the toUpperCase() call. TEIID needs to handle OLD VDB's by modifying RuntimeIndexSelector.getFileContentAsString() method to handle mixed-case schema files so it finds a match. -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Resolved: (TEIID-514) ORDER BY should have ability to include columns not specified in the SELECT clause

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-514?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-514. ---------------------------------- Resolution: Done Updated the docs, added the capability and changed the resolving/planning logic to accept unrelated columns. See TestResolver and TestProcessor. > ORDER BY should have ability to include columns not specified in the SELECT clause > ---------------------------------------------------------------------------------- > > Key: TEIID-514 > URL: https://jira.jboss.org/jira/browse/TEIID-514 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Client request to allow an ORDER BY clause to include columns other than those specified in the SELECT clause, as in the following query: > SELECT col1, col2, col3 > FROM tableA > ORDER BY col4 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-514) ORDER BY should have ability to include columns not specified in the SELECT clause

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-514?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-514: --------------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Complexity: Medium This needs the capability supportOrderByUnrelated (which is the same term used by JDBC). > ORDER BY should have ability to include columns not specified in the SELECT clause > ---------------------------------------------------------------------------------- > > Key: TEIID-514 > URL: https://jira.jboss.org/jira/browse/TEIID-514 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Client request to allow an ORDER BY clause to include columns other than those specified in the SELECT clause, as in the following query: > SELECT col1, col2, col3 > FROM tableA > ORDER BY col4 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIID-251) Support SQL 2003 order by with expressions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ] Steven Hawkins reassigned TEIID-251: ------------------------------------ Assignee: Steven Hawkins > Support SQL 2003 order by with expressions > ------------------------------------------ > > Key: TEIID-251 > URL: https://jira.jboss.org/jira/browse/TEIID-251 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-251) Support SQL 2003 order by with expressions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-251?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-251: --------------------------------- Fix Version/s: 6.2.0 (was: 6.3.0) Given the work on TEIID-514, it would be easier to implement this feature through inline view creation (with the same logic as group by rewriting) with unrelated columns. The designer would still need to have its display node logic updated before this would work there. > Support SQL 2003 order by with expressions > ------------------------------------------ > > Key: TEIID-251 > URL: https://jira.jboss.org/jira/browse/TEIID-251 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Priority: Optional > Fix For: 6.2.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Defect Tracker #25000: SQL 2003 allows the order by clause to contain expressions instead of just simple simple symbol names. Since we already support expressions in the group by clause (which is actually against the SQL spec), it would make since to support expressions in the order by as well. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Work started: (TEIID-514) ORDER BY should have ability to include columns not specified in the SELECT clause

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-514?page=com.atlassian.jira.plug... ] Work on TEIID-514 started by Steven Hawkins. > ORDER BY should have ability to include columns not specified in the SELECT clause > ---------------------------------------------------------------------------------- > > Key: TEIID-514 > URL: https://jira.jboss.org/jira/browse/TEIID-514 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Client request to allow an ORDER BY clause to include columns other than those specified in the SELECT clause, as in the following query: > SELECT col1, col2, col3 > FROM tableA > ORDER BY col4 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-625) ConvertPassword utility doesn't work

by Van Halbert (JIRA)

ConvertPassword utility doesn't work ------------------------------------ Key: TEIID-625 URL: https://jira.jboss.org/jira/browse/TEIID-625 Project: Teiid Issue Type: Bug Components: Common, Tools Affects Versions: 6.1.1 Reporter: Van Halbert Assignee: Steven Hawkins The ConvertPassword does not work and the usage provided at runtime is different than documenation. The 3 option (using -newDefault) is different. Documentation indicates there are 2 additional parms than what the class says. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Updated: (TEIID-409) server port number should be checked for availability when creating a second mmprocess

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-409?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-409: ------------------------------- Fix Version/s: 6.3.0 (was: 6.2.0) Possibly this is no longer applicable, moving 6.3 as multi process mode is handled in that release. > server port number should be checked for availability when creating a second mmprocess > -------------------------------------------------------------------------------------- > > Key: TEIID-409 > URL: https://jira.jboss.org/jira/browse/TEIID-409 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 6.x > Reporter: Marc Shirley > Fix For: 6.3.0 > > > Creating a second process on a server increments the port number by one from the primary process. This port number does not seem to be checked for availability, and so, if the second process's port is already in use, then status of the second process will be unreliable (it flickers between "Running" and "Not Started" states). One or more of the below actions should be taken: > 1) A check should be added to the process of adding a second process to detect whether a port is already in use. > 2) A KI entry should be made to cover the issue. > 3) Steps should be added to the Console User's Guide and/or Server Tuning Guide to advise the reader to make sure the port assigned to the second process is not in use by another application. -- 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, 9 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 July 2009