January 2010 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-235) Order of operations problem in Designer

by Mark Drilling (JIRA)

Order of operations problem in Designer --------------------------------------- Key: TEIIDDES-235 URL: https://jira.jboss.org/jira/browse/TEIIDDES-235 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 6.0.0 Reporter: Mark Drilling The following query when entered into the transformation editor: select * from dips_view.cards LEFT OUTER JOIN CramerXRefData.CardTypes ON card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE IS NULL OR card = CardTypes.DIPS_CardType AND CramerXRefData.CardTypes.DIPS_ELEMTYPE = device_pk is parsed as; SELECT * FROM DIPS_View.Cards LEFT OUTER JOIN CramerXRefData.CardTypes ON ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE IS NULL)) OR ((CARD = DIPS_CARDTYPE) AND (DIPS_ELEMTYPE = Device_PK)) The ordering of different variations of CompoundCriteria are not preserved correctly. -- 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

13 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-168) Designer fails to delete project.

by John Doyle (JIRA)

Designer fails to delete project. --------------------------------- Key: TEIIDDES-168 URL: https://jira.jboss.org/jira/browse/TEIIDDES-168 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0 Environment: Designer 4-27 snapshot build on Fedora 10. Reporter: John Doyle I have two projects that models of the same name. When I try to delete the project in the Model Explorer, I am prompted that I am trying to delete a model when a model in another project depends upon it. As far as I can tell this is not true, and I'm surmising it's getting confused by the name. In any event, when I tell the designer to delete anyway, the delete does not happen. -- 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

13 years, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-240) SFDC importer corrupts model during re-import, removing 'supports query' annotations on tables

by John Doyle (JIRA)

SFDC importer corrupts model during re-import, removing 'supports query' annotations on tables ---------------------------------------------------------------------------------------------- Key: TEIIDDES-240 URL: https://jira.jboss.org/jira/browse/TEIIDDES-240 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0, 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Paul Nittel (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-256?page=com.atlassian.jira.p... ] Paul Nittel commented on TEIIDDES-256: -------------------------------------- Steve, the VDB was created using the latest Designer. (It's not an old one.) BTW, the definition of Q13 is: SELECT c_count, COUNT(*) AS custdist FROM (SELECT TPCR.CUSTOMER.C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON TPCR.CUSTOMER.C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY TPCR.CUSTOMER.C_CUSTKEY) AS c_orders GROUP BY c_count > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 6.2.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-256?page=com.atlassian.jira.p... ] Steven Hawkins moved TEIID-935 to TEIIDDES-256: ----------------------------------------------- Project: Teiid Designer (was: Teiid) Key: TEIIDDES-256 (was: TEIID-935) Component/s: Transformations (was: Query Engine) Affects Version/s: 7.0 (was: 7.0) > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 7.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-256?page=com.atlassian.jira.p... ] Steven Hawkins updated TEIIDDES-256: ------------------------------------ Affects Version/s: 6.2.0 (was: 7.0) > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 6.2.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Assignee: Steven Hawkins > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-256) Teiid is making column names upper case, even when specified as lower

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-256?page=com.atlassian.jira.p... ] Steven Hawkins updated TEIIDDES-256: ------------------------------------ Assignee: (was: Steven Hawkins) > Teiid is making column names upper case, even when specified as lower > --------------------------------------------------------------------- > > Key: TEIIDDES-256 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-256 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 6.2.0 > Environment: Fedora 12, OpenJDK Server VM (build 14.0-b16, mixed mode), Teiid build 1/19/2010 > Reporter: Paul Nittel > Attachments: TextMetadataTesting.zip > > > I've got a transformation that defines two columns like this: > SELECT > c_count, COUNT(*) AS custdist > FROM > (SELECT C_CUSTKEY, COUNT(O_ORDERKEY) AS c_count FROM TPCR.CUSTOMER LEFT OUTER JOIN TPCR.ORDERS ON C_CUSTKEY = O_CUSTKEY AND O_COMMENT NOT LIKE '%special%requests%' GROUP BY C_CUSTKEY) AS c_orders > GROUP BY c_count > In the past, when queried (SELECT * FROM ...), the columns were spelled c_count and custdist. Now they're spelled C_COUNT and custdist. Do we now upcase column names that are not specified as an alias (or do we only preserve case on aliases)? > I noticed this in AdminShell, but see the Designer is also doing it, so I'm thinking it's the query engine, not the tool. (Steve H. agreed it should still be lower case when queried.) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-102) Using clear transformation button causes refresh/repaint issues in transformation diagram

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-102?page=com.atlassian.jira.p... ] Barry LaFond resolved TEIIDDES-102. ----------------------------------- Resolution: Done Tested with Teiid Designer 6.3. No refresh issues. Marking as Not reproducable > Using clear transformation button causes refresh/repaint issues in transformation diagram > ----------------------------------------------------------------------------------------- > > Key: TEIIDDES-102 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-102 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: Future > > > After using the clear transformation button, all changes require the refresh button to be manually pressed to update the transformation diagram. This affects all models/diagrams, not just the model whose transformation was cleared. > Tested during E2eYahooUdfTestScript.odt by clearing transformation of MyPortfolio.Positions and then pasting new transformation into editor. Renaming the column directly in the diagram did not cause a refresh. Tried to create a new model with a new base table, and the changes would not update correctly there either. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-89) Designer hangs when executing a Web Service Operation

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-89?page=com.atlassian.jira.pl... ] Barry LaFond resolved TEIIDDES-89. ---------------------------------- Resolution: Cannot Reproduce Bug No problems in Designer 6.3 Marking as not reproducable > Designer hangs when executing a Web Service Operation > ----------------------------------------------------- > > Key: TEIIDDES-89 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-89 > Project: Teiid Designer > Issue Type: Task > Components: VDB & Execution > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: Future > > Attachments: PartsProjectWebSvc.zip > > > Using the attached Model Project Set, I executed the Web service and used S101 and P304 as the Supplier and Part ids. When executed, it appears to hang and required the use of the System Monitor to kill it. > I _was_ able to successfully query the underlying virtual table and the XML document. And it works when deployed on a server. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-244) Text Connector does not show up after creation

by Mark Drilling (JIRA)

Text Connector does not show up after creation ---------------------------------------------- Key: TEIIDDES-244 URL: https://jira.jboss.org/jira/browse/TEIIDDES-244 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.2.0 Reporter: Mark Drilling Assignee: Barry LaFond In 6.2 Teiid Designer, create a new Text Connector in ConnectorsView. The Connector does not display anywhere. If I try to create another text connector with the same name, the wizard says a connector with that name already exists. In the VDB editor, the Text Connector does not show up as one of the available connectors. -- 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, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2010