July 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4342) loadMatView afterLoadScript error when calling a function

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4342?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4342: ---------------------------------- when having an exception in loadMatView procedure, the following script is executed: _EXECUTE logMsg(context=>'org.teiid.MATVIEWS', level=>'WARN', msg=>e.exception);_ but i was not able to find the log file where the exception was written. I did not find the exception message in TeiidMatViews.log and neither into the other log files. > loadMatView afterLoadScript error when calling a function > ---------------------------------------------------------- > > Key: TEIID-4342 > URL: https://issues.jboss.org/browse/TEIID-4342 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mark Tawk > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 9.0.2 > > > I'm using Teiid 9.0.0 > Here is the afterloadscript: > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute implify_dataModel.native(''ALTER TABLE "implify_data"."User" RENAME TO "implify_data"."User_temp"'');execute implify_dataModel.native(''ALTER TABLE "implify_data"."User_stage" RENAME TO "implify_data"."User"'');execute implify_dataModel.native(''ALTER TABLE "implify_data"."User_temp" RENAME TO "implify_data"."User_stage"'');execute implify_dataModel.native(''truncate table "implify_data"."User_stage"''); SELECT ON_VIEW_LOADED_COMPLETE(''VIEW.B7F553FA-4F52-45FE-82BD-E2C18A4658B2.User'') ' > the call of the following function is causing the exception, but i did not find the log file where the exception is written > SELECT ON_VIEW_LOADED_COMPLETE(''VIEW.B7F553FA-4F52-45FE-82BD-E2C18A4658B2.User'') > if I put the function into ON_VDB_DROP_SCRIPT, it is called successfully -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4323) Add support for first/last/absolute/relative "FETCH " syntax

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIID-4323?page=com.atlassian.jira.plugin... ] Debbie Steigner commented on TEIID-4323: ---------------------------------------- The customer considers this a major priority. > Add support for first/last/absolute/relative "FETCH " syntax > ------------------------------------------------------------ > > Key: TEIID-4323 > URL: https://issues.jboss.org/browse/TEIID-4323 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.1 > > > Add Support for the below FETCH syntax: > FETCH LAST FROM cursor_name > FETCH ABSOLUTE fetch_when FROM cursor_name > FETCH RELATIVE fetch_when FROM cursor_name > FETCH FIRST FROM cursor_name -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4323) Add support for first/last/absolute/relative "FETCH " syntax

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4323?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4323: --------------------------------------- What is the priority for this issue? > Add support for first/last/absolute/relative "FETCH " syntax > ------------------------------------------------------------ > > Key: TEIID-4323 > URL: https://issues.jboss.org/browse/TEIID-4323 > Project: Teiid > Issue Type: Feature Request > Components: ODBC > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 9.1 > > > Add Support for the below FETCH syntax: > FETCH LAST FROM cursor_name > FETCH ABSOLUTE fetch_when FROM cursor_name > FETCH RELATIVE fetch_when FROM cursor_name > FETCH FIRST FROM cursor_name -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4335) No buffer when close is called

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4335?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4335: --------------------------------- Fix Version/s: 8.7.8.6_2 > No buffer when close is called > ------------------------------ > > Key: TEIID-4335 > URL: https://issues.jboss.org/browse/TEIID-4335 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.7.6_2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 9.1, 8.7.8.6_2, 9.0.2 > > > Subquery that has a plan which can provide a final buffer such that no buffer is there when close is called. > Stracktrace similar to: > {code:java} > ERROR \[org.teiid.PROCESSOR\] (Worker2_QueryProcessorQueue14) TEIID30019 Unexpected exception for request PcSx3Ps9Yxeq.7: java.lang.NullPointerException > at org.teiid.query.processor.relational.SubqueryAwareEvaluator$SubqueryState.close(SubqueryAwareEvaluator.java:200) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.SubqueryAwareEvaluator.reset(SubqueryAwareEvaluator.java:233) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.SubqueryAwareEvaluator.close(SubqueryAwareEvaluator.java:244) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.SubqueryAwareRelationalNode.closeDirect(SubqueryAwareRelationalNode.java:71) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.AccessNode.closeDirect(AccessNode.java:517) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalNode.close(RelationalNode.java:332) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalNode.close(RelationalNode.java:335) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:297) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:450) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:332) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:260) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.7.7.6_2-redhat-1.jar:8.7.7.6_2-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4324) TEIID30019 Unexpected exception for request ... java.lang.AssertionError: Batch not found in storage

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4324?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4324: --------------------------------- Fix Version/s: 8.7.8.6_2 > TEIID30019 Unexpected exception for request ... java.lang.AssertionError: Batch not found in storage > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-4324 > URL: https://issues.jboss.org/browse/TEIID-4324 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 8.7.8.6_2, 9.0.2 > > Attachments: debugplan.txt > > > Error pops up after execution simple select on temporary table: > select * > from #cataruw > Exception: > Error: Batch not found in storage 73697 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-4320: ---------------------------------- > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 9.0.1 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4320: --------------------------------- Fix Version/s: 8.7.8.6_2 > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 9.0.1, 8.7.8.6_2 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-4320. -------------------------------- Resolution: Done > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.7.8.6_2, 9.0.1, 8.13.6 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3542) Logging does not print full queries which contain ESCAPE '\u0000' clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3542?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3542: --------------------------------- Fix Version/s: 8.7.8.6_2 > Logging does not print full queries which contain ESCAPE '\u0000' clause > ------------------------------------------------------------------------ > > Key: TEIID-3542 > URL: https://issues.jboss.org/browse/TEIID-3542 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.10.1 > Environment: Possibly only happens on Linux. > Reporter: Paul Richardson > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.12, 8.7.8.6_2 > > > Queries submitted to Teiid containing the NUL character for the ESCAPE character are not properly printed to jboss logging. > Seems that the NUL character can be used within java Strings but when the String is printed to the display, it terminates at the first NUL character it reaches. This result in "... ESCAPE '\u0000' ... being printed as "... ESCAPE '". > See [here|https://gist.github.com/phantomjinx/fef25524e7e9844c4f3d] for an example of a jboss log with such a query. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3542) Logging does not print full queries which contain ESCAPE '\u0000' clause

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3542?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3542. -------------------------------- Resolution: Done > Logging does not print full queries which contain ESCAPE '\u0000' clause > ------------------------------------------------------------------------ > > Key: TEIID-3542 > URL: https://issues.jboss.org/browse/TEIID-3542 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.10.1 > Environment: Possibly only happens on Linux. > Reporter: Paul Richardson > Assignee: Steven Hawkins > Priority: Trivial > Fix For: 8.7.8.6_2, 8.12 > > > Queries submitted to Teiid containing the NUL character for the ESCAPE character are not properly printed to jboss logging. > Seems that the NUL character can be used within java Strings but when the String is printed to the display, it terminates at the first NUL character it reaches. This result in "... ESCAPE '\u0000' ... being printed as "... ESCAPE '". > See [here|https://gist.github.com/phantomjinx/fef25524e7e9844c4f3d] for an example of a jboss log with such a query. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2016