[JBoss JIRA] (TEIID-4431) ASSERTION FAILED: expected reference to be not null
by Chenna Krishna (JIRA)
[ https://issues.jboss.org/browse/TEIID-4431?page=com.atlassian.jira.plugin... ]
Chenna Krishna updated TEIID-4431:
----------------------------------
Issue Type: Bug (was: Task)
> ASSERTION FAILED: expected reference to be not null
> ---------------------------------------------------
>
> Key: TEIID-4431
> URL: https://issues.jboss.org/browse/TEIID-4431
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12.x
> Reporter: Chenna Krishna
> Assignee: Steven Hawkins
>
> We are using TEIID 8.12 driver for Jasper. Getting the below query when tried to trigger the query.
> Caused by: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
> "DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
> "DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
> "DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
> "DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
> "DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
> "DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
> "DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
> "DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
> from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
> left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
> order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
> limit 200001
> Error Log:
> Caused by: com.jaspersoft.commons.dataset.DataSetException: Exception calling JRDataSource.next() for query select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
> "DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
> "DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
> "DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
> "DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
> "DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
> "DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
> "DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
> "DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
> from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
> left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
> left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
> order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
> limit 200001
> at com.jaspersoft.commons.semantic.dsimpl.JRQueryDataSet$JRDataSetIterator.next(JRQueryDataSet.java:456)
> at com.jaspersoft.commons.datarator.CachedData.fetchData(CachedData.java:217)
> ... 138 more
> Caused by: net.sf.jasperreports.engine.JRException: Error executing SQL statement for: null.
> at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:344)
> at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:169)
> at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:157)
> ... 1 more
> Caused by: org.teiid.jdbc.TeiidSQLException: ASSERTION FAILED: expected reference to be not null
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:703)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:542)
> at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:538)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260)
> at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73)
> at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:310)
> ... 3 more
> Regards,
> Chenna
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4431) ASSERTION FAILED: expected reference to be not null
by Chenna Krishna (JIRA)
Chenna Krishna created TEIID-4431:
-------------------------------------
Summary: ASSERTION FAILED: expected reference to be not null
Key: TEIID-4431
URL: https://issues.jboss.org/browse/TEIID-4431
Project: Teiid
Issue Type: Task
Components: Query Engine
Affects Versions: 8.12.x
Reporter: Chenna Krishna
Assignee: Steven Hawkins
We are using TEIID 8.12 driver for Jasper. Getting the below query when tried to trigger the query.
Caused by: java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
"DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
"DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
"DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
"DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
"DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
"DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
"DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
"DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
limit 200001
Error Log:
Caused by: com.jaspersoft.commons.dataset.DataSetException: Exception calling JRDataSource.next() for query select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE",
"DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME",
"DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE",
"DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE",
"DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE",
"DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME",
"DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE",
"DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE",
"DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"
from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"
left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")
left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")
left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")
order by "DT_ODS_AGENT_PROFILES_AGENT_CODE"
limit 200001
at com.jaspersoft.commons.semantic.dsimpl.JRQueryDataSet$JRDataSetIterator.next(JRQueryDataSet.java:456)
at com.jaspersoft.commons.datarator.CachedData.fetchData(CachedData.java:217)
... 138 more
Caused by: net.sf.jasperreports.engine.JRException: Error executing SQL statement for: null.
at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:344)
at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:169)
at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:157)
... 1 more
Caused by: org.teiid.jdbc.TeiidSQLException: ASSERTION FAILED: expected reference to be not null
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135)
at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71)
at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:703)
at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:64)
at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:542)
at org.teiid.client.util.ResultsFuture.addCompletionListener(ResultsFuture.java:148)
at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:538)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:260)
at org.teiid.jdbc.PreparedStatementImpl.executeQuery(PreparedStatementImpl.java:73)
at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:310)
... 3 more
Regards,
Chenna
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4325) ASSERTION FAILED: expected reference to be not null
by Chenna Krishna (JIRA)
[ https://issues.jboss.org/browse/TEIID-4325?page=com.atlassian.jira.plugin... ]
Chenna Krishna commented on TEIID-4325:
---------------------------------------
Mark,
How the problem fixed for this. Which join condition has to be changed we are also facing the same error in TEIID (jasper). Suggestion would be very helpful. We are using
Teiid JDBC Driver version 8.12 (8/12)
Query:
select "DOX_JB_EAM_FOLDER_SP"."EAM_CODE" as "DOX_JB_EAM_FOLDER_SP_EAM_CODE","DOX_JB_EAM_FOLDER_SP"."OBJECT_NAME" as "DOX_JB_EAM_FOLDER_SP_OBJECT_NAME","DT_DOX_JB_EAM_DOC_SP_CA"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_CA_R_CREATION_DATE","DT_DOX_JB_EAM_DOC_SP_EAM"."R_CREATION_DATE" as "DT_DOX_JB_EAM_DOC_SP_EAM_R_CREATION_DATE","DT_ODS_AGENT_PROFILES"."AGENT_CODE" as "DT_ODS_AGENT_PROFILES_AGENT_CODE","DT_ODS_AGENT_PROFILES"."AGENT_NAME" as "DT_ODS_AGENT_PROFILES_AGENT_NAME","DT_ODS_AGENT_PROFILES"."MODIFICATION_DATE" as "DT_ODS_AGENT_PROFILES_MODIFICATION_DATE","DT_ODS_AGENT_PROFILES"."OPEN_DATE" as "DT_ODS_AGENT_PROFILES_OPEN_DATE","DT_ODS_AGENT_PROFILES"."STATUS" as "DT_ODS_AGENT_PROFILES_STATUS"from "DOX_JASPER_DXTR_USER"."JB_EAM_FOLDER_SP_SG" "DOX_JB_EAM_FOLDER_SP"left outer join (SELECT AGENT_CODE, AGENT_NAME, MODIFICATION_DATE, OPEN_DATE, CASE WHEN STATUS = 'A' THEN 'Inactive' WHEN STATUS = '' THEN 'Active' ELSE STATUS END AS STATUS FROM ODS.AGENT_PROFILES WHERE FLG_ACTIVE = 'Y') "DT_ODS_AGENT_PROFILES" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_ODS_AGENT_PROFILES"."AGENT_CODE")left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E115' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_CA" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_CA"."EAM_CODE")left outer join (SELECT D.DOC_CODE, D.EAM_CODE, D.OBJECT_NAME, D.R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG D INNER JOIN (SELECT EAM_CODE, DOC_CODE, MAX(R_CREATION_DATE) R_CREATION_DATE FROM DOX_JASPER_DXTR_USER.JB_EAM_DOC_SP_SG WHERE DOC_CODE = 'E109' GROUP BY EAM_CODE, DOC_CODE) T ON D.EAM_CODE = T.EAM_CODE AND D.DOC_CODE = T.DOC_CODE AND D.R_CREATION_DATE = T.R_CREATION_DATE) "DT_DOX_JB_EAM_DOC_SP_EAM" on ("DOX_JB_EAM_FOLDER_SP"."EAM_CODE" = "DT_DOX_JB_EAM_DOC_SP_EAM"."EAM_CODE")order by "DT_ODS_AGENT_PROFILES_AGENT_CODE" limit 200001
Regads,
Chenna
> ASSERTION FAILED: expected reference to be not null
> ---------------------------------------------------
>
> Key: TEIID-4325
> URL: https://issues.jboss.org/browse/TEIID-4325
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.12
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Fix For: 9.1, 9.0.2, 8.12.6.6_3
>
> Attachments: show_plan_debug.txt
>
>
> I'm using teiid 9.0.0 over h2 :
>
> I'm getting ASSERTION_FAILED over the following query and can not find what is causing this exception:
>
> select "Sheet1"."AvgAmoutRange" as "Sheet1_EBt_211215_AvgAmoutRa1",COUNT( distinct IFNULL("CEGlobalView"."Customer_CustomerID",-2147483648)) as "CEGlobalView_Customer_Custom2","CEGlobalView"."Customer_GenderID" as "CEGlobalView_Customer_Gender1","Gender"."Gender" as "Gender_Gender","Sheet1"."Sheet1_EBt_211215ID" as "Sheet1_EBt_211215_Sheet1_EBt11" from "CEBanksBusinessModel"."CEGlobalView" "CEGlobalView" LEFT JOIN "h2dbimplify_data_cebankModel_ST"."implify_data_cebank"."Sheet1_EBt_211215" "Sheet1" ON ( ("CEGlobalView"."StreamCardsvt3r_StreamCards_1" BETWEEN "Sheet1"."Min" and "Sheet1"."Max") )
> LEFT JOIN "h2dbimplify_data_cebankModel_fR"."implify_data_cebank"."Gender" "Gender" ON "CEGlobalView"."Customer_GenderID" = "Gender"."GenderID"
> LEFT JOIN "h2dbimplify_data_cebankModel_fR"."implify_data_cebank"."CustomerTag" "CustomerTag" ON "CEGlobalView"."Customer_CustomerID" = "CustomerTag"."Customer_CustomerID" AND ( ( ("CustomerTag"."EndDateTime" > CURDATE()) OR ( ("CustomerTag"."EndDateTime" IS null ) ) ) )
> LEFT JOIN "h2dbimplify_data_cebankModel_fR"."implify_data_cebank"."TagValue" "TagValue" ON "CustomerTag"."TagValue_TagValueID" = "TagValue"."TagValueID"
> LEFT JOIN "h2dbimplify_data_cebankModel_fR"."implify_data_cebank"."TagName" "TagName" ON "TagValue"."TagName_TagNameID" = "TagName"."TagNameID" AND ( ( ("TagName"."TagType_TagTypeID" IN (1.0) ) ) AND ( ("TagName"."TagScope_TagScopeID" IN (1.0) ) ) )
> where ( ( ( ("TagName"."TagName" IN ('Behavior') ) ) ) AND ( ("Sheet1"."AvgAmoutRange" IS NOT null ) ) AND ( ("CEGlobalView"."Customer_GenderID" IS NOT null ) ) AND ( ("Gender"."Gender" IS NOT null ) ) ) group by "Sheet1"."AvgAmoutRange","CEGlobalView"."Customer_GenderID","Gender"."Gender","Sheet1"."Sheet1_EBt_211215ID" order by "Sheet1"."Sheet1_EBt_211215ID" ASC,"Sheet1"."AvgAmoutRange" ASC,"Gender"."Gender" DESC,"CEGlobalView"."Customer_GenderID" DESC
>
> The exception stack:
>
> ERROR TEIID_DQP_LOGGER:90 (http-bio-8080-exec-14) - - [TEIID30019 Unexpected exception for request rBDBCRYcUyyM.0]
> java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null
> at org.teiid.core.util.Assertion.failed(Assertion.java:73)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100)
> at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92)
> at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367)
> at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133)
> 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.nextBatchDirect(QueryProcessor.java:138)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:472)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:348)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:274)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:313)
> at org.teiid.dqp.internal.process.DQPCore.executeRequest(DQPCore.java:245)
> at sun.reflect.GeneratedMethodAccessor423.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.teiid.transport.LocalServerConnection$1$1.call(LocalServerConnection.java:177)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:276)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:260)
> at org.teiid.transport.LocalServerConnection$1.invoke(LocalServerConnection.java:175)
> at com.sun.proxy.$Proxy34.executeRequest(Unknown Source)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:673)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:539)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:1060)
> at org.teiid.jdbc.StatementImpl.execute(StatementImpl.java:323)
> you find attached the show plan debug
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4427:
---------------------------------------
Looking at this more, I see the same behavior in 8.11.x - that is we do validate the expected types, and I can get an exception during planning like:
org.teiid.api.exception.query.QueryValidatorException: The definition for pm1.G2 has the wrong type for column 1. Expected integer, but was bigdecimal.
at org.teiid.query.resolver.QueryResolver.validateProjectedSymbols(QueryResolver.java:487)
at org.teiid.query.resolver.QueryResolver.validateProjectedSymbols(QueryResolver.java:471)
at org.teiid.query.resolver.QueryResolver.resolveView(QueryResolver.java:440)
at org.teiid.query.optimizer.relational.RelationalPlanner.resolveVirtualGroup(RelationalPlanner.java:1832)
at org.teiid.query.optimizer.relational.RelationalPlanner.buildTree(RelationalPlanner.java:1226)
at org.teiid.query.optimizer.relational.RelationalPlanner.createQueryPlan(RelationalPlanner.java:1121)
The ddl is roughly, which has the wider bigdecimal type in the materialization target:
CREATE FOREIGN TABLE G1(e1 bigdecimal, e2 varchar);
CREATE VIEW G2 OPTIONS (MATERIALIZED 'true', MATERIALIZED_TABLE 'pm1.G1') AS SELECT 1 as e1, e2 FROM pm1.G1;
With TEIID-3999 the exception will occur during deployment. So it looks like we'll need more details on your scenario.
> Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-4427
> URL: https://issues.jboss.org/browse/TEIID-4427
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1, 9.0.4
>
>
> After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server.
> when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal.
> If we go back to Teiid 8.11.3, the same materialized views fetch without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4427:
---------------------------------------
This was caused by TEIID-3999 - but there are circumstances that will be problematic if the types do not match, so we need to properly address this rather than just relaxing the validation.
> Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-4427
> URL: https://issues.jboss.org/browse/TEIID-4427
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1, 9.0.4
>
>
> After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server.
> when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal.
> If we go back to Teiid 8.11.3, the same materialized views fetch without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4427) Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4427:
----------------------------------
Component/s: Query Engine
Fix Version/s: 9.1
9.0.4
Priority: Critical (was: Blocker)
Affects Version/s: 9.0
> Migration to Teiid 9.0.0 - Materialized views error: Expected integer, but was bigdecimal
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-4427
> URL: https://issues.jboss.org/browse/TEIID-4427
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 9.0
> Reporter: Mark Tawk
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 9.1, 9.0.4
>
>
> After migrating to Teiid 9.0.0, we are facing issues with existing views materialized on Oracle server.
> when fetching an Oracle materialized view that contains a column using date function like : "Month" or "Year" or "TIMESTAMPDIFF", we are getting the error : Expected integer, but was bigdecimal.
> If we go back to Teiid 8.11.3, the same materialized views fetch without any problem.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4422) Impala Translator - add pushdown support for concat and concat_ws functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4422?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4422.
-----------------------------------
Fix Version/s: 9.1
Resolution: Done
Marking as resolved. We can also look into adding a concat_ws system function, but unfortunately the null handling varies by vendor - postgresql/mysql skip non-separator nulls, but impala makes the whole result null.
> Impala Translator - add pushdown support for concat and concat_ws functions
> ---------------------------------------------------------------------------
>
> Key: TEIID-4422
> URL: https://issues.jboss.org/browse/TEIID-4422
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 9.0.2
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
> Fix For: 9.1
>
>
> As a consumer I need the concat and concat_ws function definitions with matching signatures in line with http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp...
> concat:
> concat(string a, string b...)
> Purpose: Returns a single string representing all the argument values joined together.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
> concat_ws:
> concat_ws(string sep, string a, string b...)
> Purpose: Returns a single string representing the second and following argument values joined together, delimited by a specified separator.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4422) Impala Translator - add pushdown support for concat and concat_ws functions
by Don Krapohl (JIRA)
[ https://issues.jboss.org/browse/TEIID-4422?page=com.atlassian.jira.plugin... ]
Don Krapohl commented on TEIID-4422:
------------------------------------
That's it exactly. Thanks for getting to it quickly!
> Impala Translator - add pushdown support for concat and concat_ws functions
> ---------------------------------------------------------------------------
>
> Key: TEIID-4422
> URL: https://issues.jboss.org/browse/TEIID-4422
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 9.0.2
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> As a consumer I need the concat and concat_ws function definitions with matching signatures in line with http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp...
> concat:
> concat(string a, string b...)
> Purpose: Returns a single string representing all the argument values joined together.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
> concat_ws:
> concat_ws(string sep, string a, string b...)
> Purpose: Returns a single string representing the second and following argument values joined together, delimited by a specified separator.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4422) Impala Translator - add pushdown support for concat and concat_ws functions
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4422?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4422:
---------------------------------------
Have a look and see if https://github.com/teiid/teiid/commit/6dec6af3c08154757dbab6ab58e80d2b780... meets your needs. It doesn't alter the Teiid system functions, but does update the impala support.
> Impala Translator - add pushdown support for concat and concat_ws functions
> ---------------------------------------------------------------------------
>
> Key: TEIID-4422
> URL: https://issues.jboss.org/browse/TEIID-4422
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Connector
> Affects Versions: 9.0.2
> Reporter: Don Krapohl
> Assignee: Steven Hawkins
>
> As a consumer I need the concat and concat_ws function definitions with matching signatures in line with http://www.cloudera.com/documentation/archive/impala/2-x/2-0-x/topics/imp...
> concat:
> concat(string a, string b...)
> Purpose: Returns a single string representing all the argument values joined together.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
> concat_ws:
> concat_ws(string sep, string a, string b...)
> Purpose: Returns a single string representing the second and following argument values joined together, delimited by a specified separator.
> Return type: string
> Usage notes: concat() and concat_ws() are appropriate for concatenating the values of multiple columns within the same row, while group_concat() joins together values from different rows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-4430) Update the Olingo library to 4.3
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4430:
-----------------------------------
Summary: Update the Olingo library to 4.3
Key: TEIID-4430
URL: https://issues.jboss.org/browse/TEIID-4430
Project: Teiid
Issue Type: Task
Components: OData
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 9.1
Upgrade the Olingo to 4.3 version. This is currently in beta but will be in final by the time 9.1 releases. Also this is required for $expand and future data aggregation capabilities.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months