[JBoss JIRA] (TEIIDDES-2713) UDF jar not referenced in exported dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2713?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2713:
----------------------------------------
Added https://github.com/Teiid-Designer/teiid-designer/compare/6cfba1b475f6...f... which performs a check on the VDB contents and adds warnings to the generate status to warn user not all parts of the VDB were exported.
> UDF jar not referenced in exported dynamic VDB
> ----------------------------------------------
>
> Key: TEIIDDES-2713
> URL: https://issues.jboss.org/browse/TEIIDDES-2713
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Paul Richardson
> Fix For: 9.2.1, 10.0.2
>
>
> When exporting a VDB with a User Defined Function, the information about the UDF jar is not present in the resulting dynamic VDB file.
> With regular VDB archives, the UDF jar is added to the lib/ directory within the archive and is referenced like so in META-INF/vdb.xml:
> {code:xml}
> <entry path="/lib/MyTestUdf-1.0-SNAPSHOT.jar">
> <property name="checksum" value="2689317444"/>
> </entry>
> {code}
> This approach is not possible in case of dynamic VDB defined only as an xml file. It is, however, possible to create a module on the server with UDF jar and then reference it in the *-vdb.xml like so:
> {code:xml}
> <property name ="lib" value ="mytestudf-module"></property>
> {code}
> It is currently possible to define such property manually in the VDB editor before exporting, but Designer should be able to define one automatically, or at least warn the user when there is a UDF jar present and the lib property is not defined.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2762) REST import parameter issue - problem on java 8
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2762?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2762:
-----------------------------------
Fix Version/s: 9.0.5
10.0.1
9.2.1
> REST import parameter issue - problem on java 8
> -----------------------------------------------
>
> Key: TEIIDDES-2762
> URL: https://issues.jboss.org/browse/TEIIDDES-2762
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.5
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Priority: Blocker
> Fix For: 9.0.5, 10.0.1, 9.2.1
>
> Attachments: Screen Shot 2016-01-15 at 11.41.18.png
>
>
> I discovered this on 9.0.5, but the issue seems to be caused by Java 8, so it doesn't matter which version of TD is used.
> I tried to import data from REST ws and when I added some parameter (name of parameter is "new") I got following error:
> {code:java}
> Illegal character(s) in message header field: rest_param:new
> {code}
> This seems to be problem only with Java 8. It works with Java 7.
> Marked this as blocker, because user cannot import from REST if he wants to use some parameters during import. After some googling I found out that this could be an issue in Java not in Designer.
> Java version: 1.8.0_65, vendor: Oracle Corporation
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2199) Designer deletes materialization setting in transformation Editor
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2199?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-2199:
-------------------------------------------
Hey [~shawkins]
Designer does preserve pre/post comments but adding the space between the /* and + stores it as a normal comment and not a cache hint as is its purpose.
(Working on preserving all comments atm).
> Designer deletes materialization setting in transformation Editor
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2199
> URL: https://issues.jboss.org/browse/TEIIDDES-2199
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, Transformations
> Affects Versions: 8.3.2
> Environment: fedora 19, Red Hat Data Virtualization 6, JBDS 7.1.1.GA
> Reporter: Jason Marley
> Assignee: Paul Richardson
> Fix For: 10.0.1, 9.2.1
>
>
> In transformation editor and add caching comment /*+ cache(ttl:300000) */, if there is a space before + and the beginning of comment, upon save designer deletes the line.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2748) ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2748?page=com.atlassian.jira.plu... ]
Johnathon Lee updated TEIIDDES-2748:
------------------------------------
Fix Version/s: (was: 9.0.5)
Workaround Description: manual modelling of the web services can still be accomplished.
> ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2748
> URL: https://issues.jboss.org/browse/TEIIDDES-2748
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.3, 9.2
> Reporter: Debbie Steigner
> Assignee: Ted Jones
> Priority: Minor
> Fix For: 10.0.1, 9.2.1
>
>
> Using the ‘Import => Teiid Designer => Web Service Source >> Source and View Model (SOAP)’ import wizard I am not getting columns for either my input or output wrapers methods.
> On the Source and WSDL Operations Definitions screen, the selected WSDL does validate. All the WSDL Operatoins are visible and selected.
> On the Models Definition screen the folders are setup and the names are unique. The recommended User-specified Procedures is checked.
> On the Procedure definition screen for EVERY operation has the warning “No columns are defined for the response result set for the operation:<name of operation>
> The Schema Contents section is blank. I can easily trace the very obvious connections through the wsdl to the associated schema that defines the complex type and the individual elements that compose it for every method. The add button doesn’t work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2199) Designer deletes materialization setting in transformation Editor
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2199?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-2199.
---------------------------------------
Resolution: Won't Fix
At no point could this be changed without a similar change being enacted by Teiid.
> Designer deletes materialization setting in transformation Editor
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2199
> URL: https://issues.jboss.org/browse/TEIIDDES-2199
> Project: Teiid Designer
> Issue Type: Bug
> Components: Patch Release, Transformations
> Affects Versions: 8.3.2
> Environment: fedora 19, Red Hat Data Virtualization 6, JBDS 7.1.1.GA
> Reporter: Jason Marley
> Assignee: Paul Richardson
> Fix For: 10.0.1, 9.2.1
>
>
> In transformation editor and add caching comment /*+ cache(ttl:300000) */, if there is a space before + and the beginning of comment, upon save designer deletes the line.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2767) Illegal argument exception if explorer context menu launched prior to explorer view fully functional
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-2767:
--------------------------------------
Summary: Illegal argument exception if explorer context menu launched prior to explorer view fully functional
Key: TEIIDDES-2767
URL: https://issues.jboss.org/browse/TEIIDDES-2767
Project: Teiid Designer
Issue Type: Bug
Reporter: Barry LaFond
Assignee: Barry LaFond
Fix For: 10.0.1, 9.2.1
Re-opening a workspace with projects and larger model sets will take a little longer to launch.
Right-clicking on the explorer may throw the following because Model Explorer is adding a listener that calls fillContextMenu() on it's own. Need to check that ModelerActionService is fully added/functional.
org.eclipse.core.runtime.AssertionFailedException: null argument:Action must not be null
at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
at org.eclipse.jface.action.ContributionManager.add(ContributionManager.java:76)
at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.createRefactorMenu(ModelExplorerResourceNavigator.java:1206)
at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator.fillContextMenu(ModelExplorerResourceNavigator.java:1291)
at org.teiid.designer.ui.explorer.ModelExplorerResourceNavigator$13.menuAboutToShow(ModelExplorerResourceNavigator.java:1144)
at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:352)
at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:492)
at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:487)
at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:519)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
at org.eclipse.swt.widgets.Display.runPopups(Display.java:3841)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3399)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2705) Teiid designer does not take the overriden translator
by jie tao (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2705?page=com.atlassian.jira.plu... ]
jie tao commented on TEIIDDES-2705:
-----------------------------------
I did not see the override translator in the source binding defination panel, where I can select this translator.
Therefore, the overriden translator is in the vdb.xml, but you see that the model does not use it. I use Teiid designer 9.20
<model name="Hive13" path="/GFBIVDB/sources/Hive13.xmi">
<property name="checksum" value="880531203"/>
<property name="indexName" value="4281170462.INDEX"/>
<property name="modelUuid" value="mmuuid:cb827637-eea2-4d57-aec5-914047a56ddc"/>
<property name="modelClass" value="Relational"/>
<property name="builtIn" value="false"/>
<source name="Hive13" connection-jndi-name="java:/HadoopDB" translator-name="hive"/>
</model>
<translator name="hive-override" type="hive" description="">
<property name="supportsDirectQueryProcedure" value="true"/>
</translator>
> Teiid designer does not take the overriden translator
> -----------------------------------------------------
>
> Key: TEIIDDES-2705
> URL: https://issues.jboss.org/browse/TEIIDDES-2705
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: VDB & Execution
> Reporter: jie tao
> Priority: Optional
>
> in the VDB editor, an overriden translator can be defined, but in vdb.xml the default one is still used. No way to tell Designer to take the overriden one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (TEIIDDES-2713) UDF jar not referenced in exported dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2713?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2713:
-----------------------------------
Fix Version/s: 10.0.2
(was: 10.0.1)
> UDF jar not referenced in exported dynamic VDB
> ----------------------------------------------
>
> Key: TEIIDDES-2713
> URL: https://issues.jboss.org/browse/TEIIDDES-2713
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release, VDB & Execution
> Affects Versions: 9.0.4
> Reporter: Andrej Šmigala
> Assignee: Paul Richardson
> Fix For: 9.2.1, 10.0.2
>
>
> When exporting a VDB with a User Defined Function, the information about the UDF jar is not present in the resulting dynamic VDB file.
> With regular VDB archives, the UDF jar is added to the lib/ directory within the archive and is referenced like so in META-INF/vdb.xml:
> {code:xml}
> <entry path="/lib/MyTestUdf-1.0-SNAPSHOT.jar">
> <property name="checksum" value="2689317444"/>
> </entry>
> {code}
> This approach is not possible in case of dynamic VDB defined only as an xml file. It is, however, possible to create a module on the server with UDF jar and then reference it in the *-vdb.xml like so:
> {code:xml}
> <property name ="lib" value ="mytestudf-module"></property>
> {code}
> It is currently possible to define such property manually in the VDB editor before exporting, but Designer should be able to define one automatically, or at least warn the user when there is a UDF jar present and the lib property is not defined.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months