April 2016 - teiid-issues - Jboss List Archives

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

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4151?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4151: ---------------------------------- Component/s: Query Engine Fix Version/s: 9.0 8.13.4 I have been able to reproduce this in master. I'll provide a fix shortly. > AssertionError: Delete failed > ----------------------------- > > Key: TEIID-4151 > URL: https://issues.jboss.org/browse/TEIID-4151 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Fix For: 9.0, 8.13.4 > > > 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)

8 years, 1 month

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 updated TEIID-4152: ---------------------------------- Description: (was: I have been able to reproduce this in master. I'll provide a fix shortly.) > 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 > Components: Query Engine > 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)

8 years, 1 month

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 updated TEIID-4152: ---------------------------------- Component/s: Query Engine Description: I have been able to reproduce this in master. I'll provide a fix shortly. Fix Version/s: 9.0 8.13.4 > 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 > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: queryplan.txt > > > I have been able to reproduce this in master. I'll provide a fix shortly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

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 updated TEIID-4152: ---------------------------------- Fix Version/s: (was: 9.0) (was: 8.13.4) > 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 > Components: Query Engine > Affects Versions: 8.11.3 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Attachments: queryplan.txt > > > I have been able to reproduce this in master. I'll provide a fix shortly. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-3035) Request to add NTLM Security to Web service datasources

by Jesse Shaffer (JIRA)

[ https://issues.jboss.org/browse/TEIID-3035?page=com.atlassian.jira.plugin... ] Jesse Shaffer commented on TEIID-3035: -------------------------------------- [~rareddy], I'm not very familiar with CXF or JAAS (or JBoss security in general for that matter), but a quick search turned up project Waffle, which provides a JAAS module (on Windows only). Would that be something I could use? I also turned this thread up from someone working directly with SharePoint from Java w/CXF: http://cxf.547215.n5.nabble.com/CXF-Client-NTLM-Authentication-with-Share..., but it seems to be setting up the authenticator at a global level, which I'm pretty sure is something I do not want. In any case, they make the point that NTLM authentication is built directly into JDK 1.6+, so it's apparently available to be used by CXF already. > Request to add NTLM Security to Web service datasources > ------------------------------------------------------- > > Key: TEIID-3035 > URL: https://issues.jboss.org/browse/TEIID-3035 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > > Currently the only Security types we support for Web Service data sources is None, HTTPBasic and WSSecurity can NTLM be added? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4165) HBase translator - time values are not translated correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4165?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4165: --------------------------------------- Can you try inserting times with the 1970 date component as well? If phoenix/hbase is not normalizing the time values, then we at least need to document that if not change the importer to use the timestamp type instead. > HBase translator - time values are not translated correctly > ----------------------------------------------------------- > > Key: TEIID-4165 > URL: https://issues.jboss.org/browse/TEIID-4165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > HBase translator rewrites time values (e.g. \{t '15:00:00'\}) as _TIME '1970-01-01 15:00:00.0'_. But HBase stores time values with base date _1900-01-01..._. > Updated source-specific commands returns correct result. > {code:sql} > SELECT g_0.intkey FROM smalla AS g_0 WHERE g_0.timevalue IN (TIME '1900-01-01 05:00:00.0', TIME '1900-01-01 15:00:00.0') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4165) HBase translator - time values are not translated correctly

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4165?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4165: ------------------------------------- No, driver does not support TIME without date component. *Exception:* Error: ERROR 601 (42P00): Syntax error. java.lang.IllegalArgumentException: Invalid format: "15:00:00.0" is malformed at ":00:00.0" I think that time were created using 1900-01-01 date component. That is the root cause probably. Phoenix supports time value, but requires date component (if created via SQL like UPSERT INTO..., not via PreparedStatement). > HBase translator - time values are not translated correctly > ----------------------------------------------------------- > > Key: TEIID-4165 > URL: https://issues.jboss.org/browse/TEIID-4165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > HBase translator rewrites time values (e.g. \{t '15:00:00'\}) as _TIME '1970-01-01 15:00:00.0'_. But HBase stores time values with base date _1900-01-01..._. > Updated source-specific commands returns correct result. > {code:sql} > SELECT g_0.intkey FROM smalla AS g_0 WHERE g_0.timevalue IN (TIME '1900-01-01 05:00:00.0', TIME '1900-01-01 15:00:00.0') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4165) HBase translator - time values are not translated correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4165?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4165: --------------------------------------- I can't say yet if this is our issue. The JDBC/Teiid notion of a time value does assume a date component of 1970, not 1900. How were the time values created? And if you can quickly test, does the source support just TIME '05:00:00.0' - without the date component? > HBase translator - time values are not translated correctly > ----------------------------------------------------------- > > Key: TEIID-4165 > URL: https://issues.jboss.org/browse/TEIID-4165 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.x > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > HBase translator rewrites time values (e.g. \{t '15:00:00'\}) as _TIME '1970-01-01 15:00:00.0'_. But HBase stores time values with base date _1900-01-01..._. > Updated source-specific commands returns correct result. > {code:sql} > SELECT g_0.intkey FROM smalla AS g_0 WHERE g_0.timevalue IN (TIME '1900-01-01 05:00:00.0', TIME '1900-01-01 15:00:00.0') > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4064) OData - missing non-nullable property

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4064?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4064. --------------------------------- Resolution: Done > OData - missing non-nullable property > ------------------------------------- > > Key: TEIID-4064 > URL: https://issues.jboss.org/browse/TEIID-4064 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Labels: Alpha3 > Fix For: 9.0, 8.12.5 > > > Change DDL for tables Customer and Orders in VDB as follows: > {code:sql} > CREATE FOREIGN TABLE Customers ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > name varchar(10)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.CUSTOMERS'); > CREATE FOREIGN TABLE Orders ( > id integer PRIMARY KEY OPTIONS (NAMEINSOURCE 'id'), > customerid integer, > place varchar(10), > FOREIGN KEY (customerid) REFERENCES Customers(id)) OPTIONS (NAMEINSOURCE 'DB.PUBLIC.ORDERS'); > {code} > Note, that both tables have same name of primary key named "id". > Invoke GET method to URL http://localhost:8080/odata4/olingo_basic/Source/Customers/?$count=true&$... > *Result:* > {code:xml} > <error> > <code>400</code> > <message>The non-nullable property 'id' is missing.</message> > </error> > {code} > Here are selected part of Teiid's log: > *Query:* > {code:sql} > SELECT g10.id, g10.name, g11.id, g11.customerid, g11.place FROM Source.Customers AS g10 LEFT OUTER JOIN Source.Orders AS g11 ON g10.id = g11.customerid ORDER BY g10.id > {code} > *Result:* > |id|name|id|customerid|place| > |1|customer1|1|1|town| > |1|customer1|2|1|state| > |1|customer1|3|1|country| > |1|customer1|4|1|abroad| > |2|customer2|5|2|state| > |2|customer2|6|2|country| > |3|customer3|7|3|town| > |3|customer3|8|3|town| > |4|customer4|<null>|<null>|<null>| -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4042) OData returns status code 200 instead of 204 if there are no expanded entities

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4042?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4042. --------------------------------- Resolution: Done > OData returns status code 200 instead of 204 if there are no expanded entities > ------------------------------------------------------------------------------- > > Key: TEIID-4042 > URL: https://issues.jboss.org/browse/TEIID-4042 > Project: Teiid > Issue Type: Sub-task > Components: OData > Reporter: Juraj Duráni > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > *URL:* http://localhost:8080/odata4/olingo_basic/Source/Customers(4)/Orders_FK0 > *Returned status code:* 200 > *Expected:* 204 and empty body > See http://docs.oasis-open.org/odata/odata/v4.0/errata02/os/complete/part1-pr... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2016