December 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5545) Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5545?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5545: ---------------------------------- Fix Version/s: 12.1 (was: 12.0) > Odata V4 Batch processing does not work as teiid/olingo rejects "Accept: multipart/mixed" request header > -------------------------------------------------------------------------------------------------------- > > Key: TEIID-5545 > URL: https://issues.jboss.org/browse/TEIID-5545 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 11.2 > Reporter: Christoph John > Assignee: Ramesh Reddy > Priority: Critical > Fix For: 12.1 > > > When using Teiid together with SAPUI5/OpenUI5 Odata V4 model, batch processing does not work as Teiid rejects the "Accept: multipart/mixed" header. The issue has been described in > https://developer.jboss.org/message/986421#986421 > It has been stated that Olingo in general does support multipart messages and it was recommended to remove the header from the request. > https://developer.jboss.org/message/986425#986425 > Unfortunately this seems to be not easily possible when using the SAPUI5 framework. I addressed the issue in the SAPUI5 forum under the following issue: > https://github.com/SAP/openui5/issues/2288 > The result of this discussion was, that the header is valid for the send content. As I am no expert in the topic I do not really have an opinion on that. However, > https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > suggests that the header is required. So I am not sure if it is correct or an error to reject the message. However, if Olingo can process the content, it would be great to have a fix for the accept header, or alternatively a config option to enable handling of the Accept header in a way that Olingo processes these data. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5351) Upgrade to WildFly 14

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5351?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5351. ----------------------------------- Resolution: Done Tested the console as well and made appropriate doc updates. > Upgrade to WildFly 14 > --------------------- > > Key: TEIID-5351 > URL: https://issues.jboss.org/browse/TEIID-5351 > Project: Teiid > Issue Type: Task > Components: Server > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0 > > > We should move to WildFly 13, which should be at GA by the Teiid 11.0 release. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5564) Batch removed during large temp table load

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5564?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5564: ---------------------------------- Fix Version/s: 11.1.2 > Batch removed during large temp table load > ------------------------------------------ > > Key: TEIID-5564 > URL: https://issues.jboss.org/browse/TEIID-5564 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.1.2, 12.0, 11.2.2 > > > For a sufficiently large temp operation, such as a merge over 2.5 million rows, you can see: > java.lang.AssertionError: Batch not found in storage 58804 > at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.SPage.getValues(SPage.java:240) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.SPage.search(SPage.java:139) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.STree.find(STree.java:249) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.STree.remove(STree.java:429) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable.deleteTuple(TempTable.java:802) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.undo(TempTable.java:159) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > Which occurs during undo/rollback of an operation and masks the underlying exception. The actual error will typically be the same as TEIID-5439, the proactive removal of the managed batches once a space limit has been reached. > This did not occur after the TEIID-5439 fix upstream, but it appears it could have still occurred - and did occur on 8.12.x. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5564) Batch removed during large temp table load

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5564?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5564. ----------------------------------- Resolution: Done Updated the batchmanager to throw only component and not unchecked exceptions. > Batch removed during large temp table load > ------------------------------------------ > > Key: TEIID-5564 > URL: https://issues.jboss.org/browse/TEIID-5564 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.0, 11.2.2 > > > For a sufficiently large temp operation, such as a merge over 2.5 million rows, you can see: > java.lang.AssertionError: Batch not found in storage 58804 > at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:382) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.SPage.getValues(SPage.java:240) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.SPage.search(SPage.java:139) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.STree.find(STree.java:249) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.common.buffer.STree.remove(STree.java:429) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable.deleteTuple(TempTable.java:802) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > at org.teiid.query.tempdata.TempTable$InsertUpdateProcessor.undo(TempTable.java:159) [teiid-engine-8.12.16.6_4-redhat-64-2.jar:8.12.16.6_4-redhat-64-2] > Which occurs during undo/rollback of an operation and masks the underlying exception. The actual error will typically be the same as TEIID-5439, the proactive removal of the managed batches once a space limit has been reached. > This did not occur after the TEIID-5439 fix upstream, but it appears it could have still occurred - and did occur on 8.12.x. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5562) Move the Teiid BOM from project-integration-bom into the Teiid project

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5562?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5562: --------------------------------------- I merged the pull request, with the test dependencies moved back and some consolidation between the bom and our root pom. There is more that could be done to better organize the root pom vs. the build integration pom, but that's not really necessary at this time. [~van.halbert] is there anything else you want to do along these lines for 12.0? > Move the Teiid BOM from project-integration-bom into the Teiid project > ---------------------------------------------------------------------- > > Key: TEIID-5562 > URL: https://issues.jboss.org/browse/TEIID-5562 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > The project-integration-bom project usefulness never materialized, so the teiid bom will be moved back into the Teiid project to simplify dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5562) Move the Teiid BOM from project-integration-bom into the Teiid project

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5562?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5562: ---------------------------------- Fix Version/s: 12.0 > Move the Teiid BOM from project-integration-bom into the Teiid project > ---------------------------------------------------------------------- > > Key: TEIID-5562 > URL: https://issues.jboss.org/browse/TEIID-5562 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > Fix For: 12.0 > > > The project-integration-bom project usefulness never materialized, so the teiid bom will be moved back into the Teiid project to simplify dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5369) enableDependentJoins for Redshift translator

