January 2020 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIIDSB-166) Update Teiid Spring Boot Example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-166?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIIDSB-166: --------------------------------- Original Estimate: 0 minutes Story Points: 0.5 > Update Teiid Spring Boot Example > -------------------------------- > > Key: TEIIDSB-166 > URL: https://issues.redhat.com/browse/TEIIDSB-166 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.1 > > Original Estimate: 0 minutes > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Update the UserGuide with working example -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-166) Update Teiid Spring Boot Example

by Ramesh Reddy (Jira)

[ https://issues.redhat.com/browse/TEIIDSB-166?page=com.atlassian.jira.plug... ] Ramesh Reddy resolved TEIIDSB-166. ---------------------------------- Resolution: Done > Update Teiid Spring Boot Example > -------------------------------- > > Key: TEIIDSB-166 > URL: https://issues.redhat.com/browse/TEIIDSB-166 > Project: Teiid Spring Boot > Issue Type: Task > Components: documentation > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Priority: Major > Fix For: 1.3.1 > > > Update the UserGuide with working example -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIIDSB-166) Update Teiid Spring Boot Example

by Ramesh Reddy (Jira)

Ramesh Reddy created TEIIDSB-166: ------------------------------------ Summary: Update Teiid Spring Boot Example Key: TEIIDSB-166 URL: https://issues.redhat.com/browse/TEIIDSB-166 Project: Teiid Spring Boot Issue Type: Task Components: documentation Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 1.3.1 Update the UserGuide with working example -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5880) Oreva fails when built with jdk11

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5880?page=com.atlassian.jira.plugi... ] Van Halbert resolved TEIID-5880. -------------------------------- Resolution: Done > Oreva fails when built with jdk11 > --------------------------------- > > Key: TEIID-5880 > URL: https://issues.redhat.com/browse/TEIID-5880 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Priority: Major > > Oreva, master branch, fails when built with jdk11. > Error: > {code} > ERROR] /home/vhalbert/RedHat/github/product_branches/teiidrepos/oreva/odata-core/src/main/java/org/odata4j/stax2/staximpl/StaxXMLWriter2.java:[74,36] no suitable method found for createStartElement(javax.xml.namespace.QName,<nulltype>,java.util.Iterator<capture#2 of ?>) > method javax.xml.stream.XMLEventFactory.createStartElement(javax.xml.namespace.QName,java.util.Iterator<? extends javax.xml.stream.events.Attribute>,java.util.Iterator<? extends javax.xml.stream.events.Namespace>) is not applicable > (argument mismatch; java.util.Iterator<capture#2 of ?> cannot be converted to java.util.Iterator<? extends javax.xml.stream.events.Namespace>) > method javax.xml.stream.XMLEventFactory.createStartElement(java.lang.String,java.lang.String,java.lang.String) is not applicable > (argument mismatch; javax.xml.namespace.QName cannot be converted to java.lang.String) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5889) Add release profile to oreva

by Van Halbert (Jira)

[ https://issues.redhat.com/browse/TEIID-5889?page=com.atlassian.jira.plugi... ] Van Halbert resolved TEIID-5889. -------------------------------- Resolution: Done > Add release profile to oreva > ---------------------------- > > Key: TEIID-5889 > URL: https://issues.redhat.com/browse/TEIID-5889 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Original Estimate: 4 minutes > Remaining Estimate: 4 minutes > > The oreva pom.xml needs to have a release profile added so that the tests can be excluded from the release build. test-integration module will only be executed as part of the default profile. > This will need to be applied to the 1.0.x and 1.1.x branches as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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?focusedWorklogId=12450000&pag... ] Steven Hawkins logged work on TEIID-5888: ----------------------------------------- Author: Steven Hawkins Created on: 30/Jan/20 1:16 PM Start Date: 30/Jan/20 1:16 PM Worklog Time Spent: 6 hours Work Description: The scope expanded to two issues and a capability change. Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 4 hours) Time Spent: 6 hours Worklog Id: (was: 12450000) > 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, 13.0.2 > > Original Estimate: 4 hours > Time Spent: 6 hours > Remaining Estimate: 0 minutes > > 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, 10 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 updated TEIID-5888: ---------------------------------- Original Estimate: 4 hours Remaining Estimate: 4 hours > 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, 13.0.2 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 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, 10 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 resolved TEIID-5894. ----------------------------------- Resolution: Done The issue is that special handling was not added into the JDBCURL for QUERYTIMEOUT. The change makes sure that all properties are added. > 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, 10 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: ---------------------------------- Original Estimate: 1 hour, 30 minutes Remaining Estimate: 1 hour, 30 minutes > 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 > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > 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, 10 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?focusedWorklogId=12449999&pag... ] Steven Hawkins logged work on TEIID-5894: ----------------------------------------- Author: Steven Hawkins Created on: 30/Jan/20 1:15 PM Start Date: 30/Jan/20 1:15 PM Worklog Time Spent: 1 hour, 30 minutes Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 1 hour, 30 minutes) Time Spent: 1 hour, 30 minutes Worklog Id: (was: 12449999) > 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 > > Original Estimate: 1 hour, 30 minutes > Time Spent: 1 hour, 30 minutes > Remaining Estimate: 0 minutes > > 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, 10 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