[JBoss JIRA] (TEIIDDES-3065) VDB Export to Import problem
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3065?page=com.atlassian.jira.plu... ]
Steve Tran updated TEIIDDES-3065:
---------------------------------
Attachment: HostSettlement-vdb.xml
> VDB Export to Import problem
> ----------------------------
>
> Key: TEIIDDES-3065
> URL: https://issues.jboss.org/browse/TEIIDDES-3065
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.1
> Environment: Windows 7
> JBoss Developer Studio 10.3.0.GA
> Teiid Designer 10.1.0.GA
> Reporter: Steve Tran
> Attachments: HostSettlement-vdb.xml, Screenshot from 2017-03-21 13-29-38.png
>
>
> I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
> {code}
> The message says "Unparsable table body".
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:40.629
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:40.629
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:48.784
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:48.784
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:35:15.660
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:35:15.660
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3065) VDB Export to Import problem
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3065?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3065:
----------------------------------------
[~sqtran] Steve, if you could attach the dynamic VDB I can debug the import to see where the parser is failing. The error messages say it has bad TABLE DDL.
> VDB Export to Import problem
> ----------------------------
>
> Key: TEIIDDES-3065
> URL: https://issues.jboss.org/browse/TEIIDDES-3065
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.1
> Environment: Windows 7
> JBoss Developer Studio 10.3.0.GA
> Teiid Designer 10.1.0.GA
> Reporter: Steve Tran
> Attachments: Screenshot from 2017-03-21 13-29-38.png
>
>
> I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
> {code}
> The message says "Unparsable table body".
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:40.629
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:40.629
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:48.784
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:48.784
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:35:15.660
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:35:15.660
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3065) VDB Export to Import problem
by Steve Tran (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3065?page=com.atlassian.jira.plu... ]
Steve Tran updated TEIIDDES-3065:
---------------------------------
Description:
I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
{code}
The message says "Unparsable table body".
!ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:40.629
!MESSAGE An exception occurred while performing a VDB operation
!SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:40.629
!MESSAGE * Error Message: Unparsable table body
Error Line Number: 323
Error Column Number: 42
Error Index: 29455
!ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:48.784
!MESSAGE An exception occurred while performing a VDB operation
!SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:48.784
!MESSAGE * Error Message: Unparsable table body
Error Line Number: 323
Error Column Number: 42
Error Index: 29455
!ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:35:15.660
!MESSAGE An exception occurred while performing a VDB operation
!SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:35:15.660
!MESSAGE * Error Message: Unparsable table body
Error Line Number: 323
Error Column Number: 42
Error Index: 29455
{code}
was:
I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
The message says "Unparsable table body".
> VDB Export to Import problem
> ----------------------------
>
> Key: TEIIDDES-3065
> URL: https://issues.jboss.org/browse/TEIIDDES-3065
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.1
> Environment: Windows 7
> JBoss Developer Studio 10.3.0.GA
> Teiid Designer 10.1.0.GA
> Reporter: Steve Tran
> Attachments: Screenshot from 2017-03-21 13-29-38.png
>
>
> I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
> {code}
> The message says "Unparsable table body".
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:40.629
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:40.629
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:28:48.784
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:28:48.784
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> !ENTRY org.teiid.designer.vdb 4 4 2017-03-21 13:35:15.660
> !MESSAGE An exception occurred while performing a VDB operation
> !SUBENTRY 1 org.teiid.designer.vdb 4 0 2017-03-21 13:35:15.660
> !MESSAGE * Error Message: Unparsable table body
> Error Line Number: 323
> Error Column Number: 42
> Error Index: 29455
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3065) VDB Export to Import problem
by Steve Tran (JIRA)
Steve Tran created TEIIDDES-3065:
------------------------------------
Summary: VDB Export to Import problem
Key: TEIIDDES-3065
URL: https://issues.jboss.org/browse/TEIIDDES-3065
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 10.1
Environment: Windows 7
JBoss Developer Studio 10.3.0.GA
Teiid Designer 10.1.0.GA
Reporter: Steve Tran
I exported my VDB as a dynamic VDB file, then I attempted to re-import it but got an error message.
The message says "Unparsable table body".
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3064) Create EAP translator
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3064?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-3064:
------------------------------------------
This will likely be supported for Teiid 10. As part of TEIID-2578 Ramesh was already looking to support this, but that is not fully ready yet. There are a lot of issues to work through though, the primary one being ownership/scoping as the datasources are server wide.
> Create EAP translator
> ---------------------
>
> Key: TEIIDDES-3064
> URL: https://issues.jboss.org/browse/TEIIDDES-3064
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Tom Johnston
>
> Creating an EAP translator would allow for DDL to be used to create EAP items such as datasources).
> Where a source model table (foreign table) is bound to a JNDI, why not allow the creation of the JNDI as a part of the overall model.
> I.E. Create Foreign Source <ForeignSourceName> using <Translator> with JDBC URL 'xxx'
> this way when creating Foreign Tables you would refer to the ForeignSource similar to DBMS's (i.e. create table xyx as select xxx from table@datalink)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3064) Create EAP translator
by Tom Johnston (JIRA)
Tom Johnston created TEIIDDES-3064:
--------------------------------------
Summary: Create EAP translator
Key: TEIIDDES-3064
URL: https://issues.jboss.org/browse/TEIIDDES-3064
Project: Teiid Designer
Issue Type: Enhancement
Reporter: Tom Johnston
Creating an EAP translator would allow for DDL to be used to create EAP items such as datasources).
Where a source model table (foreign table) is bound to a JNDI, why not allow the creation of the JNDI as a part of the overall model.
I.E. Create Foreign Source <ForeignSourceName> using <Translator> with JDBC URL 'xxx'
this way when creating Foreign Tables you would refer to the ForeignSource similar to DBMS's (i.e. create table xyx as select xxx from table@datalink)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3062) Add support for Teiid DDL export to include dependent objects
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3062?page=com.atlassian.jira.plu... ]
Tom Johnston commented on TEIIDDES-3062:
----------------------------------------
Barry, to answer your first question, I would say that ideally when there are cross-schema(model) objects then asking to generate all within one script or separate (one for each schema/model) would be great. I also assume that the dependent order would be taken into account (i.e. View one depends upon View 2 and View 3 etc would result in the supporting views appearing in the script ahead of the dependent ones).
As a side note... the reason I came across this was I had a model in another project and instead of re-creating/importing from source I thought I'd just export the DDL then import the DDL in the other project.... would there have been a better way?
> Add support for Teiid DDL export to include dependent objects
> -------------------------------------------------------------
>
> Key: TEIIDDES-3062
> URL: https://issues.jboss.org/browse/TEIIDDES-3062
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Tom Johnston
> Attachments: TeiidDES3062.jpg
>
>
> It would be helpful that if when performing an Export at model level there would be an option on the following screen to include all supporting objects.
> !image-2017-03-14-11-33-38-504.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3062) Add support for Teiid DDL export to include dependent objects
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3062?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-3062:
----------------------------------------
[~virtualdatabase] So if exporting DDL for a model equates to a Schema, then if a View in that schema references one or more source models... do you want the source DDL added to the same DDL file?
Note that adding the view model to a VDB and then generating a dynamic VDB will get you the DDL you are looking for. So will selecting a View and doing a Preview Data (test). The dialog will show the VDB XML containing related/dependent DDL.
> Add support for Teiid DDL export to include dependent objects
> -------------------------------------------------------------
>
> Key: TEIIDDES-3062
> URL: https://issues.jboss.org/browse/TEIIDDES-3062
> Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Tom Johnston
> Attachments: TeiidDES3062.jpg
>
>
> It would be helpful that if when performing an Export at model level there would be an option on the following screen to include all supporting objects.
> !image-2017-03-14-11-33-38-504.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (TEIIDDES-3063) UI improvement for procedure materialisation
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-3063?page=com.atlassian.jira.plu... ]
Barry LaFond moved JBDVPL-462 to TEIIDDES-3063:
-----------------------------------------------
Project: Teiid Designer (was: JBoss DV Planning)
Key: TEIIDDES-3063 (was: JBDVPL-462)
Issue Type: Feature Request (was: Requirement)
Workflow: classic default workflow (was: CDW v1)
Component/s: Modeling
(was: Client Tooling)
> UI improvement for procedure materialisation
> --------------------------------------------
>
> Key: TEIIDDES-3063
> URL: https://issues.jboss.org/browse/TEIIDDES-3063
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 12.0
>
>
> UI improvement for procedure materialisation
> this is related to JBDVPL-430 and JBDVPL-161
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months