[
https://issues.apache.org/jira/browse/DRILL-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8131:
--------------------------------
Description:
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.
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.
was:
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. . Both queries go
through Drill views, the definitions of which are attached to this issue. They
are both only projections.
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.
> 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.
> 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)
