August 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5023) Amazon S3 translator contains java 1.8 feature for Base64

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5023?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-5023: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Amazon S3 translator contains java 1.8 feature for Base64 > --------------------------------------------------------- > > Key: TEIID-5023 > URL: https://issues.jboss.org/browse/TEIID-5023 > Project: Teiid > Issue Type: Task > Components: Misc. Connectors > Affects Versions: 8.12.x-6.4 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > The amazon s3 translator is using the java.util.Base64 java 1.8 feature. Changing it to use the teiid util Base64. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5022) Turn off error messages from OData/SOAP responses

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5022?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-5022: ------------------------------------- Component/s: OData Assignee: (was: Steven Hawkins) Let's get more feedback based upon the last comment before considering this further. > Turn off error messages from OData/SOAP responses > ------------------------------------------------- > > Key: TEIID-5022 > URL: https://issues.jboss.org/browse/TEIID-5022 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steve Tran > Priority: Optional > > There was a request to include the ability to turn off the error messages returned to the client when a bad request was made. For example, if you had a typo in your table, in the request URL, you would get a message that says "Entity does not exist". Or, if you passed in a String instead of a number, you'd get a message about expecting a Decimal but got String. > The client would like to hide these details so that a generic error message is returned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5021) Latest openjdk does not include anon cipher suites

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5021?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5021. ----------------------------------- Fix Version/s: 10.0 9.2.6 9.3.3 Resolution: Done Since the documentation already mentions that the cipher suite may not be available, the test will simply exit if the cipher suite does not exist. This change was added to each of the active branches to simplify releases. > Latest openjdk does not include anon cipher suites > -------------------------------------------------- > > Key: TEIID-5021 > URL: https://issues.jboss.org/browse/TEIID-5021 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Driver > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > Running against OpenJDK 1.8.0.141 testAnonSSLConnect fails because the anon cipher suite is not available. I could not determine yet if this is expected or a regression. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5016) Exploit left outer join associativity prior to join planning

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5016?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5016. ----------------------------------- Resolution: Done Updated the logic to perform tree manipulations prior to join planning that are more conducive to our optimizations. We may need to consider putting in checks for the preserve hint, but for now that was left out as these are narrow changes to the join structure. > Exploit left outer join associativity prior to join planning > ------------------------------------------------------------ > > Key: TEIID-5016 > URL: https://issues.jboss.org/browse/TEIID-5016 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0 > > > Building upon TEIID-3652 there are circumstances where nested left outer joins can have be converted to an inner join prior to join planning. They can be converted back to a left outer join by TEIID-3652 if needed for pushdown after join planning. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5017) More aggressively use enhanced join sorted index to prevent buffering

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5017?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5017. ----------------------------------- Fix Version/s: 9.3.3 Resolution: Done Updated the logic to more aggressively build/use the index. This could be further refined to skip the intermediate buffering before building the index. > More aggressively use enhanced join sorted index to prevent buffering > ---------------------------------------------------------------------- > > Key: TEIID-5017 > URL: https://issues.jboss.org/browse/TEIID-5017 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > In some circumstances the cost of buffering the unsorted side to determine the applicability of the index is greater than simply using the index. The logic should also use a better estimate of the memory footprint of the index - which is only required to hold the depth of tree in memory at one time. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5022) Turn off error messages from OData/SOAP responses

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5022?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5022: --------------------------------------- See https://teiid.gitbooks.io/documents/content/admin/System_Properties.html for the org.teiid.sanitizeMessages property - this would suppress any error at the Teiid engine layer and below. However it would not affect the olingo/OData layer - such as the entity/type message. However it is of little value to omit messages such as those unless access to the OData metadata is also restricted as any client could easily determine valid entities/types. > Turn off error messages from OData/SOAP responses > ------------------------------------------------- > > Key: TEIID-5022 > URL: https://issues.jboss.org/browse/TEIID-5022 > Project: Teiid > Issue Type: Feature Request > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Optional > > There was a request to include the ability to turn off the error messages returned to the client when a bad request was made. For example, if you had a typo in your table, in the request URL, you would get a message that says "Entity does not exist". Or, if you passed in a String instead of a number, you'd get a message about expecting a Decimal but got String. > The client would like to hide these details so that a generic error message is returned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5022) Turn off error messages from OData/SOAP responses

