[JBoss JIRA] (TEIIDDES-2782) Copy paste sql to the transformation editor is not parsable
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2782?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2782:
-----------------------------------
Attachment: endOfFile.mkv
> Copy paste sql to the transformation editor is not parsable
> -----------------------------------------------------------
>
> Key: TEIIDDES-2782
> URL: https://issues.jboss.org/browse/TEIIDDES-2782
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors, Transformations
> Affects Versions: 10.0.1
> Environment: Windows 10 Pro N
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: endOfFile.mkv, XmlStagingProject.zip
>
>
> When I copy a sql query from any source (notepad, web browser ...) and paste it to the transformation editor show me that "The query is not parsable.Error in parsing of sql - null ."
> When I deleted all newlines from sql query or I wrote it myself to the editor, sql query was validated.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 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.3
(was: 10.0.2)
> 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: Barry LaFond
> Fix For: 10.0.3
>
>
> 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)
8 years, 2 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... ]
Work on TEIIDDES-2713 stopped by Barry LaFond.
----------------------------------------------
> 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: Barry LaFond
> Fix For: 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)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2398.
------------------------------------
Resolution: Won't Fix
Mapping framework fairly complex to build. Teiid Connection Importer is work-around and Komodo framework TEIIDTOOLS-11 will provide future mapping
> Inconsistent column datatypes when importing
> --------------------------------------------
>
> Key: TEIIDDES-2398
> URL: https://issues.jboss.org/browse/TEIIDDES-2398
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Modeling
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Fix For: Future
>
> Attachments: datatypes.png, MySQL_BQT_DDL.ddl
>
>
> There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer.
> Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2920) Reference/document translator that allows overriding all supports
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2920?page=com.atlassian.jira.plu... ]
Steven Hawkins commented on TEIIDDES-2920:
------------------------------------------
One consideration from a ui perspective is that the translator by itself will not advertise proper default settings for capabilities - as those would coming from the delegate.
> Reference/document translator that allows overriding all supports
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2920
> URL: https://issues.jboss.org/browse/TEIIDDES-2920
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Steven Hawkins
> Labels: CR1
> Fix For: 11.1
>
>
> As a competitive feature, we have provided a built-in mechanism that allows overriding any translator capability. This would only be used in situations to workaround an unexpected issue. It would be good to have this referenced in some way in the designer docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2920) Reference/document translator that allows overriding all supports
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2920?page=com.atlassian.jira.plu... ]
Steven Hawkins reassigned TEIIDDES-2920:
----------------------------------------
Description: As a competitive feature, we have provided a built-in mechanism that allows overriding any translator capability. This would only be used in situations to workaround an unexpected issue. It would be good to have this referenced in some way in the designer docs. (was: To assist in toggling specific capabilities without a patch, we should provide a built-in delegating translator that can selective toggle capabilities.)
Summary: Reference/document translator that allows overriding all supports (was: Add a built-in delegating translator that allows overriding all supports)
Assignee: (was: Ramesh Reddy)
> Reference/document translator that allows overriding all supports
> -----------------------------------------------------------------
>
> Key: TEIIDDES-2920
> URL: https://issues.jboss.org/browse/TEIIDDES-2920
> Project: Teiid Designer
> Issue Type: Task
> Reporter: Steven Hawkins
> Labels: CR1
>
> As a competitive feature, we have provided a built-in mechanism that allows overriding any translator capability. This would only be used in situations to workaround an unexpected issue. It would be good to have this referenced in some way in the designer docs.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 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: (was: 9.2.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: Barry LaFond
> Fix For: 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)
8 years, 2 months