[JBoss JIRA] (TEIIDSB-186) Fix to use only use alias name from ExternalSource
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-186?focusedWorklogId=12450841&pa... ]
Ramesh Reddy logged work on TEIIDSB-186:
----------------------------------------
Author: Ramesh Reddy
Created on: 16/Apr/20 4:09 PM
Start Date: 16/Apr/20 4:09 PM
Worklog Time Spent: 5 hours
Issue Time Tracking
-------------------
Time Spent: 4 days, 2 hours (was: 3 days, 5 hours)
Worklog Id: (was: 12450841)
> Fix to use only use alias name from ExternalSource
> --------------------------------------------------
>
> Key: TEIIDSB-186
> URL: https://issues.redhat.com/browse/TEIIDSB-186
> Project: Teiid Spring Boot
> Issue Type: Quality Risk
> Components: core
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.5.0
>
> Time Spent: 4 days, 2 hours
> Remaining Estimate: 0 minutes
>
> As the code progressed the usage of translator name and alias name from ExternalSource class is interchangeably used. This is leading to confusion in terms of development and documents.
> Need to fix all the places where the translator name used to use alias name with Spring Boot engine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5935) S3 support for ceph
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5935?page=com.atlassian.jira.plugi... ]
Steven Hawkins commented on TEIID-5935:
---------------------------------------
For future reference getting ceph going with docker/podman isn't very idiot proof. There older demo is out-of-date and they refer users now to a docker launch that is referenced in there travis build. That looks something like:
export RGW_FRONTEND_TYPE=civetweb
export CEPH_FLAVOR=master
export CENTOS_RELEASE=8
sudo podman run -d --name ceph-demo -v /etc/modprobe.d:/etc/modprobe.d -e RGW_FRONTEND_TYPE="${RGW_FRONTEND_TYPE}" -e BLUESTORE_BLOCK_SIZE=15GB -e DEBUG=verbose -e RGW_FRONTEND_PORT=8000 -e MON_IP=127.0.0.1 -e CEPH_PUBLIC_NETWORK=0.0.0.0/0 -e CLUSTER=test -e CEPH_DEMO_UID=demo -e CEPH_DEMO_ACCESS_KEY=G1EZ5R4K6IJ7XUQKMAED -e CEPH_DEMO_SECRET_KEY=cNmUrqpBKjCMzcfqG8fg4Qk07Xkoyau52OmvnSsz -e CEPH_DEMO_BUCKET=foobar -e SREE_PORT=5001 -e DATA_TO_SYNC=/etc/modprobe.d -e DATA_TO_SYNC_BUCKET=travis ceph/daemon:latest demoO_SECRET_KEY=qqq -e CEPH_DEMO_BUCKET=qqq ceph/daemon demo
However the container will not start for me, so now I'll try an rpm package install.
> S3 support for ceph
> -------------------
>
> Key: TEIID-5935
> URL: https://issues.redhat.com/browse/TEIID-5935
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> We need to validate ceph support against the changes in TEIID-5927. The most immediate issue appears to be that ceph does not support the v2 listing of bucket contents and would need to use an older list method.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIIDSB-190) REST with request payload throws an error
by Ramesh Reddy (Jira)
[ https://issues.redhat.com/browse/TEIIDSB-190?page=com.atlassian.jira.plug... ]
Ramesh Reddy commented on TEIIDSB-190:
--------------------------------------
I do not remember now, it was with implicit VDB usecase. But we can move this to `Spring Http` case only
> REST with request payload throws an error
> -----------------------------------------
>
> Key: TEIIDSB-190
> URL: https://issues.redhat.com/browse/TEIIDSB-190
> Project: Teiid Spring Boot
> Issue Type: Bug
> Components: core
> Reporter: Sadhana Nandakumar
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.5.0
>
>
> TEIID spring boot is expecting the payload to be a bean, and hence throws an error. POST without request body works fine without any issues.
> CREATE VIEW StockPrice (
> symbol string PRIMARY KEY,
> price double
> ) AS
> SELECT p.symbol, y.price
> FROM accounts.PRODUCT as p, TABLE(call invokeHttp(action=>'POST', endpoint=>QUERYSTRING('predict'), headers=>jsonObject('application/json' as "Content-Type"), request=>jsonObject('PLATINUM' as "customerClass"))) as x,
> JSONTABLE(JSONPARSE(x.result,true), '$' COLUMNS price double path '@.data.segment') as y
> No errors on build, when I query the odata endpoint, I see the following error.
> <error xmlns="http://docs.oasis-open.org/odata/ns/metadata">
> <code>TEIID30504</code>
> <message>
> TEIID30504 quotesvc: No bean named '{"customerClass":"PLATINUM"}' available
> </message>
> </error>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5934) Inappropriate aggregate pushdown over nested table join
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5934?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5934.
-----------------------------------
Resolution: Done
There needed to be a deeper check for correlation as the aggregate decomposition logic does not yet support it.
> Inappropriate aggregate pushdown over nested table join
> -------------------------------------------------------
>
> Key: TEIID-5934
> URL: https://issues.redhat.com/browse/TEIID-5934
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> Related to TEIID-5932, a query with multiple lateral joins and a group by is optimized incorrectly. Altering the unit test query to:
> {code}
> SELECT xt.event_id, count(*) FROM tbl AS d,
> TABLE (select d.event_id from tbl limit 1) xt
> LEFT JOIN TABLE (select tbl.str as some_col from tbl where str = 'a' || d.str) xt2
> ON xt.event_id = -1
> group by xt.event_id
> {code}
> Results in a processing error because the initial pushdown for tbl only selects count star and does not select tbl.str.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5934) Inappropriate aggregate pushdown over nested table join
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5934?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5934:
----------------------------------
Fix Version/s: 13.1.1
> Inappropriate aggregate pushdown over nested table join
> -------------------------------------------------------
>
> Key: TEIID-5934
> URL: https://issues.redhat.com/browse/TEIID-5934
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0, 13.1.1
>
>
> Related to TEIID-5932, a query with multiple lateral joins and a group by is optimized incorrectly. Altering the unit test query to:
> {code}
> SELECT xt.event_id, count(*) FROM tbl AS d,
> TABLE (select d.event_id from tbl limit 1) xt
> LEFT JOIN TABLE (select tbl.str as some_col from tbl where str = 'a' || d.str) xt2
> ON xt.event_id = -1
> group by xt.event_id
> {code}
> Results in a processing error because the initial pushdown for tbl only selects count star and does not select tbl.str.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5934) Inappropriate aggregate pushdown over nested table join
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5934?page=com.atlassian.jira.plugi... ]
Steven Hawkins updated TEIID-5934:
----------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
> Inappropriate aggregate pushdown over nested table join
> -------------------------------------------------------
>
> Key: TEIID-5934
> URL: https://issues.redhat.com/browse/TEIID-5934
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0, 13.1.1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Related to TEIID-5932, a query with multiple lateral joins and a group by is optimized incorrectly. Altering the unit test query to:
> {code}
> SELECT xt.event_id, count(*) FROM tbl AS d,
> TABLE (select d.event_id from tbl limit 1) xt
> LEFT JOIN TABLE (select tbl.str as some_col from tbl where str = 'a' || d.str) xt2
> ON xt.event_id = -1
> group by xt.event_id
> {code}
> Results in a processing error because the initial pushdown for tbl only selects count star and does not select tbl.str.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5934) Inappropriate aggregate pushdown over nested table join
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5934?focusedWorklogId=12450838&pag... ]
Steven Hawkins logged work on TEIID-5934:
-----------------------------------------
Author: Steven Hawkins
Created on: 16/Apr/20 11:26 AM
Start Date: 16/Apr/20 11:26 AM
Worklog Time Spent: 3 hours
Issue Time Tracking
-------------------
Remaining Estimate: 1 hour (was: 4 hours)
Time Spent: 3 hours
Worklog Id: (was: 12450838)
> Inappropriate aggregate pushdown over nested table join
> -------------------------------------------------------
>
> Key: TEIID-5934
> URL: https://issues.redhat.com/browse/TEIID-5934
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0, 13.1.1
>
> Original Estimate: 4 hours
> Time Spent: 3 hours
> Remaining Estimate: 1 hour
>
> Related to TEIID-5932, a query with multiple lateral joins and a group by is optimized incorrectly. Altering the unit test query to:
> {code}
> SELECT xt.event_id, count(*) FROM tbl AS d,
> TABLE (select d.event_id from tbl limit 1) xt
> LEFT JOIN TABLE (select tbl.str as some_col from tbl where str = 'a' || d.str) xt2
> ON xt.event_id = -1
> group by xt.event_id
> {code}
> Results in a processing error because the initial pushdown for tbl only selects count star and does not select tbl.str.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5927) S3 translator can not support minIO endpoint
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5927?page=com.atlassian.jira.plugi... ]
Steven Hawkins resolved TEIID-5927.
-----------------------------------
Resolution: Done
Updated the translator and the docs. Specifying a minio endpoint on the underlying source will now be used rather than defaulting to the aws endpoint.
> S3 translator can not support minIO endpoint
> --------------------------------------------
>
> Key: TEIID-5927
> URL: https://issues.redhat.com/browse/TEIID-5927
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Rui Wang
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> When I try to config my on own minIO storage to teiied RA, get following error, seems it tied directly with amazon endpoints, could you pls takes an enhancement to make it generic so it can be used with minio stores. Thanks a lot.
> <resource-adapter id="webservice">
> <module slot="main" id="org.jboss.teiid.resource-adapter.webservice"/>
> <connection-definitions>
> <connection-definition class-name="org.teiid.resource.adapter.ws.WSManagedConnectionFactory" jndi-name="java:/wsDS" enabled="true" use-java-context="true" pool-name="wsDS">
> <config-property name="EndPoint">
> http://myMinioIp:9091/minio/bucket1/
> </config-property>
> </connection-definition>
> </connection-definitions>
> </resource-adapter>
>
>
> Exception in thread "main" org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 web-connector: Error reading the file https://s3.amazonaws.com/bucket1/price.csv; The response code returned 403. Details: <?xml version="1.0" encoding="UTF-8"?>
> <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>minioadmin</AWSAccessKeyId><RequestId>EB7421ECD8EF9B88</RequestId><HostId>m3fHokjXC5shrV+y+2vIHl7KNcr46RvoKRXuZ8TnU4fiZyi1XG6rT9DiTu6yRZfg328QGcr2w+A=</HostId></Error>
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:131)
> at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:67)
> at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:783)
> at org.teiid.jdbc.StatementImpl.access$100(StatementImpl.java:62)
> at org.teiid.jdbc.StatementImpl$2.onCompletion(StatementImpl.java:581)
> at org.teiid.client.util.ResultsFuture.done(ResultsFuture.java:131)
> at org.teiid.client.util.ResultsFuture.access$200(ResultsFuture.java:36)
> at org.teiid.client.util.ResultsFuture$1.receiveResults(ResultsFuture.java:75)
> at org.teiid.net.socket.SocketServerInstanceImpl.receivedMessage(SocketServerInstanceImpl.java:281)
> at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:333)
> at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:423)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:590)
> at org.teiid.jdbc.StatementImpl.executeSql(StatementImpl.java:420)
> at org.teiid.jdbc.StatementImpl.executeQuery(StatementImpl.java:351)
> at com.ibm.vdb.TeiidFile.showVdbInfo(TeiidFile.java:181)
> at com.ibm.vdb.TeiidFile.main(TeiidFile.java:205)
> Caused by: org.teiid.core.TeiidProcessingException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 web-connector: Error reading the file https://s3.amazonaws.com/bucket1/price.csv; The response code returned 403. Details: <?xml version="1.0" encoding="UTF-8"?>
> <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>minioadmin</AWSAccessKeyId><RequestId>EB7421ECD8EF9B88</RequestId><HostId>m3fHokjXC5shrV+y+2vIHl7KNcr46RvoKRXuZ8TnU4fiZyi1XG6rT9DiTu6yRZfg328QGcr2w+A=</HostId></Error>
> at org.teiid.dqp.internal.process.DataTierTupleSource.exceptionOccurred(DataTierTupleSource.java:397)
> at org.teiid.dqp.internal.process.DataTierTupleSource.nextTuple(DataTierTupleSource.java:157)
> at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:401)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.relational.SourceState.prefetch(SourceState.java:207)
> at org.teiid.query.processor.relational.SourceState.rowCountLE(SourceState.java:154)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirectInternal(JoinNode.java:252)
> at org.teiid.query.processor.relational.JoinNode.nextBatchDirect(JoinNode.java:195)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146)
> at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277)
> at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:139)
> at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:147)
> at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:110)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160)
> at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142)
> at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492)
> at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:362)
> at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:43)
> at org.teiid.dqp.internal.process.RequestWorkItem.run(RequestWorkItem.java:285)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:281)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:124)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$2.run(ThreadReuseExecutor.java:212)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.teiid.core.TeiidException: Remote org.teiid.translator.TranslatorException: Error reading the file https://s3.amazonaws.com/bucket1/price.csv; The response code returned 403. Details: <?xml version="1.0" encoding="UTF-8"?>
> <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>minioadmin</AWSAccessKeyId><RequestId>EB7421ECD8EF9B88</RequestId><HostId>m3fHokjXC5shrV+y+2vIHl7KNcr46RvoKRXuZ8TnU4fiZyi1XG6rT9DiTu6yRZfg328QGcr2w+A=</HostId></Error>
> at org.teiid.translator.amazon.s3.S3ProcedureExecution.execute(S3ProcedureExecution.java:114)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:402)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:228)
> at com.sun.proxy.$Proxy43.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:302)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:59)
> ... 6 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (TEIID-5934) Inappropriate aggregate pushdown over nested table join
by Steven Hawkins (Jira)
[ https://issues.redhat.com/browse/TEIID-5934?page=com.atlassian.jira.plugi... ]
Work on TEIID-5934 started by Steven Hawkins.
---------------------------------------------
> Inappropriate aggregate pushdown over nested table join
> -------------------------------------------------------
>
> Key: TEIID-5934
> URL: https://issues.redhat.com/browse/TEIID-5934
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 14.0
>
>
> Related to TEIID-5932, a query with multiple lateral joins and a group by is optimized incorrectly. Altering the unit test query to:
> {code}
> SELECT xt.event_id, count(*) FROM tbl AS d,
> TABLE (select d.event_id from tbl limit 1) xt
> LEFT JOIN TABLE (select tbl.str as some_col from tbl where str = 'a' || d.str) xt2
> ON xt.event_id = -1
> group by xt.event_id
> {code}
> Results in a processing error because the initial pushdown for tbl only selects count star and does not select tbl.str.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months