You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/05/07 05:54:00 UTC
[jira] [Updated] (PHOENIX-5641) Decouple phoenix-queryserver from
phoenix-core
[ https://issues.apache.org/jira/browse/PHOENIX-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Istvan Toth updated PHOENIX-5641:
---------------------------------
Fix Version/s: 4.16.0
Affects Version/s: 4.16.0
Finally backported to 4.x
> Decouple phoenix-queryserver from phoenix-core
> ----------------------------------------------
>
> Key: PHOENIX-5641
> URL: https://issues.apache.org/jira/browse/PHOENIX-5641
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.1.0, 4.16.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.1.0, 4.16.0
>
> Attachments: PHOENIX-5641.master.v1.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> phoenix-queryserver has been moved to a separate repo, and it's versioning has been decoupled from that of phoenix-core.
> Yet, phoenix-queryserver still uses code from phoenix-core, and phoenix-core in turn contains code that is only used by phoenix-queryserver.
> This causes (at least) the following problems:
> * Adding new features to PQS is problematic, because it depends on an old released version of phoenix
> * The phoenix-thin-client includes phoenix code, that is not really necessary
> I propose fully decoupling the PQS code from phoenix proper. This effectively means:
> * duplicating the PQS specific configuration parameter names and defaults in PQS
> * copying a minimal amount of code for building the JDBC connection URL
> * copying theĀ InstanceResolver cache class
> The tests are still dependent on phoenix-core, but I do not consider that a problem.
> If/when this patch lands in PQS, we should also remove the PQS specific parameters from phoenix-core.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)