December 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2401: ---------------------------------------- I think you are missing the point, the artifact can be a file,database, a git repo or combination of all. There is no such thing single artifact to export in Teiid. A Dynamic VDB is deployment file that represents all these metadata repos in its XML. One of the repo types *is* in-lining the DDL, but that is not the only type. Think Dynamic VDB as configuration file, rather than source of metadata. >There's still no single artifact that can be obtained that represents what is actually running. What is actually running is what a *user* deployed. If user does not have copy of what deployed, then that is not an issue Teiid should set out solve. Thus the we are talking about using metadata repositories and versioning of those repositories during the development time, so that user has an accurate note of what has been deployed what has changed etc. We want to develop above mentioned Metadata repository in Teiid, once this is available may that be Modeshape or Git or RDBMS > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2401: --------------------------------------- the propagation to other servers still misses the point. There's still no single artifact that can be obtained that represents what is actually running. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2345) Using VARIABLES.ROWCOUNT in update procedure causes validation error

by Andrej Šmigala (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2345?page=com.atlassian.jira.plu... ] Andrej Šmigala updated TEIIDDES-2345: ------------------------------------- Attachment: RowcountProject.zip The attached project has no errors in 8.3.4, but causes the above error when imported in 8.6+ > Using VARIABLES.ROWCOUNT in update procedure causes validation error > -------------------------------------------------------------------- > > Key: TEIIDDES-2345 > URL: https://issues.jboss.org/browse/TEIIDDES-2345 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.6 > Reporter: Andrej Šmigala > Assignee: Paul Richardson > Attachments: RowcountProject.zip > > > Trying to get the number of affected rows in the update/insert/delete procedure of a view table by using the VARIABLES.ROWCOUNT variable causes the following error: > {quote}ERROR: TEIID31118 Element "VARIABLES.ROWCOUNT" is not defined by any relevant group.{quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2345) Using VARIABLES.ROWCOUNT in update procedure causes validation error

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2345?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2345: -------------------------------------- Assignee: Paul Richardson (was: Barry LaFond) > Using VARIABLES.ROWCOUNT in update procedure causes validation error > -------------------------------------------------------------------- > > Key: TEIIDDES-2345 > URL: https://issues.jboss.org/browse/TEIIDDES-2345 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.6 > Reporter: Andrej Šmigala > Assignee: Paul Richardson > > Trying to get the number of affected rows in the update/insert/delete procedure of a view table by using the VARIABLES.ROWCOUNT variable causes the following error: > {quote}ERROR: TEIID31118 Element "VARIABLES.ROWCOUNT" is not defined by any relevant group.{quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2401: ---------------------------------------- >Because, right now, if a VDB is changed via CLI, there's no way to get that VDB out so that it can be redeployed on another server. In domain model it is automatically propagated to other servers in the domain. >Teiid would persist the changed VDB to the filesystem You can open JIRA with EAP/WildFly, they are the ones who manage any deployment artifacts in JBoss EAP. If they allow to export artifacts, then consider we got what you are looking for. There is no access to the resource from Teiid, just a service. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2401: --------------------------------------- I would like to see Teiid, after having a VDB updated via CLI, to have the VDB saved to the filesystem in a format such that it can be redeployed. Because, right now, if a VDB is changed via CLI, there's no way to get that VDB out so that it can be redeployed on another server. In an ideal world, Teiid would persist the changed VDB to the filesystem, so that when an API method is called to get VDB, the current state of the VDB is returned in a form that can be deployed to another server. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2401: ---------------------------------------- Teiid does not have built-in concept of Dynamic VDB, .VDB etc, they are just VDBS or more abstractly they are just sources of metadata. The distinction about the artifacts that represent the VDB is removed as soon as they are deployed. That can be DDL, .VDB or database. So, Yes, we can do that, that would be useless and wrong place to do it. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[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 commented on TEIIDDES-2401: ---------------------------------------- In debug, I intercepted the getSchema() method via the Teiid importer and verified that if I give it deployed VDB name, it can return virtual table DDL for a view model. So, my next question is.... wouldn't it be fairly straight forward to "export" a VDB.vdb as a dynamic VDB? I.e. Teiid runtime does the conversion? All the metadata is already on the server side, (including the -vdb.xml maniffest) and the methods to convert the metadata into DDL already work. All that's left is to inject the DDL into the VDB XML and the conversion is done? If we're going to require the user to Deploy a VDB anyway in order to create a dynamic VDB version of it, seems like the utility makes more sense as part of the API. maybe something like: *String getDynamicVdb(String vdbName, int version, String[] modelNames, EnumSet<SchemaObjectType> allowedTypes, String typeNamePattern));* Designer would wrap this as maybe an *Convert to Dynamic VDB* action for a deployed VDB (server view/wizard) or via an action in the workspace that would/could temporarily auto-deploy a VDB, do the import/conversion, then undeploy the VDB. Being on the server-side, users could also programattically convert/export EMF VDB's to dynamic VDBs. Openshift would also benefit if users were going to migrate in the future. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2406) Provide option to set JNDI, instead of Connection Profile, in order to do data preview

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2406: ---------------------------------------- [~blafond] I am not sure about what you are thinking process with above. So, do not have any comment there. Long time ago, I suggested to create a dummy JNDI connection profile to choose instead of real connection profile to sync up with rest of the framework for situations like this and for Teiid Importer purposes. IMO, Connection profiles has been a some what failed / fragile attempt, as we were doing * Connection Profile (definition) * Connection profile based *local* connection * Data source based on connection profile - preview data source * Data source based on connection profile - *named* a data source * Teiid Importer - Teiid server based connection ( this starts with *named*) * Teiid Importer - Teiid server based connection, connection profile to support the other hooks else where So too many things to keep track of. Teiid Designer does not care for *local* connections except for in the case JDBC importing, rest every thing falls into a server based data source named or otherwise. For that we carry a hefty price of managing these connection profiles and keeping them in sync. So, I have been advocating to remove that hurdle, and base all on the server data source. I know, that is a bigger issue, I may be simplifying the issue, however that is what I would like to see us accomplish. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2401) Add support exporting the Designer VDB as Dynamic VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2401?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2401: ---------------------------------------- Admin API "getSchema()" works on Dynamic VDBs as well as .VDB files. i.e if someone deployed a .VDB and asked getSchema() on any model (except XML document model) it will return DDL for that model. As working set of VDB, Designer deploys a set of preview VDBS, I am saying issue a "getSchema()" on them to get the DDL for corresponding model. > 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 > > 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.11#6341)

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2014