[ https://issues.apache.org/jira/browse/HBASE-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905863#comment-15905863 ]
Jerry He commented on HBASE-15597: ---------------------------------- +1 on v4. > Clean up configuration keys used in hbase-spark module > ------------------------------------------------------ > > Key: HBASE-15597 > URL: https://issues.apache.org/jira/browse/HBASE-15597 > Project: HBase > Issue Type: Bug > Components: spark > Affects Versions: 2.0.0 > Reporter: Sean Busbey > Assignee: Yi Liang > Priority: Critical > Fix For: 2.0.0 > > Attachments: HBASE-15597-v1.patch, HBASE-15597-V2.patch, > HBASE-15597-V3.patch, HBase-15597-V4.patch > > > This should be considered a blocker for backport to branch-1 since it will > impact our compatibility. > The constants we expose in configuration should all start with "hbase". Since > our configurations keys for the spark integration all relate to that system, > the prefix for all configuration keys (excluding those cases where we need to > do something special due to restrictions in how properties are handled by > e.g. spark) should be "hbase.spark". > Before publishing a public api labeled version of our spark integration we > should review all of our configuration keys to make sure they either conform > to the "hbase.spark" prefix or they have a comment documenting why they need > to be otherwise. -- This message was sent by Atlassian JIRA (v6.3.15#6346)