[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3573:
---------------------------------------
> I'm thinking, as a workaround for now, turn off support of IS NULL and ISNOTNULL in the translator and let Teiid handle it.
Sounds fine.
So then until that bug and/or three value logic is addressed, then user query containing something like intnum<>1 could still return invalid results. That implies we may need to turn negation support entirely for now.
> Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values
> ----------------------------------------------------------------------------
>
> Key: TEIID-3573
> URL: https://issues.jboss.org/browse/TEIID-3573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Filip Elias
> Assignee: Van Halbert
>
> Operator '<>' returns true for NULL <> 1
> Example:
> {code}
> select intKey,intNum from smallA where intNum<>1
> {code}
> It returns also rows which have NULL in column intNum
> I believe that NULL <> 1 is not true in SQL.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-3573) Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-3573?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-3573:
------------------------------------
Unfortunately, this maybe harder to fix, as I've logged a bug with JDG (https://bugzilla.redhat.com/show_bug.cgi?id=1247191) regarding an issue with using IS NULL and IS NOT NULL with numeric columns. So adding IS NOT NULL when intNum <> 1 is specified will not work at this time.
I'm thinking, as a workaround for now, turn off support of IS NULL and ISNOTNULL in the translator and let Teiid handle it. So that its consistent across all data types. Otherwise, mix-and-matching support for IS NULL and IS NOT NULL will be confusing.
> Infinispan-dsl-cache translator: Operator <> incorrectly handles NULL values
> ----------------------------------------------------------------------------
>
> Key: TEIID-3573
> URL: https://issues.jboss.org/browse/TEIID-3573
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.7.1
> Reporter: Filip Elias
> Assignee: Van Halbert
>
> Operator '<>' returns true for NULL <> 1
> Example:
> {code}
> select intKey,intNum from smallA where intNum<>1
> {code}
> It returns also rows which have NULL in column intNum
> I believe that NULL <> 1 is not true in SQL.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-3591) Report user query CPU time
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-3591:
-----------------------------------
Summary: Report user query CPU time
Key: TEIID-3591
URL: https://issues.jboss.org/browse/TEIID-3591
Project: Teiid
Issue Type: Enhancement
Components: Query Engine
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Just like TEIID-2813 it would useful to be useful to report CPU time for user query overall. This can help determine load on CPU got given user query vs wait time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-2813) Report translator CPU time
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2813:
---------------------------------------
> If DB logging is ASYNC it hopefully is negligible to account or remove from calculations.
I don't mean in the calculation, I mean it would need another column.
> Do you want me to add another request for User queries? IMO, we can ignore the serial execution part or noted as such any docs.
Yes, let's open another issue for that.
> Report translator CPU time
> --------------------------
>
> Key: TEIID-2813
> URL: https://issues.jboss.org/browse/TEIID-2813
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> The COMMAND_LOG ought to report the CPU time accumulated by the translator for performance tuning purposes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months
[JBoss JIRA] (TEIID-2813) Report translator CPU time
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2813?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2813:
-------------------------------------
If DB logging is ASYNC it hopefully is negligible to account or remove from calculations.
Do you want me to add another request for User queries? IMO, we can ignore the serial execution part or noted as such any docs.
> Report translator CPU time
> --------------------------
>
> Key: TEIID-2813
> URL: https://issues.jboss.org/browse/TEIID-2813
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Mark Addleman
> Assignee: Steven Hawkins
> Fix For: 8.12
>
>
> The COMMAND_LOG ought to report the CPU time accumulated by the translator for performance tuning purposes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 11 months