March 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1448) Data roles' Confirm State Change dialog cannot be disabled

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1448?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1448: -------------------------------------- Assignee: Barry LaFond > Data roles' Confirm State Change dialog cannot be disabled > ---------------------------------------------------------- > > Key: TEIIDDES-1448 > URL: https://issues.jboss.org/browse/TEIIDDES-1448 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 7.7.1 > Environment: Windows 7 & JBDS 5 with SOA-tooling CR2 > Reporter: Paul Nittel > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.1 > > Attachments: ConfirmStateChange.png > > > Defining a data role may entail restricting access to an entire model (for example). When the READ option is disabled, the Confirm State Change dialog notifies the user that all children of the selected object will be affected by this change. > There is no way to stop the dialog, so it becomes an obstacle to the user's efforts. It needs one of those "Don't display this any more" checkboxes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1614: ------------------------------------------ Use getResultSetColumns instead. > Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1614 > URL: https://issues.jboss.org/browse/TEIIDDES-1614 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: DynamicSQLMPS.zip > > > Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT * FROM PARTS; > END > Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated. > When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1608) Allow any extension in the XML import wizard

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1608?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1608. --------------------------------------- Resolution: Done > Allow any extension in the XML import wizard > -------------------------------------------- > > Key: TEIIDDES-1608 > URL: https://issues.jboss.org/browse/TEIIDDES-1608 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling, Usability > Affects Versions: 8.0 > Reporter: Daniel Susín > Assignee: Paul Richardson > Fix For: 8.1 > > > The import XML wizard should allow optionally to select any extension besides '.xml'. Limiting it to only '.xml' prevents it from being used, for instance, to process KML files, which are perfectly compatible with the XML parsing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Paul Richardson edited comment on TEIIDDES-1614 at 3/25/13 1:27 PM: -------------------------------------------------------------------- Hi Steve, -[TEIID-2421|https://issues.jboss.org/browse/TEIID-2421]- does not fully solve the problem. The variable 'inferProcedureResultSetColumns' correctly nullifies the resultSetColumns collection and the value 'xml' correctly gets added. However, at no point is the 'xml' value added to the projectedSymbols collection as it was done in 7.7 (see the setProjectedSymbols line from my last comment). Thus, projectedSymbols remains empty. was (Author: phantomjinx): Hi Steve, -[TEIID-2421|https://issues.jboss.org/browse/TEIID-2421]- does not fully solve the problem. The variable 'inferProcedureResultSetColumns' correctly nullifies the resultSetColumns collection and the value 'xml' correctly gets added. However, at no point is the 'xml' value added to the projectedSymbols collection as it was done in 7.7 (see the setProjectedSymbols line from my last comment). Thus, projectSymbols remains empty. > Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1614 > URL: https://issues.jboss.org/browse/TEIIDDES-1614 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: DynamicSQLMPS.zip > > > Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT * FROM PARTS; > END > Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated. > When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1614: ------------------------------------------- Hi Steve, -[TEIID-2421|https://issues.jboss.org/browse/TEIID-2421]- does not fully solve the problem. The variable 'inferProcedureResultSetColumns' correctly nullifies the resultSetColumns collection and the value 'xml' correctly gets added. However, at no point is the 'xml' value added to the projectedSymbols collection as it was done in 7.7 (see the setProjectedSymbols line from my last comment). Thus, projectSymbols remains empty. > Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1614 > URL: https://issues.jboss.org/browse/TEIIDDES-1614 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: DynamicSQLMPS.zip > > > Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT * FROM PARTS; > END > Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated. > When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1614: ------------------------------------------ For Teiid 8.3 see TEIID-2421 > Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1614 > URL: https://issues.jboss.org/browse/TEIIDDES-1614 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: DynamicSQLMPS.zip > > > Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT * FROM PARTS; > END > Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated. > When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1614) Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1614?page=com.atlassian.jira.plu... ] Paul Richardson commented on TEIIDDES-1614: ------------------------------------------- The 8.2/8.3 implementation still fails to resolve the project symbols. Using the parts project, the following error is generated from the SQL. "The SELECT transformation is valid, but NOT fully reconciled: The number of transformation output symbols is zero." {code:SQL} CREATE VIRTUAL PROCEDURE BEGIN DECLARE string VARIABLES.IN_exampleVar; VARIABLES.IN_exampleVar = xPathValue(null, '//*[local-name()="exampleName"]'); SELECT * FROM PartsXMLViewOutput_View.PartsXMLViewTable_OutputView; END {code} The reason for the error is removal of code between the 7.7 and 8.2 teiid code streams. When a project is loaded containing a virtual procedure, it is validated and resolved by the transformation validator. In 8.2, resolution of the CreateProcedureCommand passes through TransformationMetadata.getStoredProcInfoDirect(). The output symbols are determined by this method using the ColumnSetRecordImpl.getColumnsIDs(). Now when the validator first validates the project on import, this returns empty However, when the webservice model is opened it calls: OperationObjectEditorPage.setEditorContent -> TransformationMappingHelper.reconcileTargetAttributes The reconciling of attributes determines 2 variables: * currentTargetAttrNames * projectedSymbolNames Both are empty in 8.2 so nothing more occurs. However, in 7.7 projectSymbolsNames contains "xml" and as a consequence the TransformationMappingHelper calls addTargetAttributes() correcting the validity error. So why doesn't 8.2 do the same? The reason: Teiid's CreateUpdateProcedureCommand and CreateProcedureCommand have changed in that: {code} public List getProjectedSymbols(){ if(this.projectedSymbols != null){ return this.projectedSymbols; } - if(!isUpdateProcedure){ - if(this.resultsCommand == null){ - //user may have not entered any query yet - return Collections.EMPTY_LIST; - } - List<? extends SingleElementSymbol> symbols = this.resultsCommand.getProjectedSymbols(); - if (this.resultsCommand instanceof StoredProcedure) { - StoredProcedure sp = (StoredProcedure)this.resultsCommand; - if (sp.isCallableStatement()) { - symbols = sp.getResultSetColumns(); - } - } - setProjectedSymbols(symbols); - return this.projectedSymbols; - } - this.projectedSymbols = Command.getUpdateCommandSymbol(); - return this.projectedSymbols; + //user may have not entered any query yet + return Collections.EMPTY_LIST; } {code} The removed code extracts the projected symbols from the embedded resultsCommand (a Query and is the same between 7.7 and 8.2). This is responsible for creating the crucial xml elementSymbol. To resolve the problem: * Understand why these classes were modified in Teiid and address appropriately * Should the removed code be added to the postResolveCommand method of the resolver for 8.2? > Procedure result set not being generated when creating simple CREATE VIRTUAL PROCEDURE from SQL > ----------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1614 > URL: https://issues.jboss.org/browse/TEIIDDES-1614 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > Attachments: DynamicSQLMPS.zip > > > Designer 7.7.x will auto-generated the virtual procedure result set and columns after pasting in the following: > CREATE VIRTUAL PROCEDURE > BEGIN > SELECT * FROM PARTS; > END > Current Designer 8.1 codebase results in valid SQL (no errors) but the result set and columns are not generated. > When creating a Web Service Model/Operation from same PARTS source table the resulting Operation will have a resulting OUTPUT (result set) but no output column with XML type -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1606) File XML importer does not recognise the default XMLNAMESPACE

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1606?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1606. ------------------------------------ Resolution: Done Done https://github.com/Teiid-Designer/teiid-designer/commit/36f7aa020d3c90dc1... > File XML importer does not recognise the default XMLNAMESPACE > ------------------------------------------------------------- > > Key: TEIIDDES-1606 > URL: https://issues.jboss.org/browse/TEIIDDES-1606 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: linea_bus.xml > > > When a XML file with default NAMESPACE is being imported, the XMl import wizard created the name space SQL as > {code} > XMLTABLE(XMLNAMESPACES('http://www.opengis.net/kml/2.2' AS, 'http://www.w3.org/2005/Atom' AS atom, > {code} > see the missing name after AS and before comma, it should be written as > {code} > XMLTABLE(XMLNAMESPACES(DEFAULT 'http://www.opengis.net/kml/2.2', 'http://www.w3.org/2005/Atom' AS atom, > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1606) File XML importer does not recognise the default XMLNAMESPACE

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1606?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1606: ----------------------------------- Fix Version/s: 8.1 > File XML importer does not recognise the default XMLNAMESPACE > ------------------------------------------------------------- > > Key: TEIIDDES-1606 > URL: https://issues.jboss.org/browse/TEIIDDES-1606 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: linea_bus.xml > > > When a XML file with default NAMESPACE is being imported, the XMl import wizard created the name space SQL as > {code} > XMLTABLE(XMLNAMESPACES('http://www.opengis.net/kml/2.2' AS, 'http://www.w3.org/2005/Atom' AS atom, > {code} > see the missing name after AS and before comma, it should be written as > {code} > XMLTABLE(XMLNAMESPACES(DEFAULT 'http://www.opengis.net/kml/2.2', 'http://www.w3.org/2005/Atom' AS atom, > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1606) File XML importer does not recognise the default XMLNAMESPACE

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1606?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-1606: -------------------------------------- Assignee: Barry LaFond > File XML importer does not recognise the default XMLNAMESPACE > ------------------------------------------------------------- > > Key: TEIIDDES-1606 > URL: https://issues.jboss.org/browse/TEIIDDES-1606 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.0 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Attachments: linea_bus.xml > > > When a XML file with default NAMESPACE is being imported, the XMl import wizard created the name space SQL as > {code} > XMLTABLE(XMLNAMESPACES('http://www.opengis.net/kml/2.2' AS, 'http://www.w3.org/2005/Atom' AS atom, > {code} > see the missing name after AS and before comma, it should be written as > {code} > XMLTABLE(XMLNAMESPACES(DEFAULT 'http://www.opengis.net/kml/2.2', 'http://www.w3.org/2005/Atom' AS atom, > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2013