You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2016/05/31 15:40:13 UTC

[jira] [Commented] (PHOENIX-2267) Disambiguate server jar from phoenix-server module jar

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

Nick Dimiduk commented on PHOENIX-2267:
---------------------------------------

bq. Thanks for PHOENIX-2535. Can we close this as a dup now?

I missed the logic in this conclusion. There will still be a need for better names of the queryserver -related artifacts, even after 2535, right?

> Disambiguate server jar from phoenix-server module jar
> ------------------------------------------------------
>
>                 Key: PHOENIX-2267
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2267
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Priority: Minor
>              Labels: beginner
>
> For installation of Phoenix into the RegionServer, the install documentation says
> {noformat}
> Add the phoenix-[version]-server.jar to the classpath of all HBase region
> server and master and remove any previous version. An easy way to do
> this is to copy it into the HBase lib directory
> {noformat}
> This correctly identifies the server uber jar, but unfortunately the phoenix-server module produces a much smaller jar missing all of the classes from phoenix-core as phoenix-server-<version>.jar. I know people can become confused about this because I've seen that happen. Make the wrong choice during an upgrade and all of the RegionServers will crash upon restart with CNFEs, which is an unfortunate outcome to say the least.
> I'd suggest renaming the phoenix-server module to something else in order to disambiguate between the two.



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