[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2248:
---------------------------------------------------
Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1120073|https://bugzilla.redhat.com/show_bug.cgi?id=1120073] from MODIFIED to VERIFIED
> Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2248
> URL: https://issues.jboss.org/browse/TEIIDDES-2248
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.3
> Environment: Teiid Designer 8.3.3
> Teiid 8.4.1-redhat-7
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.0.3, 9.2
>
> Attachments: screen-1.png
>
>
> Create a table with
> {code:sql}
> CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' )
> {code}
> When trying to import it through Teiid Connection Importer, the importer DDL is shown as
> {code:sql}
> CREATE FOREIGN TABLE "dballo00.dbo.t1" (
> c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar')
> ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0);
> {code}
> but on the next page, the following error is shown (see screenshot):
> The DDL failed to parse with message: "Unparsable table body".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2248.
------------------------------------
> Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2248
> URL: https://issues.jboss.org/browse/TEIIDDES-2248
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.3
> Environment: Teiid Designer 8.3.3
> Teiid 8.4.1-redhat-7
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.0.3, 9.2
>
> Attachments: screen-1.png
>
>
> Create a table with
> {code:sql}
> CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' )
> {code}
> When trying to import it through Teiid Connection Importer, the importer DDL is shown as
> {code:sql}
> CREATE FOREIGN TABLE "dballo00.dbo.t1" (
> c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar')
> ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0);
> {code}
> but on the next page, the following error is shown (see screenshot):
> The DDL failed to parse with message: "Unparsable table body".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2399) Creating view model from source model with generate transformations results in orphaned annotated object reference to source
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2399?page=com.atlassian.jira.plu... ]
Andrej Šmigala reopened TEIIDDES-2399:
--------------------------------------
The Copy all descriptors checkbox is now not shown when right-clicking an existing source model and selecting New -> Teiid Metadata Model. A view model created this way does not contain the orphaned annotated object reference.
However, when opening the New Model Wizard any other way (such as File -> New -> Teiid Metadata Model or by right clicking the model project), the checkbox is still shown and the created model does contain the annotated object reference.
> Creating view model from source model with generate transformations results in orphaned annotated object reference to source
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2399
> URL: https://issues.jboss.org/browse/TEIIDDES-2399
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.6
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 9.0.3, 9.2
>
>
> Create a View model from a source model and choose the "Transform.." option to generate default transformations.
> The resulting View model will contain an extra <annotatedObject> reference in the same <annotations> element as the *relational* extension model reference
> {code:xml}
> <mmcore:AnnotationContainer xmi:uuid="mmuuid:9c7ac03c-bafc-4aa1-855f-4e6a43dd9c21">
> <annotations xmi:uuid="mmuuid:7aeb8904-fe0c-42ac-ae67-72c8ce5b397d">
> <tags xmi:uuid="mmuuid:873b6c71-41d4-476a-bf9a-442cb7fd7943" key="modelExtensionDefinition:relational" value="relational"/>
> <annotatedObject href="XXXXXXX.xmi#mmuuid/7291fb4c-da39-4bbc-9787-d2edd9b9551c"/>
> </annotations>
> {code}
> This won't cause problems for the View model, however if the View model is copied to yet another view model, the Model Import for the original source model will end up in the top level view model due to the orphaned "href=....."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2406) Provide option to set JNDI, instead of Connection Profile, in order to do data preview
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2406.
------------------------------------
> Provide option to set JNDI, instead of Connection Profile, in order to do data preview
> --------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2406
> URL: https://issues.jboss.org/browse/TEIIDDES-2406
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview
> Affects Versions: 8.6
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.1, 9.0.3
>
> Attachments: set-jndi-name-action.png, set-jndi-name-dialog.png
>
>
> In a collaborative environment, the data sources could already be setup on the server. So in Designer, when doing data preview, it would user friendly to be able to set the JNDI reference to use, instead of having to create a connection profile. And that would eliminate the need to create a new data source in order to preview.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2422.
------------------------------------
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 8.6.2 Beta1, 9.0.3, 9.2, 8.6.2
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2422:
---------------------------------------------------
Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1104572|https://bugzilla.redhat.com/show_bug.cgi?id=1104572] from MODIFIED to VERIFIED
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 8.6.2 Beta1, 9.0.3, 9.2, 8.6.2
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2447.
------------------------------------
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.0.3
>
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2471) Assertion error trying to Delete a file
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2471?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2471:
---------------------------------------------------
Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1208027|https://bugzilla.redhat.com/show_bug.cgi?id=1208027] from NEW to VERIFIED
> Assertion error trying to Delete a file
> ---------------------------------------
>
> Key: TEIIDDES-2471
> URL: https://issues.jboss.org/browse/TEIIDDES-2471
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 9.0
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.0.3, 9.2
>
>
> When deleting a VDB in a model project, it'll fail if you click *Preview*, then *Back*, then *OK*
> Stack trace is below and it appears that by Previewing the a refactor action (Delete in this case) and clicking *Back* does not clear the original *change*, so clicking *OK* ends up trying to apply duplicate changes. I tested the Preview/Back a couple of times and verified it's adding a duplicate change each time.
> {code}
> org.eclipse.core.runtime.CoreException: assertion failed: DeleteResourcesRefactoring class is adding a
> at org.teiid.designer.ui.refactor.delete.DeleteResourcesRefactoring.createChange(DeleteResourcesRefactoring.java:232)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> !SUBENTRY 1 org.teiid.designer.ui.refactor.delete 4 0 2015-04-06 08:26:20.007
> !MESSAGE assertion failed:
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (TEIIDDES-2471) Assertion error trying to Delete a file
by Andrej Šmigala (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2471?page=com.atlassian.jira.plu... ]
Andrej Šmigala closed TEIIDDES-2471.
------------------------------------
> Assertion error trying to Delete a file
> ---------------------------------------
>
> Key: TEIIDDES-2471
> URL: https://issues.jboss.org/browse/TEIIDDES-2471
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 9.0
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-8.0.3.CR1
> Fix For: 9.0.3, 9.2
>
>
> When deleting a VDB in a model project, it'll fail if you click *Preview*, then *Back*, then *OK*
> Stack trace is below and it appears that by Previewing the a refactor action (Delete in this case) and clicking *Back* does not clear the original *change*, so clicking *OK* ends up trying to apply duplicate changes. I tested the Preview/Back a couple of times and verified it's adding a duplicate change each time.
> {code}
> org.eclipse.core.runtime.CoreException: assertion failed: DeleteResourcesRefactoring class is adding a
> at org.teiid.designer.ui.refactor.delete.DeleteResourcesRefactoring.createChange(DeleteResourcesRefactoring.java:232)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
> at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> !SUBENTRY 1 org.teiid.designer.ui.refactor.delete 4 0 2015-04-06 08:26:20.007
> !MESSAGE assertion failed:
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months