December 2014 - teiid-designer-issues

[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: ---------------------------------------- The Teiid Importer generates a temporary Dynamic VDB that contains a temporary Source model where it's data source is the VDB's data source. There is really no "schema" data in this VDB. getSchema() returns the schema for that "model", however, it's really a pass-through to the underlying VDB data source, hence it's viewed as a simple JDBC source. > 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, 3 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: ---------------------------------------- If Admin API getSchema() is called on view model, it will (should) return the DDL appropriately, if it is not then either view model is being deployed wrong as wrong type or Teiid returning the DDL wrong. > 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, 3 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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2406: ---------------------------------------- I don't have a mock-up, but we can put any properties in the panel we want. Here are the connection properties currently stored in a source model and visible via *Modeling > View Connection Profile Info* action/dialog * Discovered during JDBC/Teiid import but changable by user* key="translator:name" value="db2"/> *Defined via the connection profile and used for runtime Data Source creation* key="connection:driver-class" value="com.ibm.db2.jcc.DB2Driver" key="connection:jarList" value="/home/blafond/Testing/drivers/jdbc_4_drivers/db2jcc4.jar" key="connection:connection-url" value="jdbc:db2://slntds05.mw.lab.eng.bos.redhat.com:50000/ds05:retrieveMessagesFromServerOnGetMessage=true;" key="connection:user-name" value="partssupplier" *Info used match profile when re-importing* key="connectionProfile:connectionProfileName" value="PartsDB2" key="connectionProfile:connectionProfileCategory" value="org.eclipse.datatools.connectivity.db.category" key="connectionProfile:connectionProfileDescription" value=""/> key="connectionProfile:connectionProfileInstanceID" value="1df344c0-cf11-11df-a523-a82e9f061fc5" key="connectionProfile:connectionProfileProviderId" value="org.eclipse.datatools.enablement.ibm.db2.luw.connectionProfile" key="connection:connectionProfileInstanceID" value="org.eclipse.datatools.enablement.ibm.db2.luw.connectionProfile" > 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, 3 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: ---------------------------------------- [~rareddy] This could work for source models, but won't Virtual Tables, get returned as source table DDL (i.e. *CREATE FOREIGN TABLE "DB2_DS_VDB.Parts_DB2.PARTS" ( ..... )* ). Is there an option through the Admin API getSchema() call to return CREATE VIEW "DB2_DS_VDB.Parts_DB2.PARTS"( .... ) AS SELECT * FROM ........ instead? > 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, 3 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: ---------------------------------------- I agree that JNDI name and translator override properties come together in a VDB artifact, but not necessarily tied to a VDB. That is the persisted form we choose to deliver to the server. Do you have any mockup for your Source Connection panel? I would ideally see all these connection profiles and JNDI sources come together as one. > 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, 3 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: ---------------------------------------- Designer already building the vdb.xml when a .vdb file is created. The extra step it needs to do is iterate over models in the vdb, then query for their DDL from server then include in a metadata element of model for the vdb.xml. This can also help us phase out .vdb version of the artifact. > 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, 3 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: ---------------------------------------- Not sure how to implement this feature. We already have a DDL Export feature in Designer, but it would require developing a Teiid-specific xslt style sheet. Another option is to develop a EMF visitor framework that outputs DDL. Maybe we can leverage some of the architecture of what Paul's working on for Komodo. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2405: ----------------------------------- Fix Version/s: 9.1 > Teiid Importer *MUST* not require class-name property working with Teiid Sources > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2405 > URL: https://issues.jboss.org/browse/TEIIDDES-2405 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Priority: Critical > Fix For: 9.1 > > > When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source > {code} > {"managedconnectionfactory-class" => { > "type" => STRING, > "display" => "managedconnectionfactory-class", > "read-only" => "true", > "advanced" => "true", > "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" > }}, > {code} > That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 3 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 Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2406?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2406: ---------------------------------------- Currently source models maintain "connection" info. This info relates to connection profile information. We also inject the *translator* type in these properties. The JNDI name for a source model, however, is currently only defined a VDB and it can be different for a source model in different VDBs. So specifying a JNDI name - per - source model is doable, however we'd be setting precident, or changing our paradigm a little. So would we want a *Source Connection* panel (via dialog/wizard or view) that would contain at least 1) Translator type and 2) JNDI name ? We've also have a JIRA which would make it possible to define Translator Override instances to be defined outside of a VDB and used for multiple source models, which is also changing our VDB-centric editing of source model connection info. > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2050) Full Temp Table support in Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2050?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2050: ---------------------------------------- new extension property (OPTION) > Full Temp Table support in Designer > ----------------------------------- > > Key: TEIIDDES-2050 > URL: https://issues.jboss.org/browse/TEIIDDES-2050 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Future > > > Per TEIIDDES-1794 there are more areas Designer needs to add support for temporary tables: > ... the full array of temp table stuff we currently support is: > * Teiid global temporary table (a virtual entry - which from an engine perspective can be on any model type) > * Teiid temporary table (not a schema entry in the design time metadata, scoped to a session/block) > * Teiid temporary table backed by a physical table (not a schema entry in the design time metadata, scoped to a session/block - the physical table could be a temporary one) > Eventually we would also like to have an ease of use path to simply create a teiid temporary table and have the backing table created on a source automatically - similar to the data shipment join temporary table creation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 3 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