[
https://issues.apache.org/jira/browse/HBASE-12546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219739#comment-14219739
]
Andrew Purtell edited comment on HBASE-12546 at 11/20/14 6:34 PM:
------------------------------------------------------------------
I think for new tables it is reasonable to check known schema options that
require classes to be available on the server side when processing the admin
request RPC, and throw an exception back if we can't find it.
For existing tables, do we check if classes in schema options are still
reachable and refuse deployment instead of aborting? I don't know. Something is
seriously wrong with the RS environment.
was (Author: apurtell):
I think for new tables it is reasonable to check known schema options that
require classes to be available on the server side when processing the admin
request RPC, and throw an exception back if we can't find it.
For existing tables, do we check if classes in schema options are still
reachable and refuse deployment instead of aborting? I don't know. As you say
this part of it is a slippery slope. Something is seriously wrong with the RS
environment.
> Validate schema options that require server side class availability
> -------------------------------------------------------------------
>
> Key: HBASE-12546
> URL: https://issues.apache.org/jira/browse/HBASE-12546
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Fix For: 2.0.0, 0.98.9, 0.99.2
>
>
> When processing table create and modification requests we should check the
> supplied schema options for settings that require mentioned classes to be
> available from the regionserver classpath (split policies, etc.). If we can't
> find the class on the classpath when processing the admin request RPC, fail
> the operation immediately and return an exception rather than allow problems
> later, such as aborts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
