phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2267) Disambiguate server jar from phoenix-server module jar
Date Sun, 01 Nov 2015 04:09:27 GMT


Josh Elser commented on PHOENIX-2267:

I feel like dropping "server" might cause confusion in the other direction (people wouldn't
know what jar runs PQS as is how the feature is commonly referred to me in conversation now).

What if we make queryserver a single word? e.g. {{phoenix-queryserver}} and {{phoenix-queryserver-client}}.
Is that sufficiently different from the (HBase) "server" component of Phoenix?

> Disambiguate server jar from phoenix-server module jar
> ------------------------------------------------------
>                 Key: PHOENIX-2267
>                 URL:
>             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

View raw message