You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/10/31 22:27:58 UTC

[jira] [Reopened] (PHOENIX-3426) Upgrade to Apache Avatica 1.9.0

     [ https://issues.apache.org/jira/browse/PHOENIX-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser reopened PHOENIX-3426:
---------------------------------

[~jamestaylor] pinged me via email that I busted QueryServerBasicsIT with this upgrade.

In my attempts to simplify some of the shading that we were doing across Avatica and Phoenix, I broke things (turns out trying to get protobuf2 and protobuf3 on the test-classpath is tricky).

Patch incoming.

> Upgrade to Apache Avatica 1.9.0
> -------------------------------
>
>                 Key: PHOENIX-3426
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3426
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: 4.9.0
>
>         Attachments: PHOENIX-3426.001.patch
>
>
> Apache Avatica 1.9.0 has hit maven central. We should upgrade to let PHOENIX-3004 get in.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)