[JBoss JIRA] (TEIIDDES-2391) IllegalArgumentException when trying to edit expression using Expression Builder
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2391?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2391.
------------------------------------
Resolution: Done
The FunctionForm constructor was performing a toUpper() on the category, but the UI and FunctionLibrary was using the unaltered category. Fix was to remove the toUpper() to keep all things constent.
committed to master, 9.0.x and 8.6.1
> IllegalArgumentException when trying to edit expression using Expression Builder
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2391
> URL: https://issues.jboss.org/browse/TEIIDDES-2391
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.6
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: log
>
>
> When opening the expression builder with cursor positioned in an existing expression (other than a simple constant or column reference), the following error is logged multiple times:
> {quote}java.lang.IllegalArgumentException: Expected argument to be non-null but got null{quote}
> (relevant part of log attached)
> After that, the expression builder behaves in unpredictable way (values do not update etc)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2391) IllegalArgumentException when trying to edit expression using Expression Builder
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2391?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2391:
-----------------------------------
Fix Version/s: 8.6.1
9.0.1
9.0
Assignee: Barry LaFond
Affects Version/s: 8.6
> IllegalArgumentException when trying to edit expression using Expression Builder
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-2391
> URL: https://issues.jboss.org/browse/TEIIDDES-2391
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.6
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: log
>
>
> When opening the expression builder with cursor positioned in an existing expression (other than a simple constant or column reference), the following error is logged multiple times:
> {quote}java.lang.IllegalArgumentException: Expected argument to be non-null but got null{quote}
> (relevant part of log attached)
> After that, the expression builder behaves in unpredictable way (values do not update etc)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2393) Old values used for new criteria in Criteria Builder
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2393:
----------------------------------------
Summary: Old values used for new criteria in Criteria Builder
Key: TEIIDDES-2393
URL: https://issues.jboss.org/browse/TEIIDDES-2393
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 8.3.4, 9.0.1
Reporter: Andrej Šmigala
Attachments: project.zip
In the Criteria Builder, creating new function criteria when there already is a function expression in the criteria causes the old expression to be reused.
This together with TEIIDDES-2391 makes it impossible to reliably use the Criteria Builder to create criteria with two or more function expressions.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2392) Don't allow override name to be the same name as existing translator name
by Van Halbert (JIRA)
Van Halbert created TEIIDDES-2392:
-------------------------------------
Summary: Don't allow override name to be the same name as existing translator name
Key: TEIIDDES-2392
URL: https://issues.jboss.org/browse/TEIIDDES-2392
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 8.6.1
Reporter: Van Halbert
When creating a translator override, the name of the override should not be able to be set to the name of an existing translator (or translator override).
In this case, the translator override was set to "teradata".
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months