[
https://issues.apache.org/jira/browse/DRILL-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17491158#comment-17491158
]
ASF GitHub Bot commented on DRILL-8131:
---------------------------------------
vvysotskyi opened a new pull request #2459:
URL: https://github.com/apache/drill/pull/2459
# [DRILL-8131](https://issues.apache.org/jira/browse/DRILL-8131): Infinite
planning when JDBC or Phoenix plugin is enabled
## Description
Prevented applying JDBC and Phoenix rules for DRILL_PHYSICAL rel nodes.
Updated JDBC limit rule to be applied only for limits that weren't pushed
down, and split limit into several ones for the case of MSSql database instead
of relying on splitting it later during physical optimizations.
## Documentation
NA
## Testing
Added unit test, checked more complex cases manually.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Infinite planning when storage-phoenix is enabled
> -------------------------------------------------
>
> Key: DRILL-8131
> URL: https://issues.apache.org/jira/browse/DRILL-8131
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Phoenix
> Affects Versions: 1.20.0
> Reporter: James Turton
> Assignee: James Turton
> Priority: Blocker
> Fix For: 1.20.0
>
> Attachments: phoenix-table-profile.json, phoenix-table-profile.log,
> profiles-query-profile.json, profiles-query-profile.log, profiles.view.drill,
> pulsar_e2e_test.view.drill
>
>
> With a connection to Phoenix Query Server using either storage-jdbc or
> storage-phoenix, two queries fail after an infinite planning loop. One query
> is against the Phoenix QS (c.f. phoenix-table-* attachments), the other does
> not involve Phoenix at all and queries Parquet in HDFS (c.f. profiles-query-*
> attachments). Both queries go through Drill views, the definitions of which
> are attached to this issue. They are both only projections.
> Software versions in the environment where the bug exists: Hadoop 2, Phoenix
> 4.15.0 with hbase 1.5.0 and phoenix-queryserver 1.0.0. Downgrading Drill's
> phoenix-queryserver-client jar from 6.0.0 to 1.0.0 to accommodate this PQS
> version does not remediate the problem.
> Storage-jdbc config.
> {code:java}
> {
> "type": "jdbc",
> "driver": "org.apache.phoenix.queryserver.client.Driver",
> "url":
> "jdbc:phoenix:thin:url=http://localhost:8765;serialization=PROTOBUF;authentication=SPNEGO;principal=drill/[email protected];keytab=/etc/hadoop/conf/drill.keytab";,
> "writerBatchSize": 10000,
> "enabled": true
> }{code}
> The same storage-jdbc config is deployed in Drill 1.16 environments which do
> not exhibit this infinite planning bug.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
