[JBoss JIRA] (TEIID-3034) Add support for OData query parameters
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3034?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3034.
---------------------------------
> Add support for OData query parameters
> --------------------------------------
>
> Key: TEIID-3034
> URL: https://issues.jboss.org/browse/TEIID-3034
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.4.1
> Reporter: Greg MacKinnon
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> There are some OData v2 query parameters that don't appear to work as of Teiid 8.7 (please see teiid forum thread 241566 on this topic). I believe these are all OData v2 conventions.
> ?$inlineCount=allpages&$top=N : always returns count = $top
> $expand : does not appear to work (but no ostensible error)
> $count : "TEIID30088 Unrelated order by column g0.SYSID cannot be used in a SET query, with SELECT DISTINCT, or GROUP BY" occurs using this URI pattern entity/$count , per the OData documentation for using this parameter
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-3214) Dynamic vdb is redeployed twice
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3214?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3214.
---------------------------------
> Dynamic vdb is redeployed twice
> -------------------------------
>
> Key: TEIID-3214
> URL: https://issues.jboss.org/browse/TEIID-3214
> Project: Teiid
> Issue Type: Bug
> Reporter: Jan Stastny
> Assignee: Steven Hawkins
>
> I have a dynamic vdb. When I redeploy it with command 'touch vdbname-vdb.xml.deployed' then the vdb is redeployed twice within 5 seconds. Whole the procedure runs twice - see the log in the end of description. When the vdb is redeployed by 'touch vdbname-vdb.xml' everything is fine. Happens only with dynamic vdbs, static vdbs and wars,etc work fine.
> Log:
> 09:23:13,599 INFO [org.teiid.RUNTIME] (MSC service thread 1-4) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 7ms
> 09:23:13,604 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:13,629 INFO [org.teiid.SECURITY] (MSC service thread 1-1) TEIID40009 Admin [null] is terminating this session: ItnNDZmYCq/y.
> 09:23:13,633 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:13,634 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 3) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:13,636 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,683 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018562: Redeployed "mat-views-vdb.xml"
> 09:23:13,840 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:13,846 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB mat-views.1 is set to ACTIVE
> 09:23:18,757 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID50026 VDB "mat-views.1[Source{Source=Source, h2-override, java:/mat-views-ds}, View{}]" undeployed.
> 09:23:18,760 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment mat-views-vdb.xml (runtime-name: mat-views-vdb.xml) in 4ms
> 09:23:18,761 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "mat-views-vdb.xml" (runtime-name: "mat-views-vdb.xml")
> 09:23:18,789 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "Source" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,791 INFO [org.teiid.RUNTIME] (MSC service thread 1-8) TEIID50029 VDB mat-views.1 model "View" metadata is currently being loaded. Start Time: 11/13/14 9:23 AM
> 09:23:18,795 INFO [org.teiid.CONNECTOR] (teiid-async-threads - 2) H2ExecutionFactory Commit=true;DatabaseProductName=H2;DatabaseProductVersion=@PROJECT_VERSION@ (2012-07-13);DriverMajorVersion=1;DriverMajorVersion=3;DriverName=H2 JDBC Driver;DriverVersion=@PROJECT_VERSION@ (2012-07-13);IsolationLevel=2
> 09:23:18,807 INFO [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID50030 VDB mat-views.1 model "View" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:18,820 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "mat-views-vdb.xml" with deployment "mat-views-vdb.xml"
> 09:23:18,999 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB mat-views.1 model "Source" metadata loaded. End Time: 11/13/14 9:23 AM
> 09:23:19,005 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB mat-views.1 is set to ACTIVE
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-3153) Allow to write stream data with large size (>10G)
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3153?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3153.
---------------------------------
> Allow to write stream data with large size (>10G)
> -------------------------------------------------
>
> Key: TEIID-3153
> URL: https://issues.jboss.org/browse/TEIID-3153
> Project: Teiid
> Issue Type: Enhancement
> Components: Server
> Reporter: Haifen Bi
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> We have quite large size of data file (>10G) that needs to be sent back to server from client. Following is JDBC client code:
> void writeData(int id) {
> String sql = "UPDATE DataSet set data = ? WHERE id = ?";
> try {
> InputStream is = new FileInputStream("c:\\temp\\data");
> this.ps = connection.prepareStatement(sql);
> this.ps.setBlob(1, is);
> this.ps.setInt(2, id);
> ps.executeUpdate();
> } catch (Exception e) {
> ..
> }
> }
> Teiid throws "lob too big" error when executing above code:
> 10:01:18,801 WARN [org.teiid.TRANSPORT] (New I/O worker #1) TEIID40113 Unhandled exception, aborting operation: java.io.StreamCorruptedException: lob too big:
> 429496456065534 (max: 4294967296)
> at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:142) [teiid-runtime-8.7.0.Final.jar:8.7.0.Final]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) [netty-3.6.2.Final.jar:]
> at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:310) [netty-3.6.2.Final.jar:]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.2.Final.jar:]
> at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.2.Final.jar:]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.2.Final.jar:]
>
> It seemed teiid has stream data size limit (4G?). With this limitation, it is not possible to send more than 4G of stream data in Teiid.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-2959) Revert Salesforce DDL Option keys
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2959?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2959.
---------------------------------
> 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.8, 8.7.1
>
>
> 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.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-3074) NPE When using External Materialization management is use
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3074?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3074.
---------------------------------
> NPE When using External Materialization management is use
> ---------------------------------------------------------
>
> Key: TEIID-3074
> URL: https://issues.jboss.org/browse/TEIID-3074
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.5
> Reporter: Ramesh Reddy
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
> Attachments: debug_plan.txt, solr-integration-with-matview-vdb.xml
>
>
> When I was issuing query that has externalized materialization with management option to true, I am seeing NPE. Tried to see why NPE is occurring was not able to figure out (yet)
> {code}
> 14:37:50,269 ERROR [org.teiid.CONNECTOR] (Worker1_QueryProcessorQueue8477) 0z97J5OWq7x9 Connector worker process failed for atomic-request=0z97J5OWq7x9.7.1.4220: java.lang.NullPointerException
> at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:338)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:385) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:203) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:301) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha1-SNAPSHOT.jar:8.9.0.Alpha1-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-2885) Allow dependent join pushdown to be chosen by the planner
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2885?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2885.
---------------------------------
> Allow dependent join pushdown to be chosen by the planner
> ---------------------------------------------------------
>
> Key: TEIID-2885
> URL: https://issues.jboss.org/browse/TEIID-2885
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> As a follow on to TEIID-2249, the planner should be able to choose when to use full join pushdown, rather than only relying upon a hint. One downside to this currently is that there isn't a good way to do a back off to a different join processing (unless we embedded an alternative plan) and so we may have to add failure logic if too many independent values are retrieved.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-2916) HIVE2: Teiid didn't translate the SQL correctly for numeric field
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2916?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2916.
---------------------------------
> HIVE2: Teiid didn't translate the SQL correctly for numeric field
> ------------------------------------------------------------------
>
> Key: TEIID-2916
> URL: https://issues.jboss.org/browse/TEIID-2916
> Project: Teiid
> Issue Type: Sub-task
> Components: Misc. Connectors
> Affects Versions: 8.6
> Environment: HIVE2 with Teiid
> Reporter: Ivan Chan
> Assignee: Ramesh Reddy
> Labels: Teiid, alpha1
> Fix For: 8.8, 8.7.1
>
>
> Teiid didn't translate the SQL correctly for numeric field. It uses identifier "decimal" in the SQL which is not supported by the driver.
> Original Query:
> select "store_sales",
> "store_state",
> "store_country"
> from "Impala"."sales_new"
> where "store_sales" between 1.5 and 10
> limit 1000
> After Translation (Teiid):
> SELECT g_0.store_sales AS c_0, g_0.store_state AS c_
> 1, g_0.store_country AS c_2 FROM sales_new g_0 WHERE cast(g_0.store_sales AS
> decimal) >= 1.5 AND cast(g_0.store_sales AS decimal) <= 10 LIMIT 1000
> "decimal" is not supported identifier in HIVE driver:
> Encountered: IDENTIFIER
> Expected: BIGINT, BOOLEAN, DATE, DATETIME, REAL, FLOAT, INTEGER, SMALLINT,
> STRING, TIMESTAMP, TINYINT
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months