by Steve Tran (JIRA)

[ https://issues.jboss.org/browse/TEIID-5022?page=com.atlassian.jira.plugin... ] Steve Tran commented on TEIID-5022: ----------------------------------- Would be nice if this was a dynamic setting too, so that it can be turned on/off easily during development. Also wanted to note that the error messages should still appear in the logs, just not displayed to the callers. > Turn off error messages from OData/SOAP responses > ------------------------------------------------- > > Key: TEIID-5022 > URL: https://issues.jboss.org/browse/TEIID-5022 > Project: Teiid > Issue Type: Feature Request > Reporter: Steve Tran > Assignee: Steven Hawkins > Priority: Optional > > There was a request to include the ability to turn off the error messages returned to the client when a bad request was made. For example, if you had a typo in your table, in the request URL, you would get a message that says "Entity does not exist". Or, if you passed in a String instead of a number, you'd get a message about expecting a Decimal but got String. > The client would like to hide these details so that a generic error message is returned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5022) Turn off error messages from OData/SOAP responses

by Steve Tran (JIRA)

Steve Tran created TEIID-5022: --------------------------------- Summary: Turn off error messages from OData/SOAP responses Key: TEIID-5022 URL: https://issues.jboss.org/browse/TEIID-5022 Project: Teiid Issue Type: Feature Request Reporter: Steve Tran Assignee: Steven Hawkins Priority: Optional There was a request to include the ability to turn off the error messages returned to the client when a bad request was made. For example, if you had a typo in your table, in the request URL, you would get a message that says "Entity does not exist". Or, if you passed in a String instead of a number, you'd get a message about expecting a Decimal but got String. The client would like to hide these details so that a generic error message is returned. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5021) Latest openjdk does not include anon cipher suites

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5021: ------------------------------------- Summary: Latest openjdk does not include anon cipher suites Key: TEIID-5021 URL: https://issues.jboss.org/browse/TEIID-5021 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Reporter: Steven Hawkins Assignee: Steven Hawkins Running against OpenJDK 1.8.0.141 testAnonSSLConnect fails because the anon cipher suite is not available. I could not determine yet if this is expected or a regression. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5020) Join query results in NullPointerException

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5020?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5020. ----------------------------------- Fix Version/s: 10.0 9.3.3 Resolution: Done Update RulePushSelectCriteria to add an inline view to keep the predicate in a consistent location. > Join query results in NullPointerException > ------------------------------------------ > > Key: TEIID-5020 > URL: https://issues.jboss.org/browse/TEIID-5020 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.11.6_3, 9.3.2 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > Running Join query results in NPE: > 10:36:06,836 ERROR [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue17) TEIID30019 Unexpected exception for request KuTljjNz7YSM.1: java.lang.NullPointerException > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:423) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:415) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:491) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:399) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:276) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:223) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:243) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.LanguageBridgeFactory.translate(LanguageBridgeFactory.java:186) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.<init>(ConnectorWorkItem.java:176) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.datamgr.ConnectorManager.registerRequest(ConnectorManager.java:203) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.DataTierManagerImpl.registerRequest(DataTierManagerImpl.java:997) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:179) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:497) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.AccessNode.openInternal(AccessNode.java:265) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:168) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:254) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.UnionAllNode.open(UnionAllNode.java:123) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.JoinStrategy.openRight(JoinStrategy.java:105) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:231) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:150) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:281) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.11.6_3-redhat-3.jar:8.12.11.6_3-redhat-3] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_131] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_131] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_131] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2017