March 2017 - teiid-issues - Jboss List Archives

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

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Jan Stastny edited comment on TEIID-4661 at 3/29/17 1:34 AM: ------------------------------------------------------------- I am afraid I can't reproduce the issue. When I do, what you suggest, everything works fine. So let me summarize: * I have 2 standalone-ha servers * resultset-repl is a replicated cache as posted above * I have the vdb above * I query the mat-view first time, check that status is back to LOADED * I query the mat-view second time, check that status is back to LOADED * I query the mat-view third time, check that status is back to LOADED And all the above passes, is it safe to say the issue has been resolved (Even though I haven't been able to reproduce it on 8.12.x version at all)? was (Author: jstastny): I am afraid I can't reproduce the issue. When I do, what you suggest, everything works fine. So let me summarize: * I have 2 standalone-ha servers * resultset-repl is a replicated cache as posted above * I have the vdb above * I query the mat-view first time, check that status is back to LOADED * I query the mat-view second time, check that status is back to LOADED * I query the mat-view third time, check that status is back to LOADED And all the above passes, is it safe to say the issue has been resolved (Even though I haven't been able to reproduce it on 8.12.x version at all)? > 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, 2 months

1
0
0 / 0

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

by Jan Stastny (JIRA)

[ https://issues.jboss.org/browse/TEIID-4661?page=com.atlassian.jira.plugin... ] Jan Stastny commented on TEIID-4661: ------------------------------------ I am afraid I can't reproduce the issue. When I do, what you suggest, everything works fine. So let me summarize: * I have 2 standalone-ha servers * resultset-repl is a replicated cache as posted above * I have the vdb above * I query the mat-view first time, check that status is back to LOADED * I query the mat-view second time, check that status is back to LOADED * I query the mat-view third time, check that status is back to LOADED And all the above passes, is it safe to say the issue has been resolved (Even though I haven't been able to reproduce it on 8.12.x version at all)? > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Michael Echevarria commented on TEIID-4829: ------------------------------------------- Yeah, but going through File > Import... > Teiid Connection >> Source Model > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4578) Create SqlAlchemy Dialect for Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4578?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4578: --------------------------------------- We'll add a org.teiid.pgVersion property to allow for the override of the reported postgresql version. We also need to add handling for "show transaction isolation level" - the set is already supported. To make table metadata reflection work, we need to support DEFAULT as a non-reserved keyword. I estimate that most of the paths that we'll want to support can be done in about 2 days of effort and therefore will be in beta2. > Create SqlAlchemy Dialect for Teiid > ----------------------------------- > > Key: TEIID-4578 > URL: https://issues.jboss.org/browse/TEIID-4578 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Tooling > Affects Versions: 9.1.1 > Reporter: Salvatore Incandela > Assignee: Steven Hawkins > Fix For: Open To Community, 9.3 > > > Create SqlAlchemy Dialect for Teiid > http://www.sqlalchemy.org/ > http://docs.sqlalchemy.org/en/latest/dialects/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4829: --------------------------------------- Was that using the Teiid connection importer? > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Michael Echevarria commented on TEIID-4829: ------------------------------------------- The designer pulled that in by default. I didn't adjust it > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4832) NullPointException in GroupingNode.initialize

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4832?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4832. ----------------------------------- Resolution: Done The issue was with the expression replacement logic for searched case - it did not account for the replacement expression matching a when clause. > NullPointException in GroupingNode.initialize > --------------------------------------------- > > Key: TEIID-4832 > URL: https://issues.jboss.org/browse/TEIID-4832 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.1.4 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.3, 9.2.2 > > > When executing this query: > select year(nv.variabletime) as y, case when dv.varvalue is null then 'missing' else 'wrong' end as t, count(*) as aantal_missing_or_different > from wodan_derived_variables nv > left join tv_retrieve_dervals dv on > dv.admissionid = nv.admissionid and > dv.Datetime = nv.variabletime and > dv.VariableID = 30003400 > where nv.variableid = 'PF' > and (dv.varvalue is null or round(nv.numericvalue,0) <> round(dv.varvalue,0)) > group by year(nv.variabletime), dv.varvalue is null > order by y, t > I get an exception: > 2017-03-28 11:34:19,461 ERROR [org.teiid.PROCESSOR] (Worker440_QueryProcessorQueue34086834) vF6xRF3a6hIs TEIID30019 Unexpected exception for request vF6xRF3a6hIs.52: java.lang.NullPointerException > at org.teiid.query.processor.relational.GroupingNode.initialize(GroupingNode.java:219) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226) > at org.teiid.query.processor.QueryProcessor.getBuffer(QueryProcessor.java:289) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:154) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:477) > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:349) > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:275) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:282) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4829: --------------------------------------- That's showing a length of 0 for the affected columns. Ideally it would trigger a metadata error in Designer, as that is not expected. The runtime is effectively honoring that in the odata layer by indicating that the values are too long. If you increase the length property to a wide enough value, the odata 4 path should work. So the follow on tasks may be here: - determine if a designer validation is needed - determine what set the length to 0 initially. How was the mongodb metadata created? > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Michael Echevarria updated TEIID-4829: -------------------------------------- Attachment: Screenshot from 2017-03-28 15-38-46.png > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4829) odata4 fails to return data on top of mongoDB view model

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIID-4829?page=com.atlassian.jira.plugin... ] Michael Echevarria updated TEIID-4829: -------------------------------------- Attachment: Screenshot from 2017-03-28 15-38-25.png > odata4 fails to return data on top of mongoDB view model > --------------------------------------------------------- > > Key: TEIID-4829 > URL: https://issues.jboss.org/browse/TEIID-4829 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.9.6_3 > Environment: Noticed in JDV 6.3.4 > Reporter: Michael Echevarria > Assignee: Steven Hawkins > Priority: Critical > Attachments: Screenshot from 2017-03-28 15-38-25.png, Screenshot from 2017-03-28 15-38-32.png, Screenshot from 2017-03-28 15-38-46.png, Screenshot from 2017-03-28 15-38-56.png, mongo-view-error.png, odata2-works.png, odata4-error.png > > > Description of problem: > Accessing either an exclusive view model or combined view model for a mongoDB datasource via odata4 results in an error. > The data returns via odata2, jdbc and preview in the designer > Version-Release number of selected component (if applicable): > JDV 6.3.4 > Actual results: > Property mapping error > Expected results: > Model data -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 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