[JBoss JIRA] (TEIID-4412) Incorrectly handling when trying to update attribute that is the primar key
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4412?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-4412:
------------------------------------
I think this can be closed, as the new logic will now throw an exception when the primary key is trying to be changed. It indicates that the object must be deleted and then readded.
> Incorrectly handling when trying to update attribute that is the primar key
> ---------------------------------------------------------------------------
>
> Key: TEIID-4412
> URL: https://issues.jboss.org/browse/TEIID-4412
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 9.1
> Reporter: Van Halbert
> Assignee: Van Halbert
> Priority: Critical
>
> The current logic doesn't handle when the attribute being updated is also the primary key. The metadata from a dynamic vdb indicates this attribute to be updatable.
> (1) I'm thinking the problem is that the attribute that is the primary key should not be updatable, but in order to be changed, the object should be deleted and re-added.
> (2) Or, would the preferred way to handle this is to allow it to be updatable, but change the logic to check when this attribute is changing and internally perform a delete and re-add.
> I like option (1) because the user is in control, where (2) is done under the covers.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4431) ASSERTION FAILED: expected reference to be not null
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4431?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4431.
-----------------------------------
Resolution: Out of Date
Given that there were no updates we'll presume that this was resolved by TEIID-4325
> 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
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4745) Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file'
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4745?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4745:
----------------------------------
Component/s: Query Engine
Fix Version/s: 10.x
Adding into 10.x to recommend a solution related to cdc for file modifications or to investigate a more integrated approach to using hsql text tables.
> Avoid loading the same file over again when using 'org.jboss.teiid.resource-adapter.file'
> -----------------------------------------------------------------------------------------
>
> Key: TEIID-4745
> URL: https://issues.jboss.org/browse/TEIID-4745
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Environment: * WildFly 10
> * Teiid Server 9.1.2
> * CentOs 7
> Reporter: Pedro Inácio
> Assignee: Steven Hawkins
> Fix For: 10.x
>
>
> When using the file resource adapter _org.jboss.teiid.resource-adapter.file_, it should be possible that the system per se, by the means of a new property in the resource-adapter, or other option in the view definition, or other configuration elsewhere, to not to unnecessary load a file that is already loaded. Theoretically it should be possible, for example, to check the file date or the file checksum, to see if the file is already loaded by _Teiid_. If it is, then there is no need to parse the file again.
> This is important due to, specially, performance improvements. If there are a lot of files to be processed, and these files are big (200 MB or more), the system will be processing over and over again the same files if they are not updated for quite some time.
> If, for example, the user uses a Materialized View, then the view will be constantly being updated with the same data, which brings another performance penalty.
> *Note*: This could be extended to other resource-adapters with some sort of last data date for example, if the user whant to use this sort of mechanism. For example, if using a database like MySQL as source, then tthe user could define a last update table, and the system could do a check first against this table before tryng to load the data.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4799) Accessing a JDBC source via ODATA creates stack trace in log
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4799?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4799.
-----------------------------------
Resolution: Cannot Reproduce Bug
> Accessing a JDBC source via ODATA creates stack trace in log
> -------------------------------------------------------------
>
> Key: TEIID-4799
> URL: https://issues.jboss.org/browse/TEIID-4799
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Attachments: stacktrace.txt
>
>
> When doing a get to a odata endpoint that will use a jdbc connection in data virtualization, there will be a transaction related stacktrace in the logs. This does not seem to create a problem but is confusing.
> Version-Release number of selected component (if applicable):
> 8.12.x
> How reproducible:
> Steps to Reproduce:
> 1. Add a JDBC datasource model in the Teiid Design Perspective
> 2. Add a Teiid Metadata view model using the JDBC source model
> 3. Deploy the view model in a VDB
> 4. Access the view model via an odata call
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4851) Random errors about PostGIS without using it
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4851?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-4851.
-----------------------------------
Resolution: Incomplete Description
Not enough to determine what was being seen.
> Random errors about PostGIS without using it
> --------------------------------------------
>
> Key: TEIID-4851
> URL: https://issues.jboss.org/browse/TEIID-4851
> Project: Teiid
> Issue Type: Bug
> Components: JDBC Connector
> Affects Versions: 8.12.8.6_3
> Environment: Squirrel v3.7
> Teiid JDBC 8.13.1
> JDV 6.3.4
> PostgreSQL 9.6
> Reporter: Madou Coulibaly
> Assignee: Steven Hawkins
>
> When I issue queries using SQuirrel, I get the following error at random whereas I do not use any Geo functions:
> Originally TeiidProcessingException 'ERROR: function postgis_full_version() does not exist
> Hint: No function matches the given name and argument types. You might need to add explicit type casts.
> Position: 8' QueryExecutorImpl.java:2455. Enable more detailed logging to see the entire stacktrace.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4895) Determine community requirements for WildFly usage
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4895?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4895:
----------------------------------
Fix Version/s: 10.0
> Determine community requirements for WildFly usage
> --------------------------------------------------
>
> Key: TEIID-4895
> URL: https://issues.jboss.org/browse/TEIID-4895
> Project: Teiid
> Issue Type: Task
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 10.0
>
>
> WildFly is typically the runtime for Teiid. However we want feedback from the community on what style of WildFly integration is important:
> - The ability to deploy Teiid into a managed WildFly instance/cluster
> - The combination Teiid/WildFly artifact
> - A layered docker image
> - Not full WildFly, just Swarm
> - Not needed, just Embedded
> Based upon this we can better tune our documentation, downloads, and examples.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-5077) Couchbase strange behaviour for long numbers
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5077?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5077:
---------------------------------------
What resolution are you comfortable with:
1. Just document the issue
2. Add an import option (or execution property) to only use "safe" numeric types - which could exclude biginteger, long, and bigdecimal. As an execution property we'd also exclude those conversions from pushdown as well.
> Couchbase strange behaviour for long numbers
> --------------------------------------------
>
> Key: TEIID-5077
> URL: https://issues.jboss.org/browse/TEIID-5077
> Project: Teiid
> Issue Type: Bug
> Components: Documentation, Misc. Connectors
> Affects Versions: 8.12.x-6.4
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
> Priority: Critical
> Fix For: 10.0
>
>
> There is a strange limitation for storing large numbers (e.g. modelled as long) in Couchbase.
> https://forums.couchbase.com/t/strange-behavior-when-saving-big-long-numb...
> The same behaviour with value: 28341791043587382
> which is being stored and retreived as: 28341791043587384
> I feel we need to document this behaviour and provide hints how to overcome it. (Modelling of the column as string on Couchbase's side and defining a view).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months
[JBoss JIRA] (TEIID-4012) Implement XA transaction support for Teiid ODBC
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4012?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4012:
----------------------------------
Fix Version/s: 10.x
(was: 10.0)
> Implement XA transaction support for Teiid ODBC
> -----------------------------------------------
>
> Key: TEIID-4012
> URL: https://issues.jboss.org/browse/TEIID-4012
> Project: Teiid
> Issue Type: Feature Request
> Components: ODBC
> Affects Versions: 8.7.1.6_2
> Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP6.4.0 patched to version 6.4.5,
> JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157
> 64-bit Windows 7 environment
> Reporter: Steve Tran
> Assignee: Steven Hawkins
> Fix For: 10.x
>
>
> Without XA support the pg client will hit the following error:
> TEIID30020 Processing exception for request ... 'Group does not exist: pg_prepared_xacts'
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 7 months