[JBoss JIRA] (TEIIDDES-2806) Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb
by Debbie Steigner (JIRA)
Debbie Steigner created TEIIDDES-2806:
-----------------------------------------
Summary: Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb
Key: TEIIDDES-2806
URL: https://issues.jboss.org/browse/TEIIDDES-2806
Project: Teiid Designer
Issue Type: Feature Request
Components: Dynamic VDBs
Affects Versions: 9.2, 9.0.3
Reporter: Debbie Steigner
Assignee: Barry LaFond
The Teiid vdb has column named e.g. PE$HOME. When I generate a dynamic vdb xml from this model, the xml document contains:
CREATE FOREIGN TABLE MYTABLE (
ID string(40) NOT NULL,
NAME string(40),
PE$HOME string(19) NOT NULL,
CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID)
)
When i deploy this, it fails because P$HOME is not allowed as column name.
I expect to see this name "quoted" in the xml vdb:
CREATE FOREIGN TABLE MYTABLE (
"ID" string(40) NOT NULL,
"NAME" string(40),
"PE$HOME" string(19) NOT NULL,
CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID)
)
Proposed solution: always use "quotes" in source and view xml vdb, both for the column names, and the mapping statement.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2804) Resource adapter is not refreshed after I hit execute VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2804?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2804:
----------------------------------------
When deploying a VDB, Designer will first check to see if any source model DS's are already deployed. This means checking if the JNDI-NAME exists in the DS list.
The default behavior for Designer is to us the *model name* as the default DS/JNDI name. In your case, both projects used the default.
In practice, I think users will either already have DS's deployed on the server with specific JNDI names. Designer allows setting theJNDI name on a model as well as changing it once added to a VDB.
So the errors you are getting are correct.... and the default behavior is confusing and will lead to these errors.
Guess the default behavior on Import could be to force the user to defined a specific JNDI name before the model is saved? If a running default server is detected, the wizard could check whether a JNDI name exists or not and warn the user?
> Resource adapter is not refreshed after I hit execute VDB
> ---------------------------------------------------------
>
> Key: TEIIDDES-2804
> URL: https://issues.jboss.org/browse/TEIIDDES-2804
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
>
> I have a VDB with source model that references a data source (resource adapter - flat file) with name that already exists on server. Let's say the name is "adapter1".
> After I hit execute on VDB, it is deployed and I can submit a query. Submitting query reports an error that a flat file is not found. When I look to standalone.xml, the resource adapter "adapter1" is not changed and there is still the old one with wrong path to file. (both RA are of the same type - file)
> It looks like when I execute a VDB, TD checks if there is data source (resource adapter) with name specified in VDB. If there is such data source it doesn't check other properties of the data source (RA) (at least it looks like that, maybe it checks the type of RA).
> Or is this a server issue ?
> This may seem like a crazy use case, but when you go through the "import from flat file" wizard twice (with different projects) and don't change the model names you end up with two projects with same source model names. Default source model name in the wizard is "SourceModel" and I think TD uses source model name as data source name for VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2804) Resource adapter is not refreshed after I hit execute VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2804?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2804:
-----------------------------------
Priority: Minor (was: Major)
> Resource adapter is not refreshed after I hit execute VDB
> ---------------------------------------------------------
>
> Key: TEIIDDES-2804
> URL: https://issues.jboss.org/browse/TEIIDDES-2804
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
> Priority: Minor
>
> I have a VDB with source model that references a data source (resource adapter - flat file) with name that already exists on server. Let's say the name is "adapter1".
> After I hit execute on VDB, it is deployed and I can submit a query. Submitting query reports an error that a flat file is not found. When I look to standalone.xml, the resource adapter "adapter1" is not changed and there is still the old one with wrong path to file. (both RA are of the same type - file)
> It looks like when I execute a VDB, TD checks if there is data source (resource adapter) with name specified in VDB. If there is such data source it doesn't check other properties of the data source (RA) (at least it looks like that, maybe it checks the type of RA).
> Or is this a server issue ?
> This may seem like a crazy use case, but when you go through the "import from flat file" wizard twice (with different projects) and don't change the model names you end up with two projects with same source model names. Default source model name in the wizard is "SourceModel" and I think TD uses source model name as data source name for VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2466 at 3/7/16 10:38 AM:
-----------------------------------------------------------------
This feature could be implemented by utilizing a temporary dynamic VDB artifact rather than the current EMF VDB archive.
User could select a table or view. Designer would need to construct a temporary dynamic VDB containing a simple <model> entry for each dependent model + the selected model. These models would contain DDL representing only the tables necessary to execute the query on the source(s).
*Benefits* : would include removing (or drastically reducing the complexity) the whole framework around maintaining a project VDB as well a preview VDB for each model
*Drawbacks*
* there may be a performance hit to always deploy a VDB (and undeploy) for Preview Data
* Views using UDF methods would need to include the function in the DDL. UDF jar would have to be deployed separately prior to deploying the dyn. vdb.
was (Author: blafond):
This feature could be implemented by utilizing a temporary dynamic VDB artifact rather than the current EMF VDB archive.
User could select a table or view. Designer would need to construct a temporary dynamic VDB containing a simple <model> entry for each dependent model + the selected model. These models would contain DDL representing only the tables necessary to execute the query on the source(s).
*Benefits* : would include removing (or drastically reducing the complexity) the whole framework around maintaining a project VDB as well a preview VDB for each model
*Drawbacks* : there may be a performance hit to always deploy a VDB (and undeploy) for Preview Data
> Create Preview VDB for only the model containing the table that is being preview
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2466
> URL: https://issues.jboss.org/browse/TEIIDDES-2466
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview
> Affects Versions: 9.0
> Reporter: Debbie Steigner
>
> RFE
> Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2466:
----------------------------------------
This feature could be implemented by utilizing a temporary dynamic VDB artifact rather than the current EMF VDB archive.
User could select a table or view. Designer would need to construct a temporary dynamic VDB containing a simple <model> entry for each dependent model + the selected model. These models would contain DDL representing only the tables necessary to execute the query on the source(s).
*Benefits* : would include removing (or drastically reducing the complexity) the whole framework around maintaining a project VDB as well a preview VDB for each model
*Drawbacks* : there may be a performance hit to always deploy a VDB (and undeploy) for Preview Data
> Create Preview VDB for only the model containing the table that is being preview
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2466
> URL: https://issues.jboss.org/browse/TEIIDDES-2466
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview
> Affects Versions: 9.0
> Reporter: Debbie Steigner
>
> RFE
> Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2803) VDB could not be validated after import from File system
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2803?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2803:
-----------------------------------
Component/s: Patch Release
VDB & Execution
> VDB could not be validated after import from File system
> --------------------------------------------------------
>
> Key: TEIIDDES-2803
> URL: https://issues.jboss.org/browse/TEIIDDES-2803
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, VDB & Execution
> Affects Versions: 10.0
> Environment: MAC OS X
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Fix For: 10.0.1
>
> Attachments: UdfVDB1.vdb
>
>
> After I import attached VDB to new project (using Import -> File System) TD says that this VDB could not be validated. The VDB was created in the same TD (same version and environment).
> Error view:
> The Teiid Designer vdb file "UdfVDB1.vdb" could not be validated
> {code:java}
> java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:854)
> at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042)
> at org.teiid.designer.vdb.VdbUtil.validateVdbModelsInWorkspace(VdbUtil.java:689)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.refreshVdbFileMarkers(VdbBuilder.java:167)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.buildInternal(VdbBuilder.java:137)
> at org.teiid.designer.core.builder.AbstractTeiidProjectBuilder.build(AbstractTeiidProjectBuilder.java:76)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2803) VDB could not be validated after import from File system
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2803?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2803:
-----------------------------------
Fix Version/s: 10.0.1
> VDB could not be validated after import from File system
> --------------------------------------------------------
>
> Key: TEIIDDES-2803
> URL: https://issues.jboss.org/browse/TEIIDDES-2803
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: MAC OS X
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Fix For: 10.0.1
>
> Attachments: UdfVDB1.vdb
>
>
> After I import attached VDB to new project (using Import -> File System) TD says that this VDB could not be validated. The VDB was created in the same TD (same version and environment).
> Error view:
> The Teiid Designer vdb file "UdfVDB1.vdb" could not be validated
> {code:java}
> java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:854)
> at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042)
> at org.teiid.designer.vdb.VdbUtil.validateVdbModelsInWorkspace(VdbUtil.java:689)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.refreshVdbFileMarkers(VdbBuilder.java:167)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.buildInternal(VdbBuilder.java:137)
> at org.teiid.designer.core.builder.AbstractTeiidProjectBuilder.build(AbstractTeiidProjectBuilder.java:76)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2803) VDB could not be validated after import from File system
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2803?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2803.
------------------------------------
Resolution: Done
master: https://github.com/Teiid-Designer/teiid-designer/commit/024a0e7f1f5b901aa...
> VDB could not be validated after import from File system
> --------------------------------------------------------
>
> Key: TEIIDDES-2803
> URL: https://issues.jboss.org/browse/TEIIDDES-2803
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Environment: MAC OS X
> Reporter: Matus Makovy
> Assignee: Paul Richardson
> Attachments: UdfVDB1.vdb
>
>
> After I import attached VDB to new project (using Import -> File System) TD says that this VDB could not be validated. The VDB was created in the same TD (same version and environment).
> Error view:
> The Teiid Designer vdb file "UdfVDB1.vdb" could not be validated
> {code:java}
> java.util.NoSuchElementException
> at java.util.ArrayList$Itr.next(ArrayList.java:854)
> at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042)
> at org.teiid.designer.vdb.VdbUtil.validateVdbModelsInWorkspace(VdbUtil.java:689)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.refreshVdbFileMarkers(VdbBuilder.java:167)
> at org.teiid.designer.vdb.ui.build.VdbBuilder.buildInternal(VdbBuilder.java:137)
> at org.teiid.designer.core.builder.AbstractTeiidProjectBuilder.build(AbstractTeiidProjectBuilder.java:76)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (TEIIDDES-2805) Error message not helpful when you try to execute VDB with no credentials defined for JDBC connection to server
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2805?page=com.atlassian.jira.plu... ]
Matus Makovy updated TEIIDDES-2805:
-----------------------------------
Description:
I defined new connection to server and forgot to set username and password for JDBC connection to server.
After I hit execute on VDB TD shows an error in Errors view:
"Could not deploy the following VDB for execution: FlatFileVdb1.vdb"
In the Stack Trace there is: "Error acquiring connection profile properties"
It looks like there are some problems with connection profile in the source model to me. This is not true, the VDB was deployed. Problem was that there were no credentials set for JDBC connection to teiid. It took me a while to figure it out.
After I enter username and password everything works.
It looks like this is a consequence of TEIIDDES-2435.
was:
I defined new connection to server and forgot to set username and password for JDBC connection to server.
After I hit execute on VDB TD shows an error in Errors view:
"Could not deploy the following VDB for execution: FlatFileVdb1.vdb"
In the Stack Trace there is: "Error acquiring connection profile properties"
I looks like there are some problems with connection profile in the source model to me. This is not true, the VDB was deployed. Problem was that there were no credentials set for JDBC connection to teiid. It took me a while to figure it out.
After I enter username and password everything works.
It looks like this is a consequence of TEIIDDES-2435.
> Error message not helpful when you try to execute VDB with no credentials defined for JDBC connection to server
> ---------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2805
> URL: https://issues.jboss.org/browse/TEIIDDES-2805
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
> Attachments: Screen Shot 2016-03-07 at 14.01.30.png
>
>
> I defined new connection to server and forgot to set username and password for JDBC connection to server.
> After I hit execute on VDB TD shows an error in Errors view:
> "Could not deploy the following VDB for execution: FlatFileVdb1.vdb"
> In the Stack Trace there is: "Error acquiring connection profile properties"
> It looks like there are some problems with connection profile in the source model to me. This is not true, the VDB was deployed. Problem was that there were no credentials set for JDBC connection to teiid. It took me a while to figure it out.
> After I enter username and password everything works.
> It looks like this is a consequence of TEIIDDES-2435.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months