[JBoss JIRA] Created: (TEIIDDES-1022) Add Model Extension Definition ID to ModelResource
by Barry LaFond (JIRA)
Add Model Extension Definition ID to ModelResource
--------------------------------------------------
Key: TEIIDDES-1022
URL: https://issues.jboss.org/browse/TEIIDDES-1022
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.5, 7.4.2
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Blocker
Fix For: 7.5, 7.4.2
The Model Extension Definition ID (i.e. "salesforce" for instance) needs to be persisted with the model resource in order to allow the RuntimeAdapter to actually add extended "default" properties.
Also need a method for the extension assistant...
assistant.hasExtensionProperties(File, String)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-908) Replace Salesforce Extension Model created during import
by Barry LaFond (JIRA)
Replace Salesforce Extension Model created during import
---------------------------------------------------------
Key: TEIIDDES-908
URL: https://issues.jboss.org/browse/TEIIDDES-908
Project: Teiid Designer
Issue Type: Enhancement
Components: Import/Export
Affects Versions: 7.3
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Blocker
Fix For: 7.4
In order to simplify JDBC import processing by replacing Designer's RelationalModelProcessor with Teiid's processor, the Salesforce Import use-case needs to be simplified by removing the need to have a separate Extension model.
TEIIDDES-905 is providing a new extension model framework that eliminates the need for a separate model.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-926) Create persistance and loading mechanism for XML-based Model Extension Definitions
by Barry LaFond (JIRA)
Create persistance and loading mechanism for XML-based Model Extension Definitions
----------------------------------------------------------------------------------
Key: TEIIDDES-926
URL: https://issues.jboss.org/browse/TEIIDDES-926
Project: Teiid Designer
Issue Type: Sub-task
Components: Import/Export, Modeling
Affects Versions: 7.4
Reporter: Barry LaFond
Assignee: Dan Florian
Priority: Blocker
Fix For: 7.4
Attachments: modelExtension.xsd, salesforce.mxd
The New Model Extension framework requires reading (loading) and writing XML-formatted Model Extension Definition properties.
These property definitions will replace the old "Extension Model" EMF construct.
Attached is a sample "salesforce.mxd" (Model eXtension Definition) file and a potential backing schema
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-1028) CLONE - Allow the use of pushdown functions without requiring Java programming
by Steven Hawkins (JIRA)
CLONE - Allow the use of pushdown functions without requiring Java programming
------------------------------------------------------------------------------
Key: TEIIDDES-1028
URL: https://issues.jboss.org/browse/TEIIDDES-1028
Project: Teiid Designer
Issue Type: Feature Request
Affects Versions: 7.4
Reporter: Bernd Groh
Assignee: Barry LaFond
Fix For: 7.5, 7.4.2
Currently, in order to use a database function, even if pushdown is required, it is still necessary to add the function interface to a Java class within the connector, and the connector then must be deployed to the server in order to allow for this pushdown function to be used within the Designer. This creates a lot of extra effort every time you want to make use of a new database function. Particularly, given the schema designer doesn't necessarily have access to either the connector code or the server, and then must involve other parties simply to be able to use an additional database function. It would be very beneficial to speedy schema development if that was not necessary, and if, say, the interface could be defined on the Designer side, added to the VDB, and then deployed as part of the VDB.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Updated: (TEIIDDES-1004) Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1004?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-1004:
------------------------------------
Attachment: MasterVDB.vdb
TestVPVDB.vdb
testMergeVDBs.groovy
I was able to reproduce the mergeVDB issue using adminShell, so I am attaching the VDBs and adminShell script. The virtual procedure transformation apparently is not getting updated. The attached VDBs each contain the same virtualTable and virtualProc. MasterVDB return values are both hardcoded to '5' and TestVPVDB return values are both hardcoded to '10'. Here is summary of the script steps:
1) deploy MasterVDB.vdb
2) deploy TestVPVDB.vdb
3) connect and query MasterVDB. Both the table and proc return 5 - as expected.
4) connect and query TestVPVDB. Both the table and proc return 10 - as expected.
5) Merge TestVPVDB into MasterVDB.
6) connect and query MasterVDB. Now the table returns '10' - expected. But the proc returns '5' - not expected.
> Teiid Designer Preview Feature does not refresh if a transformation is changed on a procedure
> ---------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1004
> URL: https://issues.jboss.org/browse/TEIIDDES-1004
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 7.1.1
> Reporter: Debbie Steigner
> Assignee: Ramesh Reddy
> Fix For: 7.5
>
> Attachments: MasterVDB.vdb, testMergeVDBs.groovy, TestVPVDB.vdb
>
>
> If a preview is run on a virtual procedure, then the procedure is changed and saved the preview still gives the results from the previous transformation. You have to close Developer Studio and re-open to get the correct result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months