[JBoss JIRA] (TEIID-4433) Google gdata dependency needs to be in its own module
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-4433:
-----------------------------------
Summary: Google gdata dependency needs to be in its own module
Key: TEIID-4433
URL: https://issues.jboss.org/browse/TEIID-4433
Project: Teiid
Issue Type: Task
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Priority: Minor
Fix For: 9.1
Google resource adapter includes the gdata core jar file inside its module, this needs to be pulled into its own module.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (TEIID-2578) add/remove schema elements
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2578:
---------------------------------------
- It looks like we need to put some thought into general support of include/exclude tables across all translators. Just doing after the fact may require quite additional repair such dropping foreign keys.
- Correct me if I'm wrong, but the concept of the exportable DDL form and the internal repository DDL seem to be intermingled. For example we still need to be able to allow a vdb to "refresh" a particular set of imports, so we would need to give the option for export to contain the actual imported metadata or just the equivalent import statements.
- The storage mechanism is only currently effective for lob style storage - do you envision wanting to shred storage into metadata tables? Also for larger vdbs it seems like we may still want the option of splitting the contents based upon schema.
- The change to the SYS xml procedure may be better as quoting schema so that if someone was using (quoted) named parameters it would still work.
- We still have to terminate the session if the vdb is reloaded - or do a lot more work to determine if the change is allowable (such as with the existing DDL support to alter view, trigger, properties, etc.). In the simplest case we just need to have the jdbc client use the autoFailover=true connection property. But in the worst case, such as if the security-domain of the vdb is altered, then the login may no longer be valid.
- The convert vdb utility will only work for vdbs that contain no vdb imports nor source metadata imports, I'm assuming in those cases you expect the user to use a running server.
As for using this DDL via JDBC/ODBC, it doesn't seem like too much of a stretch - it would however be difficult to allow general DDL in procedures or dynamic sql for example. The simplest mechanics would be to use a connection property to determine if we are in an editing mode, then on a parsing failure we'd run the statement through the DDL logic (we'd obviously know the vdb/version context). The issue would be that create table / procedure would need to be against the "current" schema which wouldn't be saved if we simply terminated the connection. We could just make that part of the client state and implement the Connection.get/setSchema methods - as well as another SET statement override that does the same. There is also the issue of permissioning however. Our default assumption with existing vdbs, which is permissions are enforced only if data roles are defined, doesn't seem valid in this paradigm. In general we need to check the operations against the role system, just as we do currently for things like alter view. So we may need to have the create vdb operation convey that the vdb is in edit mode, make the user assign data roles, etc.
> add/remove schema elements
> --------------------------
>
> Key: TEIID-2578
> URL: https://issues.jboss.org/browse/TEIID-2578
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Fix For: 9.1
>
>
> Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime.
--
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:
---------------------------------------
> The materialized views fetched perfectly with teiid 8.11.3, once we migrated to 9.0.0, we start having this issue. We went back to 8.11.3 the issue is no longer reproduced.
There are still a few details that are missing here. It matters how the Teiid metadata for the Oracle materialization table is defined. Can you provide the Teiid DDL (not the Oracle DDL) for the Oracle source schema and how it was created (such as providing the vdb.xml)? Somehow you are saying that in 8.11.3 the source table is being defined in Teiid like:
CREATE FOREIGN TABLE G1(e1 integer, e2 varchar);
But in 9.0+ as:
CREATE FOREIGN TABLE G1(e1 bigdecimal, e2 varchar);
> if you are saying NUMBER(10) in Oracle represents bigdecimal or long. What is the oracle datatype expected for Integer in this case?
There isn't one directly as Oracle does not have an integral type. I'm saying that with the Teiid Oracle importer and the property importer.useIntegralTypes=true NUMBER(9) will be imported as the Teiid integer type - but it's not clear to me yet what import mechanism you are using.
> 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 Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-4427:
----------------------------------
The oracle materialized table is created via DDL, the columns and their data types are got from ResultSetMetaDataImpl from Teiid StatementImpl
The materialized views fetched perfectly with teiid 8.11.3, once we migrated to 9.0.0, we start having this issue. We went back to 8.11.3 the issue is no longer reproduced.
if you are saying NUMBER(10) in Oracle represents bigdecimal or long. What is the oracle datatype expected for Integer in this case?
> 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-4325) ASSERTION FAILED: expected reference to be not null
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4325?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4325:
---------------------------------------
> We are using Teiid JDBC Driver version 8.12 (8/12)
The fix does not affect the client, just the server/embedded side. Is is possible that a later version of Teiid can be used?
> 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:
---------------------------------------
The DDL I'm showing is specifically the Teiid DDL - how are you creating the metadata for the oracle materialized table target? Translator import, Designer, DDL? With the Teiid Oracle import NUMBER(10) will be represented by bigdecimal by default. If the useIntegralTypes import option is used, NUMBER(10) would be represented by a long. Either way it wouldn't match the expectation of the view. I'm still trying to understand how this would have worked in 8.11, but not 9.
> 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 Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-4427?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-4427:
----------------------------------
My materialized view is on Oracle:
The case is only reproducible on Oracle and when using date functions like *year*, *month*, *TIMESTAMPDIFF*,...
The materialized view is successfully populated with data.
The data type of the corresponding column in Oracle materialized view is *Number(10)*
When fetching the view the exception is raised
CREATE TABLE G1(e1 NUMBER(10), e2 VARCHAR2 (255));
CREATE VIEW G2 OPTIONS (MATERIALIZED 'true', MATERIALIZED_TABLE 'pm1.G1') AS SELECT *month(CURDATE())* as e1, e2 FROM pm1.G1;
> 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-4325) ASSERTION FAILED: expected reference to be not null
by Mark Tawk (JIRA)
[ https://issues.jboss.org/browse/TEIID-4325?page=com.atlassian.jira.plugin... ]
Mark Tawk commented on TEIID-4325:
----------------------------------
Chenna,
I kept the query as is, integrating Steven fix in the source code have fixed the problem.
But I was using Teiid 9.0.0
> 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