April 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2820) Support Couchbase as a resource

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2820?page=com.atlassian.jira.plugin... ] Steven Hawkins reassigned TEIID-2820: ------------------------------------- Assignee: (was: Steven Hawkins) > Support Couchbase as a resource > ------------------------------- > > Key: TEIID-2820 > URL: https://issues.jboss.org/browse/TEIID-2820 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Kim Palko > Priority: Minor > Labels: data_source > Fix For: Open To Community > > > Support Couchbase as a data source in Teiid. This requires resource adapter and translater development -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4152) Error: ASSERTION FAILED: expected reference to be not null

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4152?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4152: --------------------------------------- Can you also include the user query and the stacktrace? > Error: ASSERTION FAILED: expected reference to be not null > ---------------------------------------------------------- > > Key: TEIID-4152 > URL: https://issues.jboss.org/browse/TEIID-4152 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: queryplan.txt > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4152) Error: ASSERTION FAILED: expected reference to be not null

by Bram Gadeyne (JIRA)

Bram Gadeyne created TEIID-4152: ----------------------------------- Summary: Error: ASSERTION FAILED: expected reference to be not null Key: TEIID-4152 URL: https://issues.jboss.org/browse/TEIID-4152 Project: Teiid Issue Type: Bug Affects Versions: 8.11.3 Reporter: Bram Gadeyne Assignee: Steven Hawkins Attachments: queryplan.txt -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4151) AssertionError: Delete failed

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-4151?page=com.atlassian.jira.plugin... ] Bram Gadeyne commented on TEIID-4151: ------------------------------------- I'm planning on upgrading teiid in the comming weeks. I'll try and reproduce the Exception then. > AssertionError: Delete failed > ----------------------------- > > Key: TEIID-4151 > URL: https://issues.jboss.org/browse/TEIID-4151 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > > When using a query like > insert into #CaresequencesDaily > some large select; > delete > from #CaresequencesDaily > where datum < (select cast(startime as date) from #period); > delete > from #CaresequencesDaily > where datum > (select cast(endtime as date) from #period); > We get the following exception on the execution of the second delete query. It seems it does not matter in what order the delete queries are executed. > Unexpected exception for request lMZm1kGe28/C.24: java.lang.AssertionError: Delete failed > at org.teiid.query.tempdata.TempTable.deleteTuple(TempTable.java:801) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable.access$500(TempTable.java:83) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable$2.tuplePassed(TempTable.java:775) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable$UpdateProcessor.process(TempTable.java:257) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTable.delete(TempTable.java:783) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTableDataManager$1.createTupleSource(TempTableDataManager.java:242) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:109) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:145) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:457) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:339) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:267) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.11.3.jar:8.11.3] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.11.3.jar:8.11.3] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_60] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_60] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_60] > I've tried to create a reproducable example but this doesn't throw the exception. It might be helpfull to understand what is goiing on. > insert into #tmp_params > select parsetimestamp('2016-04-01','yyyy-MM-dd') as starttime, parsetimestamp('2016-04-15','yyyy-MM-dd') as endtime; > insert into #tmp_dates > select cast(parsetimestamp('2016-03-20','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue > UNION select cast(parsetimestamp('2016-04-02','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue > UNION select cast(parsetimestamp('2016-04-20','yyyy-MM-dd') as date) as datum, 'somevalue' as somevalue; > delete > from #tmp_dates > where datum > (select cast(endtime as date) from #tmp_params); > --error is thrown when executing this second statement > delete > from #tmp_dates > where datum < (select cast(starttime as date) from #tmp_params); > select * > from #tmp_dates -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4028) adding salesforce-34 resource adapter does not work through the cli

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4028?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4028: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1316144|https://bugzilla.redhat.com/show_bug.cgi?id=1316144] from ON_QA to VERIFIED > adding salesforce-34 resource adapter does not work through the cli > ------------------------------------------------------------------- > > Key: TEIID-4028 > URL: https://issues.jboss.org/browse/TEIID-4028 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.5 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5, 8.13.3 > > > The console reports that slot is not a recognized property for resource-adapter add. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3983: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1309582|https://bugzilla.redhat.com/show_bug.cgi?id=1309582] from ON_QA to VERIFIED > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3983) External Materialization MATVIEW_ONERROR_ACTION WAIT problem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3983?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3983: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1311414|https://bugzilla.redhat.com/show_bug.cgi?id=1311414] from ON_QA to VERIFIED > External Materialization MATVIEW_ONERROR_ACTION WAIT problem > ------------------------------------------------------------ > > Key: TEIID-3983 > URL: https://issues.jboss.org/browse/TEIID-3983 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > > When using "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT' option in materialized view definition, there's problem with blocked request. > The blocked request is the one, that triggered the materialized view's loading (first query on the defined materialized view). After such request, one can observe, that the query execution doesn't end, but hangs. > Meanwhile while examining the contents of 'status' table in the underlying database, the LoadNumber column's value increases regularly according to the defined ttl. Moreover the 'LOADSTATE' column changes from LOADING to LOADED in similar manner. The materialized table is populated with correct data. From this I assume, materialization is set up correctly. > During the wait, when logging set to DEBUG, there appears regularly, apart from the logs about refreshing the mat view, this entry: > {code:plain} > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 with state PROCESSING > [32m09:14:52,151 DEBUG [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue2695) Request Thread 87XzBpSzkyk4.0 - processor blocked > {code} > The log appears in 'ttl' determined intervals, each time after materialized table loading related entries. > The thread mentioned is the one created after the original query execution was initiated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3995) SAP HANA materialization:function loadMatView with argument invalidate set to true problem

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3995?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3995: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1311412|https://bugzilla.redhat.com/show_bug.cgi?id=1311412] from ON_QA to VERIFIED > SAP HANA materialization:function loadMatView with argument invalidate set to true problem > ------------------------------------------------------------------------------------------ > > Key: TEIID-3995 > URL: https://issues.jboss.org/browse/TEIID-3995 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.12.x > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.5, 8.13.2 > > Attachments: server.log > > > There appears to be an issue with loadMatView function. > Specifically when the function is invoked with invalidate=>'true' argument, when it is expected, that invocation of this function invalidates the current contents of the materialized view until the initiated load is completed and new data are populated. > But when calling this function as described, an error occurs: > {code:plain} > TEIID20001 The modeled datatype integer for column 0 doesn't match the runtime type "org.teiid.core.types.ArrayImpl". Please ensure that the column's modeled datatype matches the expected data. > {code} > Please note, that there is no column of type array in my schema. > There is declaration of the view: > {code:sql} > CREATE VIEW external_long_ttl ( > customer_id integer NOT NULL, > total_amount integer > ) > {code} > and the query used to load the view: > {code:sql} > "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;', > {code} > Complete definition of the view is: > {code:sql} > CREATE VIEW external_long_ttl ( > customer_id integer NOT NULL, > total_amount integer > ) OPTIONS ( > MATERIALIZED 'TRUE', > UPDATABLE 'FALSE', > MATERIALIZED_TABLE 'Source.JSTASTNY.dv_matviews_mat_view', > "teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true', > "teiid_rel:MATVIEW_STATUS_TABLE" 'Source.JSTASTNY.dv_matviews_statustable', > "teiid_rel:ON_VDB_START_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_create) SELECT id, vdb_create+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:ON_VDB_DROP_SCRIPT" 'MERGE INTO dv_matviews_check_table(id,vdb_drop) SELECT id, vdb_drop+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_LOAD_SCRIPT" 'INSERT INTO dv_matviews_mat_view_stage(customer_id,total_amount) SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id;', > "teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'exec Source.native(''truncate table dv_matviews_mat_view_stage'');MERGE INTO dv_matviews_check_table(id,before_load) SELECT id, before_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'exec Source.native(''RENAME TABLE dv_matviews_mat_view_stage TO dv_matviews_mat_view_temp'');exec Source.native(''RENAME TABLE dv_matviews_mat_view TO dv_matviews_mat_view_stage'');exec Source.native(''RENAME TABLE dv_matviews_mat_view_temp TO dv_matviews_mat_view'');MERGE INTO dv_matviews_check_table(id,after_load) SELECT id, after_load+1 FROM dv_matviews_check_table WHERE id=''external_long_ttl'';', > "teiid_rel:MATVIEW_ONERROR_ACTION" 'WAIT', > "teiid_rel:MATVIEW_TTL" 20000 > ) AS SELECT CONVERT(c.id,integer) AS customer_id, CONVERT(SUM(o.amount),integer) AS total_amount FROM dv_matviews_customers c INNER JOIN dv_matviews_orders o ON c.id = o.customer_id GROUP BY c.id; > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4102) Infinispan 6 resource-adapter has not valid module.xml

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4102?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4102: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1320509|https://bugzilla.redhat.com/show_bug.cgi?id=1320509] from ON_QA to VERIFIED > Infinispan 6 resource-adapter has not valid module.xml > ------------------------------------------------------ > > Key: TEIID-4102 > URL: https://issues.jboss.org/browse/TEIID-4102 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.x > Reporter: Jan Stastny > Assignee: Van Halbert > Fix For: 8.12.5 > > > There is problem with invalid module.xml file in infinispan 6 resource-adapter. > In its dependencies there is: > {code:xml} > <module name="org.jboss.teiid.translator.infinispan.cache" export=true/> > {code} > There should be > {code:xml} > <module name="org.jboss.teiid.translator.infinispan.cache" export="true"/> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4050) database logging doesn't add command and audit loggers for domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4050?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4050: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1314716|https://bugzilla.redhat.com/show_bug.cgi?id=1314716] from ON_QA to VERIFIED > database logging doesn't add command and audit loggers for domain mode > ---------------------------------------------------------------------- > > Key: TEIID-4050 > URL: https://issues.jboss.org/browse/TEIID-4050 > Project: Teiid > Issue Type: Bug > Components: Tooling > Affects Versions: 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > Fix For: 9.0, 8.12.x > > > When installing database logging, than no org.teiid.COMMAND_LOG or org.teiid.AUDIT_LOG category loggers are present in domain.xml for ha and full-ha profile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2016