[jira] [Updated] (HBASE-13621) Purge KVComparator and its related code from code base for 3.0
[ https://issues.apache.org/jira/browse/HBASE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-13621: - Attachment: HBASE-13621.v0.patch > Purge KVComparator and its related code from code base for 3.0 > -- > > Key: HBASE-13621 > URL: https://issues.apache.org/jira/browse/HBASE-13621 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: ramkrishna.s.vasudevan >Assignee: kevin su >Priority: Blocker > Attachments: HBASE-13621.v0.patch > > > This is a reminder JIRA so that while moving to 3.0 we will remove all the > code related to KVComparator that has been deprecated in the 2.0 train. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-13621) Purge KVComparator and its related code from code base for 3.0
[ https://issues.apache.org/jira/browse/HBASE-13621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-13621: Assignee: kevin su > Purge KVComparator and its related code from code base for 3.0 > -- > > Key: HBASE-13621 > URL: https://issues.apache.org/jira/browse/HBASE-13621 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: ramkrishna.s.vasudevan >Assignee: kevin su >Priority: Blocker > > This is a reminder JIRA so that while moving to 3.0 we will remove all the > code related to KVComparator that has been deprecated in the 2.0 train. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881076#comment-16881076 ] kevin su commented on HBASE-22662: -- [~Apache9] sorry for wrong patch, and thanks for your reply, help me a lot > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task > Components: rsgroup >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16881014#comment-16881014 ] kevin su commented on HBASE-22662: -- so the work will be # change package to o.a.h.h.master.rsgroup # move config in RSGroupInfoManager to HConstants anything I miss > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Priority: Major > Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22662: Assignee: (was: kevin su) > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Priority: Major > Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22662: - Attachment: HBASE-22662.v1.patch > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22662.v0.patch, HBASE-22662.v1.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880960#comment-16880960 ] kevin su commented on HBASE-22662: -- I got it, let me update the patch. > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22662.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880952#comment-16880952 ] kevin su commented on HBASE-22662: -- I also move RSGroupProtobufUtil to hbase-server, because RSGroupInfoManager uses it also. > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22662.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22662: Assignee: kevin su > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22662.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22662) Move RSGroupInfoManager to hbase-server
[ https://issues.apache.org/jira/browse/HBASE-22662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22662: - Attachment: HBASE-22662.v0.patch > Move RSGroupInfoManager to hbase-server > --- > > Key: HBASE-22662 > URL: https://issues.apache.org/jira/browse/HBASE-22662 > Project: HBase > Issue Type: Sub-task >Reporter: Duo Zhang >Priority: Major > Attachments: HBASE-22662.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-6519) FSRegionScanner should be in its own file
[
https://issues.apache.org/jira/browse/HBASE-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880213#comment-16880213
]
kevin su commented on HBASE-6519:
-
*[~rvadali]* {color:#33}link not working{color}
> FSRegionScanner should be in its own file
> -
>
> Key: HBASE-6519
> URL: https://issues.apache.org/jira/browse/HBASE-6519
> Project: HBase
> Issue Type: Improvement
> Components: util
> Environment: mac osx, jdk 1.6
>Reporter: Ramkumar Vadali
>Priority: Minor
>
> I found this problem in the 0.89-fb branch.
> I was not able to start the master because of a ClassNotFoundException for
> FSRegionScanner.
> FSRegionScanner is a top-level class in FSUtils.java. Moving it to a separate
> file solved the problem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22131) Delete the patches in hbase-protocol-shaded module
[ https://issues.apache.org/jira/browse/HBASE-22131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22131: - Attachment: HBASE-22131.v0.patch Status: Patch Available (was: Open) > Delete the patches in hbase-protocol-shaded module > -- > > Key: HBASE-22131 > URL: https://issues.apache.org/jira/browse/HBASE-22131 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22131.v0.patch > > > As now we will apply the patch in the hbase-thirdparty repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22131) Delete the patches in hbase-protocol-shaded module
[ https://issues.apache.org/jira/browse/HBASE-22131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805431#comment-16805431 ] kevin su commented on HBASE-22131: -- [~stack] Actually, I just faced some trouble about HBASE-22130, thanks for rescuing. > Delete the patches in hbase-protocol-shaded module > -- > > Key: HBASE-22131 > URL: https://issues.apache.org/jira/browse/HBASE-22131 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > As now we will apply the patch in the hbase-thirdparty repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22130) [hbase-thirdparty] Upgrade thirdparty dependencies
[ https://issues.apache.org/jira/browse/HBASE-22130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22130: Assignee: stack (was: kevin su) > [hbase-thirdparty] Upgrade thirdparty dependencies > -- > > Key: HBASE-22130 > URL: https://issues.apache.org/jira/browse/HBASE-22130 > Project: HBase > Issue Type: Task > Components: thirdparty >Reporter: Duo Zhang >Assignee: stack >Priority: Major > Attachments: > 0001-HBASE-22130-hbase-thirdparty-Upgrade-thirdparty-depe.patch > > > First guava has a CVE so we need to upgrade to at least 26.0, better to the > newest 27.1. > And we can also upgrade the other dependencies to the newest version at the > same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22131) Delete the patches in hbase-protocol-shaded module
[ https://issues.apache.org/jira/browse/HBASE-22131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805173#comment-16805173 ] kevin su commented on HBASE-22131: -- @stack Thanks for your reply, very aprreciate. I think I can take this. I will also research those patch for more detail > Delete the patches in hbase-protocol-shaded module > -- > > Key: HBASE-22131 > URL: https://issues.apache.org/jira/browse/HBASE-22131 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > As now we will apply the patch in the hbase-thirdparty repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22131) Delete the patches in hbase-protocol-shaded module
[ https://issues.apache.org/jira/browse/HBASE-22131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22131: Assignee: kevin su > Delete the patches in hbase-protocol-shaded module > -- > > Key: HBASE-22131 > URL: https://issues.apache.org/jira/browse/HBASE-22131 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > As now we will apply the patch in the hbase-thirdparty repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22131) Delete the patches in hbase-protocol-shaded module
[ https://issues.apache.org/jira/browse/HBASE-22131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16805128#comment-16805128 ] kevin su commented on HBASE-22131: -- [~Apache9]Do you mean delete whole patches in the hbase/hbase-protocol-shaded/src/main/patches/ directory ? > Delete the patches in hbase-protocol-shaded module > -- > > Key: HBASE-22131 > URL: https://issues.apache.org/jira/browse/HBASE-22131 > Project: HBase > Issue Type: Task >Reporter: Duo Zhang >Priority: Major > > As now we will apply the patch in the hbase-thirdparty repo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22130) [hbase-thirdparty] Upgrade thirdparty dependencies
[ https://issues.apache.org/jira/browse/HBASE-22130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22130: Assignee: kevin su > [hbase-thirdparty] Upgrade thirdparty dependencies > -- > > Key: HBASE-22130 > URL: https://issues.apache.org/jira/browse/HBASE-22130 > Project: HBase > Issue Type: Task > Components: thirdparty >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > First guava has a CVE so we need to upgrade to at least 26.0, better to the > newest 27.1. > And we can also upgrade the other dependencies to the newest version at the > same time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22124) Optimize the performance for region moving
[
https://issues.apache.org/jira/browse/HBASE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16804887#comment-16804887
]
kevin su commented on HBASE-22124:
--
Use ConcurrentSkipListMap to save RegionStateNode, and Encodedname as a key.
Everytime createRegionStateNode put to
ConcurrentSkipListMap.
So we can use this map to Optimize the performance, but use more memory.
> Optimize the performance for region moving
> --
>
> Key: HBASE-22124
> URL: https://issues.apache.org/jira/browse/HBASE-22124
> Project: HBase
> Issue Type: Improvement
>Reporter: Duo Zhang
>Priority: Major
> Attachments: HBASE-22124.v0.patch
>
>
> It is an admin operation so we do not care much about the performance in the
> past, but it is really important for rolling upgrade.
> For AsyncAdmin, if encoded name is present at client side, we will always
> scan the whole meta region to find the region record first, which is really
> expensive for a large cluster.
> And we always send the encoded name to master, so at master side, we still
> need the encoded name -> region name converting, and it is still very
> expensive
> {code}
> public RegionState getRegionState(final String encodedRegionName) {
> // TODO: Need a map but it is just dispatch merge...
> for (RegionStateNode node: regionsMap.values()) {
> if (node.getRegionInfo().getEncodedName().equals(encodedRegionName)) {
> return node.toRegionState();
> }
> }
> return null;
> }
> {code}
> Need to fix them both.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22124) Optimize the performance for region moving
[
https://issues.apache.org/jira/browse/HBASE-22124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-22124:
-
Attachment: HBASE-22124.v0.patch
> Optimize the performance for region moving
> --
>
> Key: HBASE-22124
> URL: https://issues.apache.org/jira/browse/HBASE-22124
> Project: HBase
> Issue Type: Improvement
>Reporter: Duo Zhang
>Priority: Major
> Attachments: HBASE-22124.v0.patch
>
>
> It is an admin operation so we do not care much about the performance in the
> past, but it is really important for rolling upgrade.
> For AsyncAdmin, if encoded name is present at client side, we will always
> scan the whole meta region to find the region record first, which is really
> expensive for a large cluster.
> And we always send the encoded name to master, so at master side, we still
> need the encoded name -> region name converting, and it is still very
> expensive
> {code}
> public RegionState getRegionState(final String encodedRegionName) {
> // TODO: Need a map but it is just dispatch merge...
> for (RegionStateNode node: regionsMap.values()) {
> if (node.getRegionInfo().getEncodedName().equals(encodedRegionName)) {
> return node.toRegionState();
> }
> }
> return null;
> }
> {code}
> Need to fix them both.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22089) HMaster#getClusterSchema() could return null and cause NPE
[
https://issues.apache.org/jira/browse/HBASE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-22089:
-
Attachment: HBASE-22089.v0.patch
> HMaster#getClusterSchema() could return null and cause NPE
> --
>
> Key: HBASE-22089
> URL: https://issues.apache.org/jira/browse/HBASE-22089
> Project: HBase
> Issue Type: Improvement
> Components: master
>Reporter: Xiang Li
>Assignee: kevin su
>Priority: Minor
> Attachments: HBASE-22089.v0.patch
>
>
> HMaster#getClusterSchema() has a lot of usage, for example:
> {code:title=hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java|borderStyle=solid}
> void assignTableToGroup(TableDescriptor desc) throws IOException {
> String groupName =
>
> master.getClusterSchema().getNamespace(desc.getTableName().getNamespaceAsString())
> .getConfigurationValue(RSGroupInfo.NAMESPACE_DESC_PROP_GROUP);
> ...
> }
> {code}
> getClusterSchema() might return null when cluster schema service is not ready
> yet. Actually, it won't be ready until HMaster#initClusterSchemaService() is
> finished. See [this
> comment|https://issues.apache.org/jira/browse/HBASE-20690?focusedCommentId=16784549=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16784549]
> for details.
> We need to add protections, like adding null check before calling
> getClusterSchema().getXXX(), or in HMaster#getClusterSchema(), add a loop to
> wait until this.clusterSchemaService is not null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HBASE-22089) HMaster#getClusterSchema() could return null and cause NPE
[
https://issues.apache.org/jira/browse/HBASE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799584#comment-16799584
]
kevin su edited comment on HBASE-22089 at 3/28/19 12:42 AM:
[~water] I found that there is a function *_isInitialized_* in Hmaster, It will
set to true after initClusterSchemaService was completed.
So,I will use *_this.master.isInitialized()_* to check if this is completed, if
no,It will give a log
{code}LOG.debug("Master has not been initialized, don't
assignTableToGroup.");{code}
And then return NULL.
What do you think?
was (Author: pingsutw):
[~water] I found that there is a function *_isInitialized_* in Hmaster, It will
set to true after initClusterSchemaService was completed.
So,I will use *_this.master.isInitialized()_* to check if this is completed, if
no,It will give a log
{code}LOG.debug("Master has not been initialized, don't get
NamespaceDescriptor.");{code}
And then return NULL.
What do you think?
> HMaster#getClusterSchema() could return null and cause NPE
> --
>
> Key: HBASE-22089
> URL: https://issues.apache.org/jira/browse/HBASE-22089
> Project: HBase
> Issue Type: Improvement
> Components: master
>Reporter: Xiang Li
>Assignee: kevin su
>Priority: Minor
>
> HMaster#getClusterSchema() has a lot of usage, for example:
> {code:title=hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java|borderStyle=solid}
> void assignTableToGroup(TableDescriptor desc) throws IOException {
> String groupName =
>
> master.getClusterSchema().getNamespace(desc.getTableName().getNamespaceAsString())
> .getConfigurationValue(RSGroupInfo.NAMESPACE_DESC_PROP_GROUP);
> ...
> }
> {code}
> getClusterSchema() might return null when cluster schema service is not ready
> yet. Actually, it won't be ready until HMaster#initClusterSchemaService() is
> finished. See [this
> comment|https://issues.apache.org/jira/browse/HBASE-20690?focusedCommentId=16784549=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16784549]
> for details.
> We need to add protections, like adding null check before calling
> getClusterSchema().getXXX(), or in HMaster#getClusterSchema(), add a loop to
> wait until this.clusterSchemaService is not null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16803001#comment-16803001 ] kevin su commented on HBASE-17094: -- There are some error in my this two patch I am fixing this. If it works, I will tell u. > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch, HBASE-17094.v2.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22028) Deprecated isTableAvailableWithSplit method in thrift
[ https://issues.apache.org/jira/browse/HBASE-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22028: - Attachment: HBASE-22028.v0.patch > Deprecated isTableAvailableWithSplit method in thrift > - > > Key: HBASE-22028 > URL: https://issues.apache.org/jira/browse/HBASE-22028 > Project: HBase > Issue Type: Task > Components: Admin, Thrift >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Attachments: HBASE-22028.v0.patch > > > As we have already deprecated the same methods in our Admin interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22028) Deprecated isTableAvailableWithSplit method in thrift
[ https://issues.apache.org/jira/browse/HBASE-22028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22028: Assignee: kevin su > Deprecated isTableAvailableWithSplit method in thrift > - > > Key: HBASE-22028 > URL: https://issues.apache.org/jira/browse/HBASE-22028 > Project: HBase > Issue Type: Task > Components: Admin, Thrift >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > > As we have already deprecated the same methods in our Admin interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22108) Avoid passing null in Admin methods
[ https://issues.apache.org/jira/browse/HBASE-22108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802154#comment-16802154 ] kevin su commented on HBASE-22108: -- maybe we could add moveRandom(byte[] encodedRegionName) method in Admin btw, there is split(TableName tableName) method, user don't need to pass null. > Avoid passing null in Admin methods > --- > > Key: HBASE-22108 > URL: https://issues.apache.org/jira/browse/HBASE-22108 > Project: HBase > Issue Type: Task > Components: Admin >Reporter: Duo Zhang >Priority: Major > > For some methods we must pass null if we want specific behaviors, for > example, move region to a random server, split region without providing an > explicit split point, etc. > We should provide methods without some parameters so user do not need to pass > null. > So in the future users do not need to guess whether a method accept null > parameters, the answer is always no. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22101: - Attachment: HBASE-22101.v1.patch > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22101.v0.patch, HBASE-22101.v1.patch > > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22102) Remove AsyncAdmin.isTableAvailable(TableName, byte[][])
[ https://issues.apache.org/jira/browse/HBASE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22102: - Attachment: HBASE-22102.v1.patch > Remove AsyncAdmin.isTableAvailable(TableName, byte[][]) > --- > > Key: HBASE-22102 > URL: https://issues.apache.org/jira/browse/HBASE-22102 > Project: HBase > Issue Type: Task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22102.v0.patch, HBASE-22102.v1.patch > > > It has been deprecated so remove it in 3.0.0, to align with the Admin > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22102) Remove AsyncAdmin.isTableAvailable(TableName, byte[][])
[ https://issues.apache.org/jira/browse/HBASE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22102: - Attachment: (was: HBASE-22102.v0.patch) > Remove AsyncAdmin.isTableAvailable(TableName, byte[][]) > --- > > Key: HBASE-22102 > URL: https://issues.apache.org/jira/browse/HBASE-22102 > Project: HBase > Issue Type: Task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22102.v0.patch > > > It has been deprecated so remove it in 3.0.0, to align with the Admin > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22102) Remove AsyncAdmin.isTableAvailable(TableName, byte[][])
[ https://issues.apache.org/jira/browse/HBASE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22102: - Attachment: HBASE-22102.v0.patch Status: Patch Available (was: Open) > Remove AsyncAdmin.isTableAvailable(TableName, byte[][]) > --- > > Key: HBASE-22102 > URL: https://issues.apache.org/jira/browse/HBASE-22102 > Project: HBase > Issue Type: Task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22102.v0.patch > > > It has been deprecated so remove it in 3.0.0, to align with the Admin > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801580#comment-16801580 ] kevin su commented on HBASE-22101: -- yes, i found some wrong in my patch, I'm going to fix it. I'm also going to add UT. [~Apache9], Thank you. > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22101.v0.patch > > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22101: - Status: In Progress (was: Patch Available) > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22101.v0.patch > > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22102) Remove AsyncAdmin.isTableAvailable(TableName, byte[][])
[ https://issues.apache.org/jira/browse/HBASE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22102: - Attachment: HBASE-22102.v0.patch > Remove AsyncAdmin.isTableAvailable(TableName, byte[][]) > --- > > Key: HBASE-22102 > URL: https://issues.apache.org/jira/browse/HBASE-22102 > Project: HBase > Issue Type: Task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22102.v0.patch > > > It has been deprecated so remove it in 3.0.0, to align with the Admin > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22101: - Attachment: HBASE-22101.v0.patch Status: Patch Available (was: Open) > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Attachments: HBASE-22101.v0.patch > > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800594#comment-16800594 ] kevin su commented on HBASE-22101: -- I got you, thanks. > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22102) Remove AsyncAdmin.isTableAvailable(TableName, byte[][])
[ https://issues.apache.org/jira/browse/HBASE-22102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22102: Assignee: kevin su > Remove AsyncAdmin.isTableAvailable(TableName, byte[][]) > --- > > Key: HBASE-22102 > URL: https://issues.apache.org/jira/browse/HBASE-22102 > Project: HBase > Issue Type: Task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > > It has been deprecated so remove it in 3.0.0, to align with the Admin > interface. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800494#comment-16800494 ] kevin su commented on HBASE-22101: -- [~Apache9] I found that isTableAvailable in AsyncAdmin don't throw any exception just return CompletableFuture Do u mean change other class ? > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22101) AsyncAdmin.isTableAvailable should not throw TableNotFoundException
[ https://issues.apache.org/jira/browse/HBASE-22101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22101: Assignee: kevin su > AsyncAdmin.isTableAvailable should not throw TableNotFoundException > --- > > Key: HBASE-22101 > URL: https://issues.apache.org/jira/browse/HBASE-22101 > Project: HBase > Issue Type: Sub-task > Components: Admin, asyncclient, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > > Should return false instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800068#comment-16800068
]
kevin su commented on HBASE-20756:
--
[~xucang] Could help me review this patch at your convenience.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22064: - Description: Because update to new version, we need to remove the deprecated function Admin.deleteSnapshot(byte[]) There are some testing also use this function, so we need to change it to Admin.deleteSnapshot(string[]) was:Because update to new version, we need to remove In order to remove delte > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Affects Versions: 3.0.0 >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22064.v0.patch > > > Because update to new version, we need to remove the deprecated function > Admin.deleteSnapshot(byte[]) > There are some testing also use this function, so we need to change it to > Admin.deleteSnapshot(string[]) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[
https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-22064:
-
Description: Because update to new version, we need to remove(was:
{color:red}colored text{color})
> Remove Admin.deleteSnapshot(byte[])
> ---
>
> Key: HBASE-22064
> URL: https://issues.apache.org/jira/browse/HBASE-22064
> Project: HBase
> Issue Type: Task
> Components: Admin
>Affects Versions: 3.0.0
>Reporter: Duo Zhang
>Assignee: kevin su
>Priority: Major
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-22064.v0.patch
>
>
> Because update to new version, we need to remove
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22064: - Description: Because update to new version, we need to remove In order to remove delte (was: Because update to new version, we need to remove ) > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Affects Versions: 3.0.0 >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22064.v0.patch > > > Because update to new version, we need to remove In order to remove delte -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[
https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-22064:
-
Description: {color:red}colored text{color}
> Remove Admin.deleteSnapshot(byte[])
> ---
>
> Key: HBASE-22064
> URL: https://issues.apache.org/jira/browse/HBASE-22064
> Project: HBase
> Issue Type: Task
> Components: Admin
>Affects Versions: 3.0.0
>Reporter: Duo Zhang
>Assignee: kevin su
>Priority: Major
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-22064.v0.patch
>
>
> {color:red}colored text{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799980#comment-16799980 ] kevin su commented on HBASE-22064: -- [~water] OK, I am going to add this as soon as possible. > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Affects Versions: 3.0.0 >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22064.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22094) Throw TableNotFoundException if table not exists in AsyncAdmin.compact
[ https://issues.apache.org/jira/browse/HBASE-22094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22094: Assignee: kevin su > Throw TableNotFoundException if table not exists in AsyncAdmin.compact > -- > > Key: HBASE-22094 > URL: https://issues.apache.org/jira/browse/HBASE-22094 > Project: HBase > Issue Type: Sub-task > Components: Admin >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > > Now we will return successfully, which is not the same with the HBaseAdmin. > For NORMAL compaction, we should throw TableNotFoundException if the > locations is empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: HBASE-17094.v2.patch > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch, HBASE-17094.v2.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: (was: HBASE-17094.v2.patch) > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: HBASE-17094.v2.patch > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch, HBASE-17094.v2.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: (was: HBASE-17094.v2.patch) > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: HBASE-17094.v2.patch > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch, HBASE-17094.v2.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-22089) HMaster#getClusterSchema() could return null and cause NPE
[
https://issues.apache.org/jira/browse/HBASE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799584#comment-16799584
]
kevin su edited comment on HBASE-22089 at 3/23/19 9:57 AM:
---
[~water] I found that there is a function *_isInitialized_* in Hmaster, It will
set to true after initClusterSchemaService was completed.
So,I will use *_this.master.isInitialized()_* to check if this is completed, if
no,It will give a log
{code}LOG.debug("Master has not been initialized, don't get
NamespaceDescriptor.");{code}
And then return NULL.
What do you think?
was (Author: pingsutw):
[~water] I found that there is a function *_isInitialized_* in Hmaster, It will
set to true after initClusterSchemaService was completed.
So,I will use *_this.master.isInitialized()_* to check if this is completed, if
no,It will give a log
{code}LOG.debug("Master has not been initialized, don't run balancer.");{code}
And then return NULL.
What do you think?
> HMaster#getClusterSchema() could return null and cause NPE
> --
>
> Key: HBASE-22089
> URL: https://issues.apache.org/jira/browse/HBASE-22089
> Project: HBase
> Issue Type: Improvement
> Components: master
>Reporter: Xiang Li
>Assignee: kevin su
>Priority: Minor
>
> HMaster#getClusterSchema() has a lot of usage, for example:
> {code:title=hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java|borderStyle=solid}
> void assignTableToGroup(TableDescriptor desc) throws IOException {
> String groupName =
>
> master.getClusterSchema().getNamespace(desc.getTableName().getNamespaceAsString())
> .getConfigurationValue(RSGroupInfo.NAMESPACE_DESC_PROP_GROUP);
> ...
> }
> {code}
> getClusterSchema() might return null when cluster schema service is not ready
> yet. Actually, it won't be ready until HMaster#initClusterSchemaService() is
> finished. See [this
> comment|https://issues.apache.org/jira/browse/HBASE-20690?focusedCommentId=16784549=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16784549]
> for details.
> We need to add protections, like adding null check before calling
> getClusterSchema().getXXX(), or in HMaster#getClusterSchema(), add a loop to
> wait until this.clusterSchemaService is not null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22089) HMaster#getClusterSchema() could return null and cause NPE
[
https://issues.apache.org/jira/browse/HBASE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799584#comment-16799584
]
kevin su commented on HBASE-22089:
--
[~water] I found that there is a function *_isInitialized_* in Hmaster, It will
set to true after initClusterSchemaService was completed.
So,I will use *_this.master.isInitialized()_* to check if this is completed, if
no,It will give a log
{code}LOG.debug("Master has not been initialized, don't run balancer.");{code}
And then return NULL.
What do you think?
> HMaster#getClusterSchema() could return null and cause NPE
> --
>
> Key: HBASE-22089
> URL: https://issues.apache.org/jira/browse/HBASE-22089
> Project: HBase
> Issue Type: Improvement
> Components: master
>Reporter: Xiang Li
>Assignee: kevin su
>Priority: Minor
>
> HMaster#getClusterSchema() has a lot of usage, for example:
> {code:title=hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java|borderStyle=solid}
> void assignTableToGroup(TableDescriptor desc) throws IOException {
> String groupName =
>
> master.getClusterSchema().getNamespace(desc.getTableName().getNamespaceAsString())
> .getConfigurationValue(RSGroupInfo.NAMESPACE_DESC_PROP_GROUP);
> ...
> }
> {code}
> getClusterSchema() might return null when cluster schema service is not ready
> yet. Actually, it won't be ready until HMaster#initClusterSchemaService() is
> finished. See [this
> comment|https://issues.apache.org/jira/browse/HBASE-20690?focusedCommentId=16784549=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16784549]
> for details.
> We need to add protections, like adding null check before calling
> getClusterSchema().getXXX(), or in HMaster#getClusterSchema(), add a loop to
> wait until this.clusterSchemaService is not null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-22089) HMaster#getClusterSchema() could return null and cause NPE
[
https://issues.apache.org/jira/browse/HBASE-22089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su reassigned HBASE-22089:
Assignee: kevin su
> HMaster#getClusterSchema() could return null and cause NPE
> --
>
> Key: HBASE-22089
> URL: https://issues.apache.org/jira/browse/HBASE-22089
> Project: HBase
> Issue Type: Improvement
> Components: master
>Reporter: Xiang Li
>Assignee: kevin su
>Priority: Minor
>
> HMaster#getClusterSchema() has a lot of usage, for example:
> {code:title=hbase-rsgroup/src/main/java/org/apache/hadoop/hbase/rsgroup/RSGroupAdminEndpoint.java|borderStyle=solid}
> void assignTableToGroup(TableDescriptor desc) throws IOException {
> String groupName =
>
> master.getClusterSchema().getNamespace(desc.getTableName().getNamespaceAsString())
> .getConfigurationValue(RSGroupInfo.NAMESPACE_DESC_PROP_GROUP);
> ...
> }
> {code}
> getClusterSchema() might return null when cluster schema service is not ready
> yet. Actually, it won't be ready until HMaster#initClusterSchemaService() is
> finished. See [this
> comment|https://issues.apache.org/jira/browse/HBASE-20690?focusedCommentId=16784549=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16784549]
> for details.
> We need to add protections, like adding null check before calling
> getClusterSchema().getXXX(), or in HMaster#getClusterSchema(), add a loop to
> wait until this.clusterSchemaService is not null.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-22064: - Affects Version/s: 3.0.0 Attachment: HBASE-22064.v0.patch Status: Patch Available (was: Open) > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Affects Versions: 3.0.0 >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-22064.v0.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-22064 started by kevin su. > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work stopped] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-22064 stopped by kevin su. > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22064) Remove Admin.deleteSnapshot(byte[])
[ https://issues.apache.org/jira/browse/HBASE-22064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22064: Assignee: kevin su > Remove Admin.deleteSnapshot(byte[]) > --- > > Key: HBASE-22064 > URL: https://issues.apache.org/jira/browse/HBASE-22064 > Project: HBase > Issue Type: Task > Components: Admin >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-22056) Unexpected blank line in ClusterConnection
[
https://issues.apache.org/jira/browse/HBASE-22056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795753#comment-16795753
]
kevin su commented on HBASE-22056:
--
ok, thnak you so much .
> Unexpected blank line in ClusterConnection
> --
>
> Key: HBASE-22056
> URL: https://issues.apache.org/jira/browse/HBASE-22056
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0
>Reporter: kevin su
>Assignee: kevin su
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-22056.v0.patch
>
>
> {code}
> /**
> *
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-22056) Unexpected blank line in ClusterConnection
[
https://issues.apache.org/jira/browse/HBASE-22056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-22056:
-
Release Note: Remove unexpected blank line at comment in ClusterConnection
Attachment: HBASE-22056.v0.patch
Status: Patch Available (was: Open)
> Unexpected blank line in ClusterConnection
> --
>
> Key: HBASE-22056
> URL: https://issues.apache.org/jira/browse/HBASE-22056
> Project: HBase
> Issue Type: Umbrella
>Affects Versions: 3.0.0
>Reporter: kevin su
>Assignee: kevin su
>Priority: Trivial
> Fix For: 3.0.0
>
> Attachments: HBASE-22056.v0.patch
>
>
> {code}
> /**
> *
> * Licensed to the Apache Software Foundation (ASF) under one
> * or more contributor license agreements. See the NOTICE file
> * distributed with this work for additional information
> * regarding copyright ownership. The ASF licenses this file
> * to you under the Apache License, Version 2.0 (the
> * "License"); you may not use this file except in compliance
> * with the License. You may obtain a copy of the License at
> *
> * http://www.apache.org/licenses/LICENSE-2.0
> *
> * Unless required by applicable law or agreed to in writing, software
> * distributed under the License is distributed on an "AS IS" BASIS,
> * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> * See the License for the specific language governing permissions and
> * limitations under the License.
> */
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (HBASE-22056) Unexpected blank line in ClusterConnection
kevin su created HBASE-22056:
Summary: Unexpected blank line in ClusterConnection
Key: HBASE-22056
URL: https://issues.apache.org/jira/browse/HBASE-22056
Project: HBase
Issue Type: Umbrella
Affects Versions: 3.0.0
Reporter: kevin su
Assignee: kevin su
Fix For: 3.0.0
{code}
/**
*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-22002) Remove the deprecated methods in Admin interface
[ https://issues.apache.org/jira/browse/HBASE-22002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786352#comment-16786352 ] kevin su commented on HBASE-22002: -- I will try to do it as well. Hopefully I could help in the future. > Remove the deprecated methods in Admin interface > > > Key: HBASE-22002 > URL: https://issues.apache.org/jira/browse/HBASE-22002 > Project: HBase > Issue Type: Task > Components: Admin, Client >Reporter: Duo Zhang >Priority: Major > Fix For: 3.0.0 > > > For API cleanup, and will make the work in HBASE-21718 a little easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-22002) Remove the deprecated methods in Admin interface
[ https://issues.apache.org/jira/browse/HBASE-22002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22002: Assignee: (was: kevin su) > Remove the deprecated methods in Admin interface > > > Key: HBASE-22002 > URL: https://issues.apache.org/jira/browse/HBASE-22002 > Project: HBase > Issue Type: Task > Components: Admin, Client >Reporter: Duo Zhang >Priority: Major > Fix For: 3.0.0 > > > For API cleanup, and will make the work in HBASE-21718 a little easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786235#comment-16786235
]
kevin su commented on HBASE-20756:
--
ok, I got it. Thanks again.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786186#comment-16786186
]
kevin su commented on HBASE-20756:
--
[~busbey]Thanks you so much.
Now I already fix it. Maybe could mark it as resolved.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Attachment: (was: HBASE-21057.v2.patch)
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Attachment: HBASE-20756.v2.patch
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Attachment: HBASE-21057.v2.patch
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> HBASE-20756.v2.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-22002) Remove the deprecated methods in Admin interface
[ https://issues.apache.org/jira/browse/HBASE-22002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-22002: Assignee: kevin su > Remove the deprecated methods in Admin interface > > > Key: HBASE-22002 > URL: https://issues.apache.org/jira/browse/HBASE-22002 > Project: HBase > Issue Type: Task > Components: Admin, Client >Reporter: Duo Zhang >Assignee: kevin su >Priority: Major > Fix For: 3.0.0 > > > For API cleanup, and will make the work in HBASE-21718 a little easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785949#comment-16785949 ] kevin su edited comment on HBASE-17094 at 3/6/19 5:56 PM: -- Instead use third party's maven-plugin to generate sitemap.xml I use maven's build-in plugin to generate. I already make sure there is a sitemap.xml under site directory. was (Author: pingsutw): Instead use third party's maven-plugin to generate site-map I use maven's build-in plugin to generate. I already make sure there is a site map under site directory. > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: HBASE-17094.v1.patch Status: Patch Available (was: Reopened) Instead use third party's maven-plugin to generate site-map I use maven's build-in plugin to generate. I already make sure there is a site map under site directory. > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: (was: HBASE-17094.v1.patch) > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785942#comment-16785942
]
kevin su commented on HBASE-20756:
--
[~busbey] sorry for some misunderstanding.
In my patch now I already change to
Version HBASE-3.0.0-SNAPSHOT, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat
May 31 19:56:09 PDT 2014
and this version will change automatically, when the doc-version chnage.
do u mean remove this line ?
don't print this line ?
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785790#comment-16785790
]
kevin su commented on HBASE-20756:
--
[~busbey] How do think this patch or I need to change to version 2.1.3.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Attachment: HBASE-17094.v1.patch > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch, > HBASE-17094.v1.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Attachment: HBASE-20756.v1.patch
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, HBASE-20756.v1.patch,
> image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784544#comment-16784544
]
kevin su edited comment on HBASE-20756 at 3/5/19 3:14 PM:
--
[~xucang] Thanks for you suggestion. I use the variable from config to
represent the version.
was (Author: pingsutw):
[~xucang] Thanks for you suggestion. I use the variable fro m config to
represent the version.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784544#comment-16784544
]
kevin su edited comment on HBASE-20756 at 3/5/19 3:11 PM:
--
[~xucang] Thanks for you suggestion. I use the variable fro m config to
represent the version.
was (Author: pingsutw):
[~xucang] Thanks for you suggestion. I use the variable fro
!image-2019-03-05-23-07-57-228.png! m config to represent the version.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784544#comment-16784544
]
kevin su edited comment on HBASE-20756 at 3/5/19 3:10 PM:
--
[~xucang] Thanks for you suggestion. I use the variable fro
!image-2019-03-05-23-07-57-228.png! m config to represent the version.
was (Author: pingsutw):
[~xucang] Thanks for you suggestion. I use the variable from config to
represent the version.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784544#comment-16784544
]
kevin su edited comment on HBASE-20756 at 3/5/19 3:09 PM:
--
[~xucang] Thanks for you suggestion. I use the variable from config to
represent the version.
was (Author: pingsutw):
[~xucang] Thanks for you suggestion. I use the variable from config to
represent the version.
!image-2019-03-05-23-07-57-228.png!
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784544#comment-16784544
]
kevin su commented on HBASE-20756:
--
[~xucang] Thanks for you suggestion. I use the variable from config to
represent the version.
!image-2019-03-05-23-07-57-228.png!
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Attachment: image-2019-03-05-23-07-57-228.png
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch, image-2019-03-05-23-07-57-228.png
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-20756:
-
Fix Version/s: 3.0.0
Release Note:
I found that this ref guide is about hbase-3.0.0-SNAPSHOT
I think the change should match that version
So use variable to represent the version,so next time we change this ref guide
version, this will automatically change by itself.
Affects Version/s: 3.0.0
Attachment: HBASE-20756.v0.patch
Status: Patch Available (was: Open)
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Affects Versions: 3.0.0
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
> Fix For: 3.0.0
>
> Attachments: HBASE-20756.v0.patch
>
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783597#comment-16783597
]
kevin su commented on HBASE-20756:
--
OK,thanks.
I am going to do this.
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su reassigned HBASE-20756:
Assignee: kevin su
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Minor
> Labels: beginner
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-20756) reference guide examples still contain references to EOM versions
[
https://issues.apache.org/jira/browse/HBASE-20756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783177#comment-16783177
]
kevin su commented on HBASE-20756:
--
[~busbey]
So the job is revise the hbase ref guide.
Change this example to current release version
Anything i miss?
btw, current hbase version is 2.1.3 ?
> reference guide examples still contain references to EOM versions
> -
>
> Key: HBASE-20756
> URL: https://issues.apache.org/jira/browse/HBASE-20756
> Project: HBase
> Issue Type: Bug
> Components: community, documentation
>Reporter: Sean Busbey
>Priority: Minor
> Labels: beginner
>
> the reference guide still has examples that refer to EOM versions. e.g. this
> shell output that has 0.98 in it:
> {code}
> $ echo "describe 'test1'" | ./hbase shell -n
> Version 0.98.3-hadoop2, rd5e65a9144e315bb0a964e7730871af32f5018d5, Sat May 31
> 19:56:09 PDT 2014
> describe 'test1'
> DESCRIPTION ENABLED
> 'test1', {NAME => 'cf', DATA_BLOCK_ENCODING => 'NON true
> E', BLOOMFILTER => 'ROW', REPLICATION_SCOPE => '0',
> VERSIONS => '1', COMPRESSION => 'NONE', MIN_VERSIO
> NS => '0', TTL => 'FOREVER', KEEP_DELETED_CELLS =>
> 'false', BLOCKSIZE => '65536', IN_MEMORY => 'false'
> , BLOCKCACHE => 'true'}
> 1 row(s) in 3.2410 seconds
> {code}
> these should be redone with a current release. Ideally a version in the minor
> release line the docs are for, but even just updating to the stable pointer
> would be a big improvement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775337#comment-16775337 ] kevin su commented on HBASE-17094: -- I will check as well. > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774828#comment-16774828 ] kevin su commented on HBASE-17094: -- Appreciate for [~stack]. help me find something wrong in my patch. Do i need to change anything again or it already resolved. btw, if it's resolved, it means i become contributor in (hbase github)? Do i need to commit in github. > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-17094.v0.patch, HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-20754) quickstart guide should instruct folks to set JAVA_HOME to a JDK installation.
[
https://issues.apache.org/jira/browse/HBASE-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su reassigned HBASE-20754:
Assignee: (was: kevin su)
> quickstart guide should instruct folks to set JAVA_HOME to a JDK installation.
> --
>
> Key: HBASE-20754
> URL: https://issues.apache.org/jira/browse/HBASE-20754
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Sean Busbey
>Priority: Major
> Labels: beginner
>
> The quickstart guide currently instructs folks to set JAVA_HOME, but to the
> wrong place
> {code}
> The JAVA_HOME variable should be set to a directory which contains the
> executable file bin/java. Most modern Linux operating systems provide a
> mechanism, such as /usr/bin/alternatives on RHEL or CentOS, for transparently
> switching between versions of executables such as Java. In this case, you can
> set JAVA_HOME to the directory containing the symbolic link to bin/java,
> which is usually /usr.
> JAVA_HOME=/usr
> {code}
> instead, it should tell folks to point it to a jdk installation and help them
> on how to find that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su reassigned HBASE-17094: Assignee: (was: kevin su) > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Priority: Major > Labels: beginner > Attachments: HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-21057) upgrade to latest spotbugs
[ https://issues.apache.org/jira/browse/HBASE-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773721#comment-16773721 ] kevin su commented on HBASE-21057: -- [~busbey] did you already push ? could i mark it as resolved. > upgrade to latest spotbugs > -- > > Key: HBASE-21057 > URL: https://issues.apache.org/jira/browse/HBASE-21057 > Project: HBase > Issue Type: Task > Components: community, test >Reporter: Sean Busbey >Assignee: kevin su >Priority: Minor > Labels: beginner > Fix For: 3.0.0, 1.6.0, 2.2.0 > > Attachments: HBASE-21057.master.001.patch, HBASE-21057.v0.patch, > HBASE-21057.v1.patch, HBASE-21057.v1.patch > > > we currently rely on [spotbugs definitions from > 3.1.0-RC3|https://github.com/spotbugs/spotbugs/releases/tag/3.1.0_RC3], which > was a pre-release candidate from Jun 2017. > [spotbugs version > 3.1.6|https://github.com/spotbugs/spotbugs/releases/tag/3.1.6] came out about > a month ago. We should update to the latest. > they also have their own maven plugin now. as a stretch goal we could switch > over to that, if it works with yetus. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755925#comment-16755925 ] kevin su edited comment on HBASE-17094 at 1/30/19 9:44 AM: --- Add a sitemap for hbase.apache.org in target/site was (Author: pingsutw): Add a sitemap for hbase.apache.org > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Attachments: HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-17094) Add a sitemap for hbase.apache.org
[ https://issues.apache.org/jira/browse/HBASE-17094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-17094: - Affects Version/s: 3.0.0 Attachment: HBASE-17094.v0.patch Status: Patch Available (was: Open) Add a sitemap for hbase.apache.org > Add a sitemap for hbase.apache.org > -- > > Key: HBASE-17094 > URL: https://issues.apache.org/jira/browse/HBASE-17094 > Project: HBase > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: stack >Assignee: kevin su >Priority: Major > Labels: beginner > Attachments: HBASE-17094.v0.patch > > > We don't have a sitemap. It was pointed out by [~mbrukman]. Lets add one. > Add tooling under dev-support so it gets autogenerated as part of site build. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-18837) HTableMultiplexer behavior during regions split
[
https://issues.apache.org/jira/browse/HBASE-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-18837:
-
Attachment: (was: HBASE-18837.v0.patch)
> HTableMultiplexer behavior during regions split
> ---
>
> Key: HBASE-18837
> URL: https://issues.apache.org/jira/browse/HBASE-18837
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.2
>Reporter: chausson
>Assignee: kevin su
>Priority: Minor
> Attachments: HBASE-18837.v0.patch
>
>
> HTableMultiplexer class mentions following in the javadoc : "If any queue is
> full, the HTableMultiplexer starts to drop the Put requests for that
> particular queue."
> This could be improved by replacing following code in
> HTableMultiplexer.resubmitFailedPut() method :
> {code:title=HTableMultiplexer}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> if (!succ) {
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> {code}
> With :
> {code}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> if (!succ) {
> if (!resubmitFailedPut(ps, oldLoc)) {
>
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-18837) HTableMultiplexer behavior during regions split
[
https://issues.apache.org/jira/browse/HBASE-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-18837:
-
Attachment: (was: HBASE-18837.v0.patch)
> HTableMultiplexer behavior during regions split
> ---
>
> Key: HBASE-18837
> URL: https://issues.apache.org/jira/browse/HBASE-18837
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.2
>Reporter: chausson
>Assignee: kevin su
>Priority: Minor
> Attachments: HBASE-18837.v0.patch
>
>
> HTableMultiplexer class mentions following in the javadoc : "If any queue is
> full, the HTableMultiplexer starts to drop the Put requests for that
> particular queue."
> This could be improved by replacing following code in
> HTableMultiplexer.resubmitFailedPut() method :
> {code:title=HTableMultiplexer}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> if (!succ) {
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> {code}
> With :
> {code}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> if (!succ) {
> if (!resubmitFailedPut(ps, oldLoc)) {
>
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-18837) HTableMultiplexer behavior during regions split
[
https://issues.apache.org/jira/browse/HBASE-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-18837:
-
Attachment: HBASE-18837.v0.patch
Status: Patch Available (was: Open)
HTableMultiplexer behavior during regions split
> HTableMultiplexer behavior during regions split
> ---
>
> Key: HBASE-18837
> URL: https://issues.apache.org/jira/browse/HBASE-18837
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.2
>Reporter: chausson
>Assignee: kevin su
>Priority: Minor
> Attachments: HBASE-18837.v0.patch
>
>
> HTableMultiplexer class mentions following in the javadoc : "If any queue is
> full, the HTableMultiplexer starts to drop the Put requests for that
> particular queue."
> This could be improved by replacing following code in
> HTableMultiplexer.resubmitFailedPut() method :
> {code:title=HTableMultiplexer}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> if (!succ) {
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> {code}
> With :
> {code}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> if (!succ) {
> if (!resubmitFailedPut(ps, oldLoc)) {
>
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HBASE-18837) HTableMultiplexer behavior during regions split
[
https://issues.apache.org/jira/browse/HBASE-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su updated HBASE-18837:
-
Attachment: HBASE-18837.v0.patch
> HTableMultiplexer behavior during regions split
> ---
>
> Key: HBASE-18837
> URL: https://issues.apache.org/jira/browse/HBASE-18837
> Project: HBase
> Issue Type: Improvement
> Components: Client
>Affects Versions: 1.1.2
>Reporter: chausson
>Assignee: kevin su
>Priority: Minor
> Attachments: HBASE-18837.v0.patch
>
>
> HTableMultiplexer class mentions following in the javadoc : "If any queue is
> full, the HTableMultiplexer starts to drop the Put requests for that
> particular queue."
> This could be improved by replacing following code in
> HTableMultiplexer.resubmitFailedPut() method :
> {code:title=HTableMultiplexer}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> if (!succ) {
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> {code}
> With :
> {code}
> try {
> succ = FlushWorker.this.getMultiplexer().put(tableName, failedPut,
> retryCount);
> if (!succ) {
> if (!resubmitFailedPut(ps, oldLoc)) {
>
> FlushWorker.this.getTotalFailedPutCount().incrementAndGet();
> }
> }
> } finally {
> FlushWorker.this.getRetryInQueue().decrementAndGet();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (HBASE-21057) upgrade to latest spotbugs
[ https://issues.apache.org/jira/browse/HBASE-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753712#comment-16753712 ] kevin su commented on HBASE-21057: -- [~busbey] would you help me commit the code. I am glad to contribute to hbase > upgrade to latest spotbugs > -- > > Key: HBASE-21057 > URL: https://issues.apache.org/jira/browse/HBASE-21057 > Project: HBase > Issue Type: Task > Components: community, test >Affects Versions: 3.0.0 >Reporter: Sean Busbey >Assignee: kevin su >Priority: Minor > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-21057.v0.patch, HBASE-21057.v1.patch, > HBASE-21057.v1.patch > > > we currently rely on [spotbugs definitions from > 3.1.0-RC3|https://github.com/spotbugs/spotbugs/releases/tag/3.1.0_RC3], which > was a pre-release candidate from Jun 2017. > [spotbugs version > 3.1.6|https://github.com/spotbugs/spotbugs/releases/tag/3.1.6] came out about > a month ago. We should update to the latest. > they also have their own maven plugin now. as a stretch goal we could switch > over to that, if it works with yetus. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-21057) upgrade to latest spotbugs
[ https://issues.apache.org/jira/browse/HBASE-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kevin su updated HBASE-21057: - Resolution: Fixed Status: Resolved (was: Patch Available) upgrade to latest spotbugs > upgrade to latest spotbugs > -- > > Key: HBASE-21057 > URL: https://issues.apache.org/jira/browse/HBASE-21057 > Project: HBase > Issue Type: Task > Components: community, test >Affects Versions: 3.0.0 >Reporter: Sean Busbey >Assignee: kevin su >Priority: Minor > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-21057.v0.patch, HBASE-21057.v1.patch, > HBASE-21057.v1.patch > > > we currently rely on [spotbugs definitions from > 3.1.0-RC3|https://github.com/spotbugs/spotbugs/releases/tag/3.1.0_RC3], which > was a pre-release candidate from Jun 2017. > [spotbugs version > 3.1.6|https://github.com/spotbugs/spotbugs/releases/tag/3.1.6] came out about > a month ago. We should update to the latest. > they also have their own maven plugin now. as a stretch goal we could switch > over to that, if it works with yetus. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (HBASE-21057) upgrade to latest spotbugs
[ https://issues.apache.org/jira/browse/HBASE-21057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753328#comment-16753328 ] kevin su commented on HBASE-21057: -- [~busbey] it works,could I mark it as resolved. > upgrade to latest spotbugs > -- > > Key: HBASE-21057 > URL: https://issues.apache.org/jira/browse/HBASE-21057 > Project: HBase > Issue Type: Task > Components: community, test >Affects Versions: 3.0.0 >Reporter: Sean Busbey >Assignee: kevin su >Priority: Minor > Labels: beginner > Fix For: 3.0.0 > > Attachments: HBASE-21057.v0.patch, HBASE-21057.v1.patch, > HBASE-21057.v1.patch > > > we currently rely on [spotbugs definitions from > 3.1.0-RC3|https://github.com/spotbugs/spotbugs/releases/tag/3.1.0_RC3], which > was a pre-release candidate from Jun 2017. > [spotbugs version > 3.1.6|https://github.com/spotbugs/spotbugs/releases/tag/3.1.6] came out about > a month ago. We should update to the latest. > they also have their own maven plugin now. as a stretch goal we could switch > over to that, if it works with yetus. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (HBASE-20754) quickstart guide should instruct folks to set JAVA_HOME to a JDK installation.
[
https://issues.apache.org/jira/browse/HBASE-20754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kevin su reassigned HBASE-20754:
Assignee: kevin su
> quickstart guide should instruct folks to set JAVA_HOME to a JDK installation.
> --
>
> Key: HBASE-20754
> URL: https://issues.apache.org/jira/browse/HBASE-20754
> Project: HBase
> Issue Type: Bug
> Components: documentation
>Reporter: Sean Busbey
>Assignee: kevin su
>Priority: Major
> Labels: beginner
>
> The quickstart guide currently instructs folks to set JAVA_HOME, but to the
> wrong place
> {code}
> The JAVA_HOME variable should be set to a directory which contains the
> executable file bin/java. Most modern Linux operating systems provide a
> mechanism, such as /usr/bin/alternatives on RHEL or CentOS, for transparently
> switching between versions of executables such as Java. In this case, you can
> set JAVA_HOME to the directory containing the symbolic link to bin/java,
> which is usually /usr.
> JAVA_HOME=/usr
> {code}
> instead, it should tell folks to point it to a jdk installation and help them
> on how to find that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
