[JBoss JIRA] (TEIID-3135) Result of query depends on Locale
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-3135?page=com.atlassian.jira.plugin... ]
Juraj Duráni commented on TEIID-3135:
-------------------------------------
Same query has no problem, if underlying source is file (e.g. *.xlsx).
> Result of query depends on Locale
> ---------------------------------
>
> Key: TEIID-3135
> URL: https://issues.jboss.org/browse/TEIID-3135
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Environment: OS: fedora 20
> arch: x86_64
> java: sun 1.7, openjdk 1.7
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Description: Some kind of queries ends with SQL syntax error (or incorrect result) because of real numbers are translated to locale-specific-string (e.g. -24 => -24,0 for sk_SK locale).
> Testing environment:
> a) Locale: sk_SK (Slovakia), cs_CZ(Czech)
> b) OS: fedora 20
> c) arch: x86_64
> d) java: sun 1.7, openJDK_1.7
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3135) Result of query depends on Locale
by Juraj Duráni (JIRA)
Juraj Duráni created TEIID-3135:
-----------------------------------
Summary: Result of query depends on Locale
Key: TEIID-3135
URL: https://issues.jboss.org/browse/TEIID-3135
Project: Teiid
Issue Type: Bug
Affects Versions: 8.7
Environment: OS: fedora 20
arch: x86_64
java: sun 1.7, openjdk 1.7
Reporter: Juraj Duráni
Assignee: Steven Hawkins
Fix For: 8.7.1
Description: Some kind of queries ends with SQL syntax error (or incorrect result) because of real numbers are translated to locale-specific-string (e.g. -24 => -24,0 for sk_SK locale).
Testing environment:
a) Locale: sk_SK (Slovakia), cs_CZ(Czech)
b) OS: fedora 20
c) arch: x86_64
d) java: sun 1.7, openJDK_1.7
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3135) Result of query depends on Locale
by Juraj Duráni (JIRA)
[ https://issues.jboss.org/browse/TEIID-3135?page=com.atlassian.jira.plugin... ]
Juraj Duráni updated TEIID-3135:
--------------------------------
Fix Version/s: (was: 8.7.1)
> Result of query depends on Locale
> ---------------------------------
>
> Key: TEIID-3135
> URL: https://issues.jboss.org/browse/TEIID-3135
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Environment: OS: fedora 20
> arch: x86_64
> java: sun 1.7, openjdk 1.7
> Reporter: Juraj Duráni
> Assignee: Steven Hawkins
>
> Description: Some kind of queries ends with SQL syntax error (or incorrect result) because of real numbers are translated to locale-specific-string (e.g. -24 => -24,0 for sk_SK locale).
> Testing environment:
> a) Locale: sk_SK (Slovakia), cs_CZ(Czech)
> b) OS: fedora 20
> c) arch: x86_64
> d) java: sun 1.7, openJDK_1.7
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3098) allow pushdown functions to be used by designer import
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3098?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3098:
---------------------------------------
I forget that as part of TEIID-2875 the import property importer.importPushdownFunctions was added to put the pushdown functions into the imported schema. This is not exposed to designer as the other import properties have been as it is handled in the NativeMetadataRepository and not on the MetadataProcessor. So this issue is mostly done already. The only other part that is missing is ensuring that that the functions can be used without ambiguity errors.
> allow pushdown functions to be used by designer import
> ------------------------------------------------------
>
> Key: TEIID-3098
> URL: https://issues.jboss.org/browse/TEIID-3098
> Project: Teiid
> Issue Type: Enhancement
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> allow pushdown functions to be schema scoped or some other mechanism for the purpose of designer metadata import. If schema scoped, this will require supporting logic that such functions when imported for multiple sources will not be seen as duplicates.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3129) Limit is not added with multiple nulls in select on outer query to an inline view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3129?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3129.
-----------------------------------
Fix Version/s: 8.9
Resolution: Done
Updated the logic dealing with distinct optimization with another check in rule collapse source.
> Limit is not added with multiple nulls in select on outer query to an inline view
> ---------------------------------------------------------------------------------
>
> Key: TEIID-3129
> URL: https://issues.jboss.org/browse/TEIID-3129
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Sanjeev Gour
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> When a query does multiple null selects in the in the outer query to an inline view and you only have a DISTINCT constant selected from the view definition, a limit 1 is expected to be applied to the inline view query which does not happen. Here is the sample query-
> SELECT DISTINCT c1, null as c2, null as c3 FROM(
> SELECT c1, c2 FROM (
> SELECT 'const_col_1' as c1, ID as c2 FROM FIRST_SCHEMA.FIRST_TABLE
> UNION ALL
> SELECT 'const_col_2' as c1, ID as c2 FROM SECOND_SCHEMA.SECOND_TABLE
> ) as v
> ) as v1
> The query will contain queries to the inline view without a limit like the following-
> SELECT 'const_col_1' FROM h2extended.TEST.FIRST_SCHEMA.FIRST_TABLE AS g_0 -------------------LIMIT 1 is not applied here
> Full query plan and the detail are capture in this discussion-
> https://developer.jboss.org/thread/248787
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3129) Limit is not added with multiple nulls in select on outer query to an inline view
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3129?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3129:
----------------------------------
Issue Type: Enhancement (was: Bug)
> Limit is not added with multiple nulls in select on outer query to an inline view
> ---------------------------------------------------------------------------------
>
> Key: TEIID-3129
> URL: https://issues.jboss.org/browse/TEIID-3129
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Affects Versions: 8.9
> Reporter: Sanjeev Gour
> Assignee: Steven Hawkins
>
> When a query does multiple null selects in the in the outer query to an inline view and you only have a DISTINCT constant selected from the view definition, a limit 1 is expected to be applied to the inline view query which does not happen. Here is the sample query-
> SELECT DISTINCT c1, null as c2, null as c3 FROM(
> SELECT c1, c2 FROM (
> SELECT 'const_col_1' as c1, ID as c2 FROM FIRST_SCHEMA.FIRST_TABLE
> UNION ALL
> SELECT 'const_col_2' as c1, ID as c2 FROM SECOND_SCHEMA.SECOND_TABLE
> ) as v
> ) as v1
> The query will contain queries to the inline view without a limit like the following-
> SELECT 'const_col_1' FROM h2extended.TEST.FIRST_SCHEMA.FIRST_TABLE AS g_0 -------------------LIMIT 1 is not applied here
> Full query plan and the detail are capture in this discussion-
> https://developer.jboss.org/thread/248787
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months
[JBoss JIRA] (TEIID-3132) Upgrade Groovy version
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3132?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3132:
---------------------------------------
That's not quite the situation. We are on a very old version of groovy. The platform is on a newer 2.0.x and the pull request is for what is probably the latest. So it's not so much that an upgrade is prohibited but about what version to move to.
> Upgrade Groovy version
> ----------------------
>
> Key: TEIID-3132
> URL: https://issues.jboss.org/browse/TEIID-3132
> Project: Teiid
> Issue Type: Component Upgrade
> Components: AdminApi
> Affects Versions: 8.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
>
> Upgrade groovy for admin shell to a later version.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 3 months