[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2401:
-----------------------------------
Attachment: generate-dynamic-vdb-page-1.png
> Add support exporting the Designer VDB as Dynamic VDB
> -----------------------------------------------------
>
> Key: TEIIDDES-2401
> URL: https://issues.jboss.org/browse/TEIIDDES-2401
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Reporter: Ramesh Reddy
> Attachments: generate-dynamic-vdb-page-1.png
>
>
> When a VDB is developed in the Designer, provide an option to export the given VDB as Dynamic VDB, which is simple XML format using DDL.
> The server already provides mechanism to retrieve the schema (DDL) for a given model. Using this technique of retrieving the DDL, this feature can be built.
> One caveat is support for XML document models in Dynamic VDB. When VDB contains XML document model, do not support this feature.
> This has couple benefits
> * Users can use these in Teiid for simplified usage.
> * Can used to check the models into source repository like GIT or SVN etc and compare with later versions for modifications
> * Open Shift
> As for importing of Dynamic VDB, that can be handled as separate issue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2555) Provide importing of Swagger service definition file
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2555:
--------------------------------------
Summary: Provide importing of Swagger service definition file
Key: TEIIDDES-2555
URL: https://issues.jboss.org/browse/TEIIDDES-2555
Project: Teiid Designer
Issue Type: Feature Request
Components: Import/Export
Reporter: Ramesh Reddy
http://swagger.io is popular REST service description framework, it defines a specification http://swagger.io/specification/ for REST service definition.
Designer should provide an option to import this file, and create automatic stubs for creation of REST based web services with appropriate input and out put parsing routines and extension metadata properties.
Once the above is provided, the user just needs to fill the transformation to produce the result contents.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2540) Cannot create Data Source on the server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2540?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2540:
-----------------------------------
Fix Version/s: 9.0.2 Beta2
> Cannot create Data Source on the server
> ---------------------------------------
>
> Key: TEIIDDES-2540
> URL: https://issues.jboss.org/browse/TEIIDDES-2540
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 9.0.2 Beta2
> Reporter: Andrej Šmigala
> Assignee: Andrej Šmigala
> Priority: Critical
> Fix For: 9.1, 9.0.2 Beta2, 9.0.2
>
>
> Right clicking Data Sources under the Teiid Instance in Servers view and selecting Create Data Source fails with an empty error message.
> This is caused by a NPE in the code on lines 125 - 133 here: https://github.com/Teiid-Designer/teiid-designer/blob/f28c49b8dafe2a7351e...
> Stacktrace:
> {noformat}
> java.lang.NullPointerException
> at org.teiid.designer.runtime.ui.connection.CreateDataSourceAction.run(CreateDataSourceAction.java:130)
> at org.teiid.designer.runtime.ui.views.TeiidServerActionProvider$7.run(TeiidServerActionProvider.java:359)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (TEIIDDES-2497) Incorrect "Name in Source" when importing from JDBC Database using Informix
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2497?page=com.atlassian.jira.plu... ]
Debbie Steigner commented on TEIIDDES-2497:
-------------------------------------------
Barry,
Not in QE or Eng, but Tom Fonteyne with support maintains one that every can use. I emailed you the request information.
> Incorrect "Name in Source" when importing from JDBC Database using Informix
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2497
> URL: https://issues.jboss.org/browse/TEIIDDES-2497
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0
> Reporter: Bruno Machado
> Assignee: Barry LaFond
> Labels: designer, informix, metadata, teiid
>
> When importing from JDBC Database using a Informix connection, an incorrect "Name in source" metadata is set as "catalog":"schema":"table-name" instead of "catalog":"schema"."table-name", the delimiter between schema and table-name is set to ':' but Informix uses '.'.
> The ':' character must be replaced by a '.' between schema and table name when importing informix tables using Import From JDBC Database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2554) Import of REST service with columns set to 'integer' type results in "Expected biginteger, but was integer."
by Marc Shirley (JIRA)
Marc Shirley created TEIIDDES-2554:
--------------------------------------
Summary: Import of REST service with columns set to 'integer' type results in "Expected biginteger, but was integer."
Key: TEIIDDES-2554
URL: https://issues.jboss.org/browse/TEIIDDES-2554
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.0.1
Reporter: Marc Shirley
Importing posts service from http://jsonplaceholder.typicode.com results in "Expected biginteger, but was integer." runtime error when previewing procedure. This appears to be an issue with the type assignments on the model as a dynamic VDB using the same invocation executes properly. Also seems similar to the issue described in TEIIDDES-2438.
Full error is:
org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30492 TEIID31121 The expected result set of the procedure ViewModel.postById does not match the result set from returnable statement SELECT A.id AS id, A.userId AS userId, A.title AS title, A.body AS body FROM (EXEC SourceModel.invokeHttp(action => 'GET', endpoint => VARIABLES.qp, stream => 'TRUE')) AS f, XMLTABLE('/response' PASSING JSONTOXML('response', f.result) COLUMNS id integer PATH 'id/text()', userId integer PATH 'userId/text()', title string PATH 'title/text()', body string PATH 'body/text()') AS A; use WITHOUT RETURN to indicate the statement should not be returned - The definition for ViewModel.postById has the wrong type for column 1. Expected biginteger, but was integer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2458:
----------------------------------------
Viewing this DB in Squirrel, It appears the tables have NIS that includes a "dbo" schema segment, yet the the DB says the schemaName == NULL.
Thinking that this particular Schema wasn't set up correctly, which may be causing the exception above?
> Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2458
> URL: https://issues.jboss.org/browse/TEIIDDES-2458
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Environment: JBDS: 8.0.2GA
> TD: 9.0.1.Final
> OS: Fedora 20
> java: oracle 1.7
> JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502)
> Sybase DB: ASE 15.0.3/EBF
> Reporter: Juraj Duráni
> Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png
>
>
> I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2458 at 6/5/15 2:21 PM:
----------------------------------------------------------------
Debugging JDBC Importer, there's a call in JdbcCatalogImpl.addSchemaChildren() to get schema children from SybDatabaseMetadata.getSchema() that's throwing an exception:
*java.sql.SQLException: JZ0SB: Parameter index out of range: 1.*
As a result, the schema isn't found and not set on the NIS.
{code}
java.sql.SQLException: JZ0SB: Parameter index out of range: 1.
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.int(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.doSetParam(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.setParam(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.setNull(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getSchemas(Unknown Source)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.addSchemaChildren(JdbcCatalogImpl.java:121)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.computeChildren(JdbcCatalogImpl.java:77)
at org.teiid.designer.jdbc.metadata.impl.JdbcNodeImpl.getChildren(JdbcNodeImpl.java:197)
at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage$TreeContentProvider.hasChildren(JdbcImportObjectsPage.java:1007)
{code}
I it appears to be a driver issue? or maybe the Sybase instance set-up is weird
was (Author: blafond):
Debugging JDBC Importer, there's a call in JdbcCatalogImpl.addSchemaChildren() to get schema children from SybDatabaseMetadata.getSchema() that's throwing an exception:
*java.sql.SQLException: JZ0SB: Parameter index out of range: 1.*
As a result, the schema isn't found and not set on the NIS.
{code}
java.sql.SQLException: JZ0SB: Parameter index out of range: 1.
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.int(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.doSetParam(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.setParam(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.setNull(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getSchemas(Unknown Source)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.addSchemaChildren(JdbcCatalogImpl.java:121)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.computeChildren(JdbcCatalogImpl.java:77)
at org.teiid.designer.jdbc.metadata.impl.JdbcNodeImpl.getChildren(JdbcNodeImpl.java:197)
at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage$TreeContentProvider.hasChildren(JdbcImportObjectsPage.java:1007)
{code}
> Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2458
> URL: https://issues.jboss.org/browse/TEIIDDES-2458
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Environment: JBDS: 8.0.2GA
> TD: 9.0.1.Final
> OS: Fedora 20
> java: oracle 1.7
> JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502)
> Sybase DB: ASE 15.0.3/EBF
> Reporter: Juraj Duráni
> Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png
>
>
> I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month
[JBoss JIRA] (TEIIDDES-2458) Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2458?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2458 at 6/5/15 2:02 PM:
----------------------------------------------------------------
Debugging JDBC Importer, there's a call in JdbcCatalogImpl.addSchemaChildren() to get schema children from SybDatabaseMetadata.getSchema() that's throwing an exception:
*java.sql.SQLException: JZ0SB: Parameter index out of range: 1.*
As a result, the schema isn't found and not set on the NIS.
{code}
java.sql.SQLException: JZ0SB: Parameter index out of range: 1.
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.int(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.doSetParam(Unknown Source)
at com.sybase.jdbc4.jdbc.ParamManager.setParam(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.setNull(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.a(Unknown Source)
at com.sybase.jdbc4.jdbc.SybDatabaseMetaData.getSchemas(Unknown Source)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.addSchemaChildren(JdbcCatalogImpl.java:121)
at org.teiid.designer.jdbc.metadata.impl.JdbcCatalogImpl.computeChildren(JdbcCatalogImpl.java:77)
at org.teiid.designer.jdbc.metadata.impl.JdbcNodeImpl.getChildren(JdbcNodeImpl.java:197)
at org.teiid.designer.jdbc.ui.wizards.JdbcImportObjectsPage$TreeContentProvider.hasChildren(JdbcImportObjectsPage.java:1007)
{code}
was (Author: blafond):
Debugging JDBC Importer, there's a call in JdbcCatalogImpl.addSchemaChildren() to get schema children from SybDatabaseMetadata.getSchema() that's throwing an exception:
*java.sql.SQLException: JZ0SB: Parameter index out of range: 1.*
As a result, the schema isn't found and not set on the NIS.
> Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2458
> URL: https://issues.jboss.org/browse/TEIIDDES-2458
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Environment: JBDS: 8.0.2GA
> TD: 9.0.1.Final
> OS: Fedora 20
> java: oracle 1.7
> JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502)
> Sybase DB: ASE 15.0.3/EBF
> Reporter: Juraj Duráni
> Attachments: parts_sql_catalog_in_name_in_source.png, parts_sql_include_catalog_in_name.png, parts_sql_schema_tree.png, pic1.png, pic2.png, pic3.png, sybase_bqt2_datatools_tree.png
>
>
> I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 1 month