by Johnathon Lee (Jira)

[ https://issues.jboss.org/browse/TEIID-5369?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5369: --------------------------------- Fix Version/s: 8.12.17.6_4 > enableDependentJoins for Redshift translator > -------------------------------------------- > > Key: TEIID-5369 > URL: https://issues.jboss.org/browse/TEIID-5369 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Chandra Akkinepalli > Assignee: Steven Hawkins > Priority: Major > Fix For: 11.0, 10.3.2, 8.12.17.6_4 > > > When using Translator overwrite property enableDependentJoins with Redshift translator, we got the following error. > Caused by: java.sql.SQLException: [Amazon](500310) Invalid operation: CREATE TEMP TABLE ON COMMIT is not supported; at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(ErrorResponse.java:1830) ... 30 lines omitted ... at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: CREATE TEMP TABLE ON COMMIT is not supported; ... 32 more -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5565) Drop client and other support for 1.6

by Steven Hawkins (Jira)

Steven Hawkins created TEIID-5565: ------------------------------------- Summary: Drop client and other support for 1.6 Key: TEIID-5565 URL: https://issues.jboss.org/browse/TEIID-5565 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 13.0 Compatibility of the client/core code will need to be moved up to Java 8, while the project as a whole can move forward to Java 11. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5562) Move the Teiid BOM from project-integration-bom into the Teiid project

by Van Halbert (Jira)

[ https://issues.jboss.org/browse/TEIID-5562?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5562: ------------------------------- Git Pull Request: https://github.com/teiid/teiid/pull/1108 > Move the Teiid BOM from project-integration-bom into the Teiid project > ---------------------------------------------------------------------- > > Key: TEIID-5562 > URL: https://issues.jboss.org/browse/TEIID-5562 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Affects Versions: 12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Major > > The project-integration-bom project usefulness never materialized, so the teiid bom will be moved back into the Teiid project to simplify dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5557) Restrict imports to a single schema

by Steven Hawkins (Jira)

[ https://issues.jboss.org/browse/TEIID-5557?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5557: --------------------------------------- For 12.0 added info messages to start with about the potential default change for useFullSchemaName and the recommendation to import from only a single schema. > Restrict imports to a single schema > ----------------------------------- > > Key: TEIID-5557 > URL: https://issues.jboss.org/browse/TEIID-5557 > Project: Teiid > Issue Type: Quality Risk > Components: Connector API > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Major > Fix For: 12.x, 13.0 > > > To better align with SQL/MED and to simplify legacy import properties it would be best to restrict foreign imports to a single schema. This will remove quite a bit of confusion around potential duplicate object names. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2018