[JBoss JIRA] (TEIID-2977) class cast exception with odata json format function results
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2977?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2977.
-----------------------------------
Resolution: Done
Changed the collection builders to use the component type rather than the collection type.
> class cast exception with odata json format function results
> ------------------------------------------------------------
>
> Key: TEIID-2977
> URL: https://issues.jboss.org/browse/TEIID-2977
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.4
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> If the json format is requested for function/stored procedure results, the json formatting logic will through a class cast:
> 14:56:38,642 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16013 Error occured producing OData result.: java.lang.ClassCastException: org.odata4j.core.OComplexObjects$OComplexObjectImpl cannot be cast to org.odata4j.core.OCollection at org.odata4j.format.json.JsonFormatWriter.writeValue(JsonFormatWriter.java:145) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:38) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:14) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2977) class cast exception with odata json format function results
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2977:
-------------------------------------
Summary: class cast exception with odata json format function results
Key: TEIID-2977
URL: https://issues.jboss.org/browse/TEIID-2977
Project: Teiid
Issue Type: Bug
Components: OData
Affects Versions: 8.4
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.7.1, 8.8
If the json format is requested for function/stored procedure results, the json formatting logic will through a class cast:
14:56:38,642 ERROR [org.teiid.ODATA] (http-localhost/127.0.0.1:8080-1) TEIID16013 Error occured producing OData result.: java.lang.ClassCastException: org.odata4j.core.OComplexObjects$OComplexObjectImpl cannot be cast to org.odata4j.core.OCollection at org.odata4j.format.json.JsonFormatWriter.writeValue(JsonFormatWriter.java:145) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:38) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at org.odata4j.format.json.JsonCollectionFormatWriter.writeContent(JsonCollectionFormatWriter.java:14) [odata4j-core-0.8.0-SNAPSHOT-redhat.jar:] at
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ]
Van Halbert commented on TEIID-2976:
------------------------------------
That should be good. This will get some good user testing next week.
> Using new database logging extension, getting error that indicates column isn't long enough
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-2976
> URL: https://issues.jboss.org/browse/TEIID-2976
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 8.7.1
>
>
> Getting the following sporadically:
> 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement:
> insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2976.
---------------------------------
Fix Version/s: 8.7.1
Resolution: Done
Changed the tansactionId column size to 100
> Using new database logging extension, getting error that indicates column isn't long enough
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-2976
> URL: https://issues.jboss.org/browse/TEIID-2976
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Critical
> Fix For: 8.7.1
>
>
> Getting the following sporadically:
> 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement:
> insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-2976:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Using new database logging extension, getting error that indicates column isn't long enough
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-2976
> URL: https://issues.jboss.org/browse/TEIID-2976
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Critical
>
> Getting the following sporadically:
> 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement:
> insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2976?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-2976:
-------------------------------------
Do you think changing the column size to 100 will suffice?
> Using new database logging extension, getting error that indicates column isn't long enough
> -------------------------------------------------------------------------------------------
>
> Key: TEIID-2976
> URL: https://issues.jboss.org/browse/TEIID-2976
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Reporter: Van Halbert
> Assignee: Steven Hawkins
> Priority: Critical
>
> Getting the following sporadically:
> 11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement:
> insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2976) Using new database logging extension, getting error that indicates column isn't long enough
by Van Halbert (JIRA)
Van Halbert created TEIID-2976:
----------------------------------
Summary: Using new database logging extension, getting error that indicates column isn't long enough
Key: TEIID-2976
URL: https://issues.jboss.org/browse/TEIID-2976
Project: Teiid
Issue Type: Bug
Components: Server
Reporter: Van Halbert
Assignee: Steven Hawkins
Priority: Critical
Getting the following sporadically:
11:57:57,538 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (pool-2-thread-1) Value too long for column "TRANSACTIONID VARCHAR(50)": "'TransactionImple < ac, BasicAction: 0:ffffc0a80102:307704ce:5388aa39:169 status: ActionStatus.RUNNING >' (103)"; SQL statement:
insert into commandlog (id, applicationname, executionid, modelname, plan, principal, requestid, rowcount, sessionid, sourcecommand, sourcerequestid, sqlcmd, eventtype, logtime, transactionid, translatorname, vdbname, vdbversion) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-168]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2959) Revert Salesforce DDL Option keys
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-2959?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-2959.
---------------------------------
Labels: Beta1 (was: )
Resolution: Done
Reverted to original names
> Revert Salesforce DDL Option keys
> ---------------------------------
>
> Key: TEIID-2959
> URL: https://issues.jboss.org/browse/TEIID-2959
> Project: Teiid
> Issue Type: Bug
> Components: AdminApi
> Affects Versions: 8.7
> Reporter: Mark Drilling
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 8.7.1, 8.8
>
>
> The OPTION keys for Salesforce DDL changed going from 8.6 to 8.7. Example below.
> =================
> 8.6 version
> CONSTRAINT Id_PK PRIMARY KEY(Id),
> CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES ApexPage
> ) OPTIONS (UPDATABLE TRUE, Custom 'false', "Supports Create" 'true', "Supports Delete" 'true', "Supports Merge" 'false', "Supports Query" 'true', "Supports Replicate" 'true', "Supports Retrieve" 'true', "Supports Search" 'false');
> =================
> 8.7 version
> CONSTRAINT Id_PK PRIMARY KEY(Id),
> CONSTRAINT FK_ApexPage_ScontrolId FOREIGN KEY(ScontrolId) REFERENCES importVDBSrcModel.ApexPage (Id)
> ) OPTIONS (UPDATABLE TRUE, custom 'false', supportsCreate 'true', supportsDelete 'true', supportsMerge 'false', supportsQuery 'true', supportsReplicate 'true', supportsRetrieve 'true', supportsSearch 'false');
> =================
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years
[JBoss JIRA] (TEIID-2975) mark the xmloutputfactory as a repairing namespace
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2975?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2975.
-----------------------------------
Resolution: Done
Added a narrow fix that affects incoming sqlxml values from translators that need to be saved to disk. It is possible that we may want to expand this fix in the future to all xmloutputfacties we use depending upon whether udfs or other places in code may be returning child nodes with inherited namespaces. However that will change quite a few expected results as it will add in at least the default namespace declaration, so that was not done yet.
> mark the xmloutputfactory as a repairing namespace
> ---------------------------------------------------
>
> Key: TEIID-2975
> URL: https://issues.jboss.org/browse/TEIID-2975
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.7.10
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.8
>
>
> Avoiding issue similar to [1] in cases of non-steaming xml where using a staxsource. The response is forwarded to the body and effectively loses any namespace declarations that are part of the soap envelope.
> [1]
> [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue13) TEIID30020 Processing exception for request a6bkC44ELQu9.3 'TEIID30151 Error building Source for context item.'. Originally TeiidProcessingException 'The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.' org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source).: org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item.
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:140) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:226) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_71]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_71]
> at java.lang.Thread.run(Thread.java:680) [rt.jar:1.6.0_71]
> Caused by: nu.xom.ParsingException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.
> at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3]
> at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3]
> at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:134) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> ... 7 more
> Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.
> at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:171) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7]
> ... 10 more
> Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years