[JBoss JIRA] (TEIID-3781) Queries are not killed even if the client sends a cancel request
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3781?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3781:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1315378|https://bugzilla.redhat.com/show_bug.cgi?id=1315378] from VERIFIED to CLOSED
> Queries are not killed even if the client sends a cancel request
> ----------------------------------------------------------------
>
> Key: TEIID-3781
> URL: https://issues.jboss.org/browse/TEIID-3781
> Project: Teiid
> Issue Type: Quality Risk
> Components: Query Engine
> Affects Versions: 7.0
> Reporter: Salvatore R
> Assignee: Steven Hawkins
> Fix For: 8.12.1, 8.13
>
>
> I have different behaviors when I try to cancel the following queries:
> {code:sql}
> SELECT COUNT(*)
> FROM
> (SELECT * FROM my.address) as x1,
> (SELECT * FROM my.address) as y1
> {code}
> and
> {code:sql}
> SELECT COUNT(*)
> FROM
> (SELECT * FROM my.address limit 10000) as x1,
> (SELECT * FROM my.address limit 10000) as y1
> {code}
> where "my.address" is a table with around 20000 rows in MySQL.
> The first query is immediately cancelled but the second one continues to run until the end and it is never killed.
> Looking at the generated plans, the main difference is that the first query is fully pushed down to MySQL while the second one is not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3929:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1301527|https://bugzilla.redhat.com/show_bug.cgi?id=1301527] from VERIFIED to CLOSED
> Accumulo does not return null values
> ------------------------------------
>
> Key: TEIID-3929
> URL: https://issues.jboss.org/browse/TEIID-3929
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Ramesh Reddy
> Fix For: 9.0, 8.12.5
>
>
> Accumulo doesn't return null values when a whole 'column' is being selected.
> For a command in accumulo shell like:
> {code:plain}
> scan -c name:BYTENUM
> {code}
> Accumulo returns only non-empty values, this is expected behaviour.
> Equivalent query in Teiid would be:
> {code:sql}
> SELECT ByteNum FROM SmallA
> {code}
> Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3922) Accumulo translator needs defined dependency to "org.jboss.teiid" module
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3922?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3922:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1301065|https://bugzilla.redhat.com/show_bug.cgi?id=1301065] from VERIFIED to CLOSED
> Accumulo translator needs defined dependency to "org.jboss.teiid" module
> ------------------------------------------------------------------------
>
> Key: TEIID-3922
> URL: https://issues.jboss.org/browse/TEIID-3922
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.12.3
> Reporter: Jan Stastny
> Assignee: Jan Stastny
> Fix For: 8.13, 8.12.5
>
>
> When using Accumulo translator to query an accumulo instance, following exception appears, when comparing on a column.
> {code}
> Caused by: java.lang.ClassNotFoundException: org.teiid.api.exception.query.ExpressionEvaluationException
> {code}
> Example query:
> {code:sql}
> SELECT * FROM MyTable WHERE MyColumn='string';
> {code}
> The reason is, that the mentioned class ExpressionEvaluationException is placed in module "org.jboss.teiid", but this module is not set as dependency in resulting "org.jboss.teiid.translator.accumulo" module.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (TEIID-3022) refine removed vdb handling
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3022?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-3022:
------------------------------------------------
Filip Elias <felias(a)redhat.com> changed the Status of [bug 1291719|https://bugzilla.redhat.com/show_bug.cgi?id=1291719] from VERIFIED to CLOSED
> refine removed vdb handling
> ---------------------------
>
> Key: TEIID-3022
> URL: https://issues.jboss.org/browse/TEIID-3022
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Affects Versions: 8.1
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8
>
>
> With TEIID-2105 the server will reject requests against a non-active vdb, which includes a removed vdb. This is against the original intent of allowing for lazy cleanup. We should either have a vdb remove proactively terminate all sessions and fully cleanup or we should reinstate the lazy logic. At this point it probably makes the most sense to go the first route as there is other logic (materialization management for one) now checking the vdb state and assuming that removal will invalidate the vdb.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months