February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1605) Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1605: ---------------------------------------- Pulled latest code today. 1) Previewed with 8.x TEiid just fine 2) Stopped AS 7.1 server 3) Started AS 5.1 server (TEiid 7.7.x) 4) Set Default Server to AS 5.1 instance 5) Tried to preview, but got the <import-vdb> parsing error because previous PROJECT PREVIEW VDB was still deployed 6) Deleted the PROJECT PVDB and re-executed Preview Data and it deployed correct project PVDB and was successful returning data > Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-1605 > URL: https://issues.jboss.org/browse/TEIIDDES-1605 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace)..... > * Opened Project > * Tried to Preview a table and got an NPE: > ** java.lang.NullPointerException > at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642) > at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > The method failing is: > private String getFullDeployedVdbName(ITeiidVdb deployedVdb) { > String fullVdbName = deployedVdb.getPropertyValue("deployment-name");; > if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) { > fullVdbName = fullVdbName + Vdb.FILE_EXTENSION; > } > return fullVdbName; > > } > ITeiidVdb is a new SPI interface. > So was the "deployment-name" property available with Teiid 7.7.x runtime? > Also can't Undeploy VDB on 7.7.2 server -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1605) Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1605: ----------------------------------- Summary: Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server (was: Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server) > Issues with previewing data after switch from 7.7.x Teiid to 8.2.x Teiid default server > --------------------------------------------------------------------------------------- > > Key: TEIIDDES-1605 > URL: https://issues.jboss.org/browse/TEIIDDES-1605 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, VDB & Execution > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Paul Richardson > Fix For: 8.1 > > > After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace)..... > * Opened Project > * Tried to Preview a table and got an NPE: > ** java.lang.NullPointerException > at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642) > at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373) > at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) > The method failing is: > private String getFullDeployedVdbName(ITeiidVdb deployedVdb) { > String fullVdbName = deployedVdb.getPropertyValue("deployment-name");; > if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) { > fullVdbName = fullVdbName + Vdb.FILE_EXTENSION; > } > return fullVdbName; > > } > ITeiidVdb is a new SPI interface. > So was the "deployment-name" property available with Teiid 7.7.x runtime? > Also can't Undeploy VDB on 7.7.2 server -- 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

12 years

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1606?page=com.atlassian.jira.plu... ] Ramesh Reddy updated TEIIDDES-1606: ----------------------------------- Attachment: linea_bus.xml sample xml file > 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 > 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

12 years

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-1606: -------------------------------------- Summary: 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 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1531) Exception when updating Oracle NVARCHAR2 columns

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1531: ---------------------------------------- Mark, it may be a simple as updating our Oracle JDBC import processor class to do the d-type mapping. > Exception when updating Oracle NVARCHAR2 columns > ------------------------------------------------ > > Key: TEIIDDES-1531 > URL: https://issues.jboss.org/browse/TEIIDDES-1531 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0 > Reporter: I Leitch > Assignee: Mark Drilling > Fix For: 8.1 > > > If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111) and VARCHAR2 (type 12) as string. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1531) Exception when updating Oracle NVARCHAR2 columns

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1531: ----------------------------------- Fix Version/s: 8.1 > Exception when updating Oracle NVARCHAR2 columns > ------------------------------------------------ > > Key: TEIIDDES-1531 > URL: https://issues.jboss.org/browse/TEIIDDES-1531 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0 > Reporter: I Leitch > Fix For: 8.1 > > > If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111) and VARCHAR2 (type 12) as string. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1531) Exception when updating Oracle NVARCHAR2 columns

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1531: ----------------------------------- Assignee: Mark Drilling > Exception when updating Oracle NVARCHAR2 columns > ------------------------------------------------ > > Key: TEIIDDES-1531 > URL: https://issues.jboss.org/browse/TEIIDDES-1531 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0 > Reporter: I Leitch > Assignee: Mark Drilling > Fix For: 8.1 > > > If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111) and VARCHAR2 (type 12) as string. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1531) Exception when updating Oracle NVARCHAR2 columns

by Srini Kethireddipalli (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1531?page=com.atlassian.jira.plu... ] Srini Kethireddipalli commented on TEIIDDES-1531: ------------------------------------------------- The comment says Oracle translator should handle this as String. Is this confirmed to be an issue? If so, when is it likely to be fixed? > Exception when updating Oracle NVARCHAR2 columns > ------------------------------------------------ > > Key: TEIIDDES-1531 > URL: https://issues.jboss.org/browse/TEIIDDES-1531 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration > Environment: Windows 7 64 bit, Eclipse Indigo, Oracle jdbc thin 11.2.0.2.0 > Reporter: I Leitch > > If it doesn't already do so, the Oracle importer should import NVARCHAR2 (type 1111) and VARCHAR2 (type 12) as string. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1560) Add Support for Query Parameters in Generated REST War

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1560?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1560. --------------------------------- Release Notes Docs Status: Documented as Feature Request Release Notes Text: The generated REST WAR now support query parameters in addition to URI parameters and XML/JSON inputs. Query parameters can be specified in the target REST procedure's URI property using "&" as a delimiter. For example: REST:URI = authors&parm1&parm2. Resolution: Done The generated REST WAR now support query parameters in addition to URI parameters and XML/JSON inputs. Query parameters can be specified in the target REST procedure's URI property using "&" as a delimiter. For example: REST:URI = authors&parm1&parm2. > Add Support for Query Parameters in Generated REST War > ------------------------------------------------------ > > Key: TEIIDDES-1560 > URL: https://issues.jboss.org/browse/TEIIDDES-1560 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.8, 8.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.1 > > > The generated REST war supports path parameters and XML/JSON inputs, but does not allow for query parameters. We should support query parameters as well. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1560) Add Support for Query Parameters in Generated REST War

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1560?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1560: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/114 > Add Support for Query Parameters in Generated REST War > ------------------------------------------------------ > > Key: TEIIDDES-1560 > URL: https://issues.jboss.org/browse/TEIIDDES-1560 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.8, 8.0 > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.1 > > > The generated REST war supports path parameters and XML/JSON inputs, but does not allow for query parameters. We should support query parameters as well. -- 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

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2013