[JBoss JIRA] (TEIIDDES-2179) Teiid connection importer choice of dynamic-vdb name needs to be unique
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2179?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2179.
------------------------------------
Resolution: Done
implemented check for existing VDB and added counter to help create unique name. Fixed in master and 8.5.x
> Teiid connection importer choice of dynamic-vdb name needs to be unique
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2179
> URL: https://issues.jboss.org/browse/TEIIDDES-2179
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
>
> When working in a shared server environment, it is possible that two users may try to import schema using "Teiid Connection Importer" and collide on the vbd-name "importer-vdb.xml", and fail to deploy and the whole process.
> The vdb name and file name given should be unique to that instance to avoid collisions.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2238) Add configuration options to set default datatype mapping for columns in source model when importing jdbc datasource
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2238?page=com.atlassian.jira.plu... ]
Van Halbert moved JBDVPL-150 to TEIIDDES-2238:
----------------------------------------------
Project: Teiid Designer (was: JBoss DV Planning)
Key: TEIIDDES-2238 (was: JBDVPL-150)
Issue Type: Feature Request (was: Requirement)
Workflow: classic default workflow (was: CDW v1)
Affects Version/s: Komodo
(was: 6.0.0.GA)
User Story: (was: Steps to Reproduce:
1. generate source model by importing jdbc datasource
Actual results:
User can not change default data type mapping
Expected results:
There is a configuration for default datatype mapping, so user can specify default datatype.)
Component/s: Import/Export
(was: Tooling)
Security: Public
Target Release: (was: 6.2.0.GA)
> Add configuration options to set default datatype mapping for columns in source model when importing jdbc datasource
> --------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2238
> URL: https://issues.jboss.org/browse/TEIIDDES-2238
> Project: Teiid Designer
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: Komodo
> Reporter: hisao furuichi
> Assignee: Van Halbert
>
> Description of problem:
> Lack of configuration to set default datatype mapping for columns in source model when importing jdbc datasource.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2167) Cannot find registered translator "file" when deploying or executing VDB; preview works
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2167?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2167:
-----------------------------------
Fix Version/s: 8.6
Assignee: Mark Drilling
> Cannot find registered translator "file" when deploying or executing VDB; preview works
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2167
> URL: https://issues.jboss.org/browse/TEIIDDES-2167
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Affects Versions: 8.5
> Environment: Windows 7
> Eclipse Kepler with Designer 8.5.0.Alpha2
> JBoss EAP 6.1.0 Final
> JBoss Teiid 8.6.0 Final standalone (localhost)
> Reporter: John Muller
> Assignee: Mark Drilling
> Labels: FileConnector, translator
> Fix For: 8.6
>
> Attachments: standalone-teiid.xml, TEIIDDES-2167_console.log, TEIIDDES-2167_project.zip
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> After modeling a simple CSV file using the "Create source model from local flat file source" and creating a Preview VDB deployed to a local standalone, unclustered Teiid 8.6 final box, the Preview VDB works. However, attempting to deploy the actual VDB fails with:
> "One or more models in VDB "zipFlatFileVDB" are either missing a translator name or have a translator name that is not found on the current Teiid Instance. These translator problems must be fixed before you can deploy the VDB".
> The source model's connection info is below in name -> value pairs:
> connectionProfileProviderId -> org.eclipse.datatools.connectivity.oda.flatfile
> ParentDirectory -> C:\Users\jmuller\Documents
> connectionProfileInstanceID -> 16447210-df7c-11e3-ad0b-97d7f7ba1428
> translator name -> file
> connectionProfileCategory -> org.eclipse.datatools.connectivity.oda.flatfile
> connectionProfileName -> zipFileSource
> connectionProfileDescription ->
> The FileManagedConnectionFactory datasource for the source model was created prior to attempting to deploy the VDB.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2179) Teiid connection importer choice of dynamic-vdb name needs to be unique
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2179?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2179:
-----------------------------------
Issue Type: Bug (was: Enhancement)
Fix Version/s: 8.6
8.5.1
Assignee: Barry LaFond
Should be able to check the server for existing VDB name (importer-vdb.xml). If exists, append the name with a counter.
> Teiid connection importer choice of dynamic-vdb name needs to be unique
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2179
> URL: https://issues.jboss.org/browse/TEIIDDES-2179
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.4, 8.3.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
>
> When working in a shared server environment, it is possible that two users may try to import schema using "Teiid Connection Importer" and collide on the vbd-name "importer-vdb.xml", and fail to deploy and the whole process.
> The vdb name and file name given should be unique to that instance to avoid collisions.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2187) Teiid Connection importer- chosing a location isn't filled in unless you hit back button
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2187?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2187:
-----------------------------------
Fix Version/s: 8.6
8.5.1
Assignee: Mark Drilling
> Teiid Connection importer- chosing a location isn't filled in unless you hit back button
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2187
> URL: https://issues.jboss.org/browse/TEIIDDES-2187
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Import/Export
> Affects Versions: 8.3.2
> Environment: Windows Vista or 2008 Only
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 8.6, 8.5.1
>
>
> This only happens when installed on Windows Vista or 2008 not on Linux.
> Choose File -> Import -> Teiid Designer -> Teiid Connection >> Source model:
> Then, choose a particular data source (shouldn't matter which one)
> Click "Next", this screen will now ask you to choose a location
> Click on the dots behind the grayed out "Location:" field and choose a location
> After selecting a location and pressing the "Ok" button, the location is not taken from the "Select a folder" dialog box and therefore empty.
> If I now choose "Back", I arrive in the previous screen again. Pressing "Next" again now does fill in the previously chosen "Location" value.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2198) Virtual procedure transformation not revalidated after changing parameter datatype
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2198?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2198:
-----------------------------------
Fix Version/s: 8.6
8.5.1
Assignee: Barry LaFond
Probably need to check change in datatype for a column in an input table (t-form dependency) and delete the cached SQL Status. This will force the re-validation on save.
> Virtual procedure transformation not revalidated after changing parameter datatype
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-2198
> URL: https://issues.jboss.org/browse/TEIIDDES-2198
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transformations, Validation
> Affects Versions: 8.3.2
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6, 8.5.1
>
>
> Changing the datatype of a virtual procedure parameter does not trigger revalidation. This means that errors caused by trying to convert the parameter to an incompatible datatype in the transformation do not disappear after fixing the datatype, and conversely, changing the datatype does not trigger validation errors when the new datatype is incompatible.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2222) Verify Teiid version discovery with remote servers
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2222?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2222:
-----------------------------------
Assignee: Paul Richardson
> Verify Teiid version discovery with remote servers
> --------------------------------------------------
>
> Key: TEIIDDES-2222
> URL: https://issues.jboss.org/browse/TEIIDDES-2222
> Project: Teiid Designer
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Teiid Integration
> Affects Versions: 8.5
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.6
>
>
> Description of problem from Jason Stokes below. Need to test teiid version discovery with remote servers.
> We had a problem connecting to a TEIID/DV 6.0 instance on Amazon AWS via Jboss Dev Studio. (Never fully figured out why.) So we FTP'd our VDB we created in Teiid designer 8.5 and deployed it via the Jboss console. I
> forget the error, but something about incompatible versions.
> For whatever reason, JB Dev studio 7.1.1 (with 8.5 teiid designer) was
> reporting that the TEIID version of the AWS server was 8.6, even though it
> was 8.4. (As far as I know, they didn't do anything different but install
> it.) So the consensus was there was a mismatch between the fact we created a TEIID 8.4 version VDB and were trying to deploy it on the AWS server. (The local server I was testing with reported the correct version of TEIID 8.4 in dev studio.) Technically both installs should have been the same version though (8.4) so not sure what was going on.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2237) Server credentials for multiple Teiid instances sharing password
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2237?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2237:
----------------------------------------
Looks like the secure pwd storage is setting the provider key via *getClass() and getUrl()* which unless host/port are different, will not be unique between servers (i.e. org/teiid/datatools/connectivity/TeiidJdbcInfo/jdbc:teiid:<vdbname>@mm://localhost:31000/)
Suggest we inject the unique server ID in TeiidConnectionInfo
private String getProviderKey() {
return ConnectivityUtil.buildSecureStorageKey(getClass(), getUrl(), *getServerId()* );
}
> Server credentials for multiple Teiid instances sharing password
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2237
> URL: https://issues.jboss.org/browse/TEIIDDES-2237
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.5
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.6, 8.5.1
>
>
> 1) Set up EAP6.1Alpha + Teiid 7.7Final server (username=user, pwd=user)
> * Open Teiid server editor page and see user/****
> 2) Set up DV6.1DR1 server (username=teiidUser, pwd =teiidUser)
> 3) Start DV6.1DR1 server and open Teiid server editor page and see teiidUser/******** properties. Stop server.
> 4) Start EAP6.1Alpha + Teiid 7.7Final. Open Teiid server editor page and see user/********
> Seems the PWD from one server is being used for multiple servers?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2235) Preview uses Pool Name instead of JNDI name
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2235?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2235.
------------------------------------
Resolution: Done
Fixed in both 8.5.x and master brances
> Preview uses Pool Name instead of JNDI name
> -------------------------------------------
>
> Key: TEIIDDES-2235
> URL: https://issues.jboss.org/browse/TEIIDDES-2235
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Data Preview, Import/Export
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.6, 8.5.1
>
> Attachments: connection_profile.png, names.xlsx
>
>
> I am using almost latest 8.5-nightly, and latest 8.8 Teiid.
> I created a file data source in server using CLI
> {code}
> /subsystem=resource-adapters/resource-adapter=fileExcel:add(module=org.jboss.teiid.resource-adapter.file)
> /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS:add(jndi-name="java:/excel-ds", class-name=org.teiid.resource.adapter.file.FileManagedConnectionFactory, enabled=true, use-java-context=true)
> /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS/config-properties=ParentDirectory:add(value="/home/rareddy/Downloads" )
> /subsystem=resource-adapters/resource-adapter=fileExcel:activate
> {code}
> here
> fileExcel = is resource adapter name
> fileDS = pool-name
> java:/excel-ds = JNDI name
> All the communication over the Admin API occurs over "pool-name", however JNDI name is what should be used in the "connection-jndi-name"
> Now, I used "Teiid Connection Importer" to import from data source created above, used "excel" translator, created a model. It created a "sheet1" table. Now right click preview, I see
> {code}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 Names: TEIID30481 Failed to find the Connection Factory with JNDI name fileDS. Please check the name or deploy the Connection Factory with specified name.
> {code}
> which is wrong. "Right-Click -> View Connection Profile Dialog" attached.
> I have been suggesting to use a simple "JNDI" based data source connection profile for dealing with the data sources on server to avoid issues like this, and I see designer is going more towards other side adding dependencies like BIRT etc.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (TEIIDDES-2235) Preview uses Pool Name instead of JNDI name
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2235?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2235:
-----------------------------------
Fix Version/s: 8.6
8.5.1
Assignee: Barry LaFond
Affects Version/s: 8.5
Component/s: Import/Export
> Preview uses Pool Name instead of JNDI name
> -------------------------------------------
>
> Key: TEIIDDES-2235
> URL: https://issues.jboss.org/browse/TEIIDDES-2235
> Project: Teiid Designer
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Data Preview, Import/Export
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.6, 8.5.1
>
> Attachments: connection_profile.png, names.xlsx
>
>
> I am using almost latest 8.5-nightly, and latest 8.8 Teiid.
> I created a file data source in server using CLI
> {code}
> /subsystem=resource-adapters/resource-adapter=fileExcel:add(module=org.jboss.teiid.resource-adapter.file)
> /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS:add(jndi-name="java:/excel-ds", class-name=org.teiid.resource.adapter.file.FileManagedConnectionFactory, enabled=true, use-java-context=true)
> /subsystem=resource-adapters/resource-adapter=fileExcel/connection-definitions=fileDS/config-properties=ParentDirectory:add(value="/home/rareddy/Downloads" )
> /subsystem=resource-adapters/resource-adapter=fileExcel:activate
> {code}
> here
> fileExcel = is resource adapter name
> fileDS = pool-name
> java:/excel-ds = JNDI name
> All the communication over the Admin API occurs over "pool-name", however JNDI name is what should be used in the "connection-jndi-name"
> Now, I used "Teiid Connection Importer" to import from data source created above, used "excel" translator, created a model. It created a "sheet1" table. Now right click preview, I see
> {code}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidProcessingException: TEIID30504 Names: TEIID30481 Failed to find the Connection Factory with JNDI name fileDS. Please check the name or deploy the Connection Factory with specified name.
> {code}
> which is wrong. "Right-Click -> View Connection Profile Dialog" attached.
> I have been suggesting to use a simple "JNDI" based data source connection profile for dealing with the data sources on server to avoid issues like this, and I see designer is going more towards other side adding dependencies like BIRT etc.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months