[ 
https://issues.apache.org/jira/browse/DRILL-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579619#comment-17579619
 ] 

ASF GitHub Bot commented on DRILL-8279:
---------------------------------------

jnturton commented on PR #2622:
URL: https://github.com/apache/drill/pull/2622#issuecomment-1214844957

   @vvysotskyi even though we've only seen this Avatica conflict affect Drill 
master after the Calcite upgrade was merged, do I understand correctly that it 
also lies latent the 1.20 branch? If so then my thinking is that this change 
should be backported even though it represents a type of breaking change for 
existing users of PQS. Anyone on 1.20.x who needs to continue with PQS to the 
extent that they are willing to roll the classloader dice (I'd like to hope 
that this is no one) could still manually replace their Phoenix plugin with a 
download of drill-storage-phoenix-1.20.2.jar, the last version to be based on 
PQS, or just remain stuck on 1.20.2 until they can coordinate an upgrade...




> Use thick Phoenix driver
> ------------------------
>
>                 Key: DRILL-8279
>                 URL: https://issues.apache.org/jira/browse/DRILL-8279
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Vova Vysotskyi
>            Assignee: Vova Vysotskyi
>            Priority: Major
>
> phoenix-queryserver-client shades Avatica classes, so it causes issues when 
> starting Drill and shaded class from phoenix jars is loaded before, so Drill 
> wouldn't be able to start correctly.
> To avoid that, phoenix thick client can be used, it also will improve query 
> performance.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to