[
https://issues.apache.org/jira/browse/HBASE-24039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Antal updated HBASE-24039:
----------------------------------
Description:
Each HBase version is shipped with a specific version of HBCK2 therefore we can
check the HBCK2 version and decide if the given command is supported in that
version or not.
It is not that easy to decide if the command is supported or not when dealing
with back-ported features.
It the conclusion of this I would recommend using feature negotiation to check
what commands are supported on the server side instead of comparing versions.
was:
Each HBase version is shipped with a specific version of HBCK2 therefore we can
check the HBCK2 version and decide if the given command is supported in that
version or not.
It is not that easy to decide if the command is supported or not when dealing
with back-ported features.
It the conclusion of this I would recommend using feature negotiation to check
what commands are supported instead of comparing versions.
> HBCK2 feature negotiation to check what commands are supported
> --------------------------------------------------------------
>
> Key: HBASE-24039
> URL: https://issues.apache.org/jira/browse/HBASE-24039
> Project: HBase
> Issue Type: Improvement
> Reporter: Richard Antal
> Priority: Major
>
> Each HBase version is shipped with a specific version of HBCK2 therefore we
> can check the HBCK2 version and decide if the given command is supported in
> that version or not.
> It is not that easy to decide if the command is supported or not when
> dealing with back-ported features.
> It the conclusion of this I would recommend using feature negotiation to
> check what commands are supported on the server side instead of comparing
> versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)