Error in executing the updateable Internal Materialised view

[vivedha]

Hi all,

I am working on Internal Materialised view.

If I execute this command on the VDB

CALL SYSADMIN.refreshMatViewRow(viewname=>'RESTView.Air_Travel', key=>3);

It is showing error as

java.lang.String cannot be cast to java.lang.Integer

As per the cache guide, I have set the cache to be updateable and set the primary key for the view.What should I give for key value?Is it the primary key value?

The error in Server log:

19:02:50,825 INFO  [MATVIEWS] Refreshing row '3' for materialized view RESTView.Air_Travel.

19:02:50,876 ERROR [PROCESSOR] Unexpected exception for request zSTOp2lwpjxX.0

java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer

        at java.lang.Integer.compareTo(Unknown Source)

        at org.teiid.query.sql.symbol.Constant.compare(Constant.java:249)

        at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:177)

        at org.teiid.query.processor.relational.ListNestedSortComparator.compare(ListNestedSortComparator.java:59)

        at java.util.Collections.indexedBinarySearch(Unknown Source)

        at java.util.Collections.binarySearch(Unknown Source)

        at org.teiid.common.buffer.SPage.search(SPage.java:139)

        at org.teiid.common.buffer.STree.find(STree.java:244)

        at org.teiid.common.buffer.STree.insert(STree.java:289)

        at org.teiid.query.tempdata.TempTable.updateTuple(TempTable.java:773)

        at org.teiid.query.tempdata.GlobalTableStoreImpl.updateMatViewRow(GlobalTableStoreImpl.java:297)

        at org.teiid.query.tempdata.TempTableDataManager.handleSystemProcedures(TempTableDataManager.java:334)

        at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:155)

        at org.teiid.query.tempdata.TempTableDataManager.registerRequest(TempTableDataManager.java:134)

        at org.teiid.query.processor.relational.AccessNode.registerRequest(AccessNode.java:367)

        at org.teiid.query.processor.relational.AccessNode.open(AccessNode.java:156)

        at org.teiid.query.processor.relational.RelationalNode.open(RelationalNode.java:256)

        at org.teiid.query.processor.relational.RelationalPlan.open(RelationalPlan.java:167)

        at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:182)

        at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:126)

        at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:105)

        at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:147)

        at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:375)

        at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:288)

        at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:49)

        at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:216)

        at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:244)

        at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)

        at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at java.lang.Thread.run(Unknown Source)

[rareddy]

yes, you should provide primary key value. Looks like your Pk definition type and submitted value type do not match.

[shawkins]

Even if the types don't match this exception is not expected.  I don't see this behavior on latest - what version are you using and what is the type of your primary key column?

[vivedha]

Ramesh,

Thanks for the response

I checked the Primary key type and there is no type mismatch.I think there is a pattern in the error

If I deploy the VDB for the first time, the refresh is working(though I guess it refreshes the entire table not a single row as said in caching guide) but when I do a refresh again I get this error.

java.lang.String cannot be cast to java.lang.Integer

[vivedha]

Steve,
Thanks for the response
I am using Teiid designer 7.8 and Teiid runtime 7.7.5 in Eclipse indigo 4.2.1 JBoss EDS-5.3.1 GA,JBOSS SOA 5.3.1 GA
I checked the Primary key type it is integer and there is no type mismatch.I think there is a pattern in the error
If I deploy the VDB for the first time, the refresh is working(though I guess it refreshes the entire table not a single row as said in caching guide) but when I do a refresh again I get this error.

java.lang.String cannot be cast to java.lang.Integer

[shawkins]

> If I deploy the VDB for the first time, the refresh is working(though I guess it refreshes the entire table not a single row as said in caching guide) but when I do a refresh again I get this error.

If the internal materialization table has not yet been created the refresh call should just return -1 indicating that it's in an invalid state.

Could you try your scenario against 8.4 or make a small reproducing case, since I wasn't able to get the same error against latest?

[vivedha]

Hi steve,

Sorry for the delayed response.

I am using EDS 5.3.1 GA and SOA 5.3.1 will it be compatible with teiid runtime 8.4? My IDE is Eclipse indigo 4.2 and teiid designer 7.8.
Until now my understanding is that teiid runtime comes with the EDS, because my EDS had teiid 7.7.5 in it and I am using it currently.
If I can change the teiid runtime please guide me how to do it.

[rareddy]

Teiid runtime 8.4 is not compatible with EDS 5.3.1, it will be EDS 6. The runtime in EDS can not be upgraded. If you are RedHat customer you should log ticket for support.

[shawkins]

I can reproduce this behavior on 7.7.x (in a slightly different scenario where the view has a numeric key and I'm using a string in the refresh call), but not on latest.  So this was addressed along the way and would need to be backported for inclusion in a product roll-up patch to make it into EDS 5.3.  You should contact GSS to escalate the issue.

Steve

[vivedha]

Thanks for the reply Steven & Ramesh,

When I keep the first column as the primary key(int) it is working fine.I think the Teiid assumes the first column as the primary key and since in my original issue first column being a string I got this error.