March 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4827) Update the readme to indicate that Java 1.8 is required for building

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4827: ------------------------------------- Summary: Update the readme to indicate that Java 1.8 is required for building Key: TEIID-4827 URL: https://issues.jboss.org/browse/TEIID-4827 Project: Teiid Issue Type: Bug Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.3 There are several places where we are implicitly depending upon 1.8 features to build - such as the larger key size from TestDhKeyGenerator. These issues do not affect compatibility with a 1.7 runtime. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4661: --------------------------------------- Changing the test case on master to more repetitions still provides the expected result - that subsequent queries do not hang. > Subsequent queries hang after materialized view TTL expires. > ------------------------------------------------------------ > > Key: TEIID-4661 > URL: https://issues.jboss.org/browse/TEIID-4661 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3 > > > With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4661) Subsequent queries hang after materialized view TTL expires.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4661: --------------------------------------- What vdb are you using? Also are you testing that the subsequent query is hanging as it's not clear from what's here that we could be in the loading state ephemerally. > Subsequent queries hang after materialized view TTL expires. > ------------------------------------------------------------ > > Key: TEIID-4661 > URL: https://issues.jboss.org/browse/TEIID-4661 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Reporter: Colin Mondesir > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.0.6, 9.1.2, 9.2, 8.12.10.6_3 > > > With a VDB using lazy-invalidate in a clustered configuration initially the materialized view is cached correctly but when the TTL expires (10 minutes) and the query is run again the state of the view changes to LOADING and never reverts to "LOADED", so the next query hangs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4468) Google translator evaluates 0 as not NULL for operator <>

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4468?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4468: --------------------------------- Fix Version/s: 8.12.10.6_3 > Google translator evaluates 0 as not NULL for operator <> > ---------------------------------------------------------- > > Key: TEIID-4468 > URL: https://issues.jboss.org/browse/TEIID-4468 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12 > Reporter: Lucie Fabrikova > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.5, 8.12.10.6_3, 8.12.x-6.4 > > > Query ""SELECT stringNum FROM bqt1.SmallA <> 0" returns also values NULL (empty cell in spreadsheet). > I.e., NULL is treated as different from 0. > If this is expected behavior, shouldn't it be in the documentation? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2879) Add more Resource Management

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2879?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2879. ----------------------------------- Resolution: Duplicate Issue Marking as a duplicate of TEIID-4742, TEIID-2465, and TEIID-4557 > Add more Resource Management > ---------------------------- > > Key: TEIID-2879 > URL: https://issues.jboss.org/browse/TEIID-2879 > Project: Teiid > Issue Type: Feature Request > Reporter: Rick Wagner > Assignee: Steven Hawkins > > To protect the system sometimes we may need to throttle the queries to ensure it does not exhaust all the existing resources on the server. Resource management is the key to play this role of monitoring and throttling queries. Oracle products offer such a feature for managing the consumption of resources. We have quite a number of (Teiid) profiles running on a big box and we want to ensure no silly queires are hogging on to all the resources and consequently causing issue to others. > Ability to throttle the query by restricting query that uses > 1) Too much CPU > 2) Too much java heap > 3) Long running query -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4817) Infinispan DSL Resource Adapter: can't query after JDG restart

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4817?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4817: ------------------------------- Fix Version/s: 8.12.x-6.4 > Infinispan DSL Resource Adapter: can't query after JDG restart > -------------------------------------------------------------- > > Key: TEIID-4817 > URL: https://issues.jboss.org/browse/TEIID-4817 > Project: Teiid > Issue Type: Bug > Components: JDG Connector > Affects Versions: 8.12.10.6_3 > Reporter: Jan Stastny > Assignee: Van Halbert > Priority: Blocker > Fix For: 9.3, 8.12.10.6_3, 8.12.x-6.4 > > > There is an issue with Infinispan DSL connector when accessing JDG after it has been restarted. > When I have a vdb accessing JDG only as datasource and I do following: > 1. Start JDV and JDG > 2. Configure JDV to use JDG as datasource (no materialization needed) > 3. Deploy a vdb accessing the JDG instance using a pojo. > 4. Query the vdb with no issues. > 5. Restart JDG (call reload using DMR/CLI) > 6. Wait for JDG to come up. > 7. Query the vdb again > Then in step 7 I get: > {code:plain|title="WARN in server log"} > 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA > {code} > {code:plain|title="full stacktrace"} > 12:32:32,749 WARN [org.infinispan.client.hotrod.impl.protocol.Codec21] (Worker1_QueryProcessorQueue5) ISPN004005: Error received from the server: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA > 12:32:32,753 WARN [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue5) Connector worker process failed for atomic-request=jUZx1bBd0k4L.0.3.1: org.teiid.translator.TranslatorException: java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA > at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:275) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_121] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_121] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_121] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_121] > at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at com.sun.proxy.$Proxy89.execute(Unknown Source) > at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_121] > at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_121] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_121] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_121] > Caused by: org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for message id[9] returned server error (status=0x85): java.lang.IllegalStateException: Unknown entity name org.jboss.qe.jdg.remote.protobuf.SmallA > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:133) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:119) > at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) > at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:62) > at org.infinispan.client.hotrod.impl.operations.QueryOperation.executeOperation(QueryOperation.java:28) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) > at org.infinispan.client.hotrod.impl.query.RemoteQuery.executeQuery(RemoteQuery.java:61) > at org.infinispan.client.hotrod.impl.query.RemoteQuery.list(RemoteQuery.java:51) > at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:196) > at org.teiid.resource.adapter.infinispan.dsl.DSLSearch.performSearch(DSLSearch.java:149) > at org.teiid.translator.object.ObjectExecution.execute(ObjectExecution.java:261) [translator-object-8.12.10.6_3-redhat-1.jar:8.12.10.6_3-redhat-1] > ... 18 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4826) OAuth2 add option to set access_token directly in login module

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4826?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4826. --------------------------------- Fix Version/s: 9.3 Assignee: Jan Stastny (was: Steven Hawkins) Resolution: Done Labels: Alpha2 (was: ) > OAuth2 add option to set access_token directly in login module > -------------------------------------------------------------- > > Key: TEIID-4826 > URL: https://issues.jboss.org/browse/TEIID-4826 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.3 > Reporter: Jan Stastny > Assignee: Jan Stastny > Labels: Alpha2 > Fix For: 9.3 > > > OAuth2 login module expects that auth service issues a 'refresh_token' together with an access_token. Then it can be used together with 'access_token_uri' to get a valid access_token automatically. > Still this prevents Teiid from being configured for such OAuth2 implementations, that don't provide the refresh_token. > One option how to workaround this inconsistency in OAuth2 service implementations is to provide option to set the access_token directly in a login-module. This would resolve the issue for never expiring or long-lasting access_token. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4826) OAuth2 add option to set access_token directly in login module

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4826?page=com.atlassian.jira.plugin... ] Jan Stastny updated TEIID-4826: ------------------------------- Security: (was: Security Issue) > OAuth2 add option to set access_token directly in login module > -------------------------------------------------------------- > > Key: TEIID-4826 > URL: https://issues.jboss.org/browse/TEIID-4826 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.3 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > OAuth2 login module expects that auth service issues a 'refresh_token' together with an access_token. Then it can be used together with 'access_token_uri' to get a valid access_token automatically. > Still this prevents Teiid from being configured for such OAuth2 implementations, that don't provide the refresh_token. > One option how to workaround this inconsistency in OAuth2 service implementations is to provide option to set the access_token directly in a login-module. This would resolve the issue for never expiring or long-lasting access_token. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4825) Google translator throws Column doesn't exist in the worksheet

by Lucie Fabrikova (JIRA)

Lucie Fabrikova created TEIID-4825: -------------------------------------- Summary: Google translator throws Column doesn't exist in the worksheet Key: TEIID-4825 URL: https://issues.jboss.org/browse/TEIID-4825 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.10.6_3 Reporter: Lucie Fabrikova Assignee: Steven Hawkins Attachments: gs-export-vdb.xml, server.log-dv635cr1 If sheet (WikiData9) contains only string type columns, queries to that sheet fail with 'org.teiid.resource.adapter.google.common.SpreadsheetOperationException: Column link doesn't exist in the worksheet WikiData9' If I added e.g. numeric or boolean column, it worked ok... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4819) Tree page modifications removing the previous page, don't remove immediately

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4819?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4819. ----------------------------------- Resolution: Done Corrected to always perform the remove and simplified the addMemoryEntry call. > Tree page modifications removing the previous page, don't remove immediately > ---------------------------------------------------------------------------- > > Key: TEIID-4819 > URL: https://issues.jboss.org/browse/TEIID-4819 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.9, 8.7.6.6_2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.3, 9.1.5, 9.2.2 > > > TEIID-3119 introduced logic to reuse the existing cacheentry, but the removal of the old entry was based upon the wrong remove method - just a remove from cache and not memory. That would delay the cleanup of the memory reference until eviction or when the buffer/tree is removed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 March 2017