You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/04/09 16:37:00 UTC

[jira] [Commented] (PHOENIX-5771) Make standalone queryserver assembly useful again

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

Istvan Toth commented on PHOENIX-5771:
--------------------------------------

Based on  a discussion with [~elserj], the current preferred solution is to add a profile that builds a PQS assembly with the specified phoenix-client.

> Make standalone queryserver assembly useful again
> -------------------------------------------------
>
>                 Key: PHOENIX-5771
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5771
>             Project: Phoenix
>          Issue Type: Task
>          Components: queryserver
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> The assembly module in the phoenix-queryserver repo doesn't make much sense as it is.
> Things to do:
>  * figure out the use case for the assembly: 
>  ** Do we want this to be copied onto the main phoenix assembly (my preferred answer)
>  ** Or do we want it to live in standalone driectory
>  * Copy the right jars to the right place for the scripts to work
>  * Make sure we do not overwrite stuff in the main repo (if we share the install dir)
>  * Make sure PQS can access the fat client JAR ( an issue if we want to live standalone)
>  * Remove PQS cruft from the main Phoenix scripts and vica versa (probably in a different JIRA)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)