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 2023/11/20 06:58:00 UTC
[jira] [Comment Edited] (PHOENIX-7059) De-duplicate HBase string contants in Phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17787833#comment-17787833 ]
Istvan Toth edited comment on PHOENIX-7059 at 11/20/23 6:57 AM:
----------------------------------------------------------------
I would suggest waiting for PHOENIX-6053 to land before working on this, otherwise additional HBase server dependencies may be introduced into the client code.
was (Author: stoty):
I would suggest wiating for PHOENIX-6053 to land before working on this, otherwise additional HBase server dependencies may be introduced into the client code.
> De-duplicate HBase string contants in Phoenix
> ---------------------------------------------
>
> Key: PHOENIX-7059
> URL: https://issues.apache.org/jira/browse/PHOENIX-7059
> Project: Phoenix
> Issue Type: Improvement
> Components: core
> Affects Versions: 5.2.0, 5.1.3
> Reporter: Istvan Toth
> Assignee: Jing Yu
> Priority: Minor
>
> We are re-defining a lot of HBase property and class names in Phoenix.
> We should either directly replace the String constats in Phoenix, or initialize them from the HBase constants.
> We need to be careful not to introduce additional dependencies (i.e. do not replace constants in client-side code that are defined in hbase-server).
> We also need to be careful to replace only constants that are present in all supported HBase version (2.1+, as of writing this)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)