January 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5894) QueryTimeout JDBC connection property is not enforced

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5894?page=com.atlassian.jira.plugi... ] Work on TEIID-5894 started by Steven Hawkins. --------------------------------------------- > QueryTimeout JDBC connection property is not enforced > ----------------------------------------------------- > > Key: TEIID-5894 > URL: https://issues.redhat.com/browse/TEIID-5894 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 13.0.2 > > > We have observed that when QueryTimeout connection string property is being set , it is not being enforced and request is terminated even after the set time limit is exceeded. > Can you please look into it? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5894) QueryTimeout JDBC connection property is not enforced

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5894?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5894: ---------------------------------- Story Points: 0.5 Sprint: DV Sprint 58 > QueryTimeout JDBC connection property is not enforced > ----------------------------------------------------- > > Key: TEIID-5894 > URL: https://issues.redhat.com/browse/TEIID-5894 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1, 13.0.2 > > > We have observed that when QueryTimeout connection string property is being set , it is not being enforced and request is terminated even after the set time limit is exceeded. > Can you please look into it? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5892?page=com.atlassian.jira.plugi... ] Steven Hawkins updated TEIID-5892: ---------------------------------- Fix Version/s: 13.1 > Incorrect issue number/link on downloads page > --------------------------------------------- > > Key: TEIID-5892 > URL: https://issues.redhat.com/browse/TEIID-5892 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Scott Seaton > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 13.1 > > > On this page: > https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ > This seems to reference and link to the wrong issue number: > TEIID-5492 added support for an EXPLAIN statement. > Presumably should be this: > https://issues.redhat.com/browse/TEIID-5740 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5894) QueryTimeout JDBC connection property is not enforced

by Chandra Akkinepalli (Jira)

Chandra Akkinepalli created TEIID-5894: ------------------------------------------ Summary: QueryTimeout JDBC connection property is not enforced Key: TEIID-5894 URL: https://issues.redhat.com/browse/TEIID-5894 Project: Teiid Issue Type: Bug Reporter: Chandra Akkinepalli Assignee: Steven Hawkins We have observed that when QueryTimeout connection string property is being set , it is not being enforced and request is terminated even after the set time limit is exceeded. Can you please look into it? -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5893) Delete dv.0.1.0.clusterserviceversion.yaml from teiid-operator

by Van Halbert (Jira)

Van Halbert created TEIID-5893: ---------------------------------- Summary: Delete dv.0.1.0.clusterserviceversion.yaml from teiid-operator Key: TEIID-5893 URL: https://issues.redhat.com/browse/TEIID-5893 Project: Teiid Issue Type: Quality Risk Components: Build/Kits Reporter: Van Halbert Assignee: Steven Hawkins Can the dv.0.1.0.clusterserviceversion.yaml be removed from teiid-operator, because i believe it causes more confusion and work. It just adds another file to maintain that isn't complete for what the product is expecting. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5893) Delete dv.0.1.0.clusterserviceversion.yaml from teiid-operator

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5893?page=com.atlassian.jira.plugi... ] Van Halbert reassigned TEIID-5893: ---------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Delete dv.0.1.0.clusterserviceversion.yaml from teiid-operator > -------------------------------------------------------------- > > Key: TEIID-5893 > URL: https://issues.redhat.com/browse/TEIID-5893 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Minor > > Can the dv.0.1.0.clusterserviceversion.yaml be removed from teiid-operator, because i believe it causes more confusion and work. It just adds another file to maintain that isn't complete for what the product is expecting. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Scott Seaton (Jira)

[ https://issues.redhat.com/browse/TEIID-5892?page=com.atlassian.jira.plugi... ] Scott Seaton updated TEIID-5892: -------------------------------- Description: On this page: https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ This seems to reference and link to the wrong issue number: TEIID-5492 added support for an EXPLAIN statement. Presumably should be this: https://issues.redhat.com/browse/TEIID-5740 was: On this page: https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ This seems to reference and link to the wrong issue number: TEIID-5492 added support for an EXPLAIN statement. > Incorrect issue number/link on downloads page > --------------------------------------------- > > Key: TEIID-5892 > URL: https://issues.redhat.com/browse/TEIID-5892 > Project: Teiid > Issue Type: Bug > Components: Documentation > Reporter: Scott Seaton > Assignee: Steven Hawkins > Priority: Trivial > > On this page: > https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ > This seems to reference and link to the wrong issue number: > TEIID-5492 added support for an EXPLAIN statement. > Presumably should be this: > https://issues.redhat.com/browse/TEIID-5740 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5892) Incorrect issue number/link on downloads page

by Scott Seaton (Jira)

Scott Seaton created TEIID-5892: ----------------------------------- Summary: Incorrect issue number/link on downloads page Key: TEIID-5892 URL: https://issues.redhat.com/browse/TEIID-5892 Project: Teiid Issue Type: Bug Components: Documentation Reporter: Scott Seaton Assignee: Steven Hawkins On this page: https://teiid.io/teiid_runtimes/teiid_wildfly/downloads/ This seems to reference and link to the wrong issue number: TEIID-5492 added support for an EXPLAIN statement. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5888) Infinispan translator returns wrong update count in some circumstances

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5888?page=com.atlassian.jira.plugi... ] Steven Hawkins commented on TEIID-5888: --------------------------------------- It looks like some wires are getting crossed with the join logic. In the select above there is an implicit join on g3 implied which then becomes how the results are actually processed, which leads to incorrect rows. > Infinispan translator returns wrong update count in some circumstances > ---------------------------------------------------------------------- > > Key: TEIID-5888 > URL: https://issues.redhat.com/browse/TEIID-5888 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > In some nested circumstances the wrong update count is returned. For example in TestHodrodExecution the update: > UPDATE G4 SET e2 = 'two-2' WHERE e2 = 'two-two' OR e2 = 'one-one' > should return 2, but instead returns 4. This happens both prior to and after the changes for TEIID-5887. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5885) Timestamp nanosecond precision is dropped

by Steven Hawkins (Jira)

[ https://issues.redhat.com/browse/TEIID-5885?page=com.atlassian.jira.plugi... ] Steven Hawkins resolved TEIID-5885. ----------------------------------- Resolution: Done Elaborated the only millisecond precision is retained and removed limitations that are no longer valid. > Timestamp nanosecond precision is dropped > ----------------------------------------- > > Key: TEIID-5885 > URL: https://issues.redhat.com/browse/TEIID-5885 > Project: Teiid > Issue Type: Bug > Components: Infinispan > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 13.1 > > > This is probably something that can just be documented as a limitation of the hotrod data source - that it only supports millisecond precision. It is only stores timestamps in a 64 bit integer. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2020