[jira] [Commented] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146819#comment-17146819 ] Qilin Cao commented on HBASE-24516: --- hi, [~ndimiduk] this is not needed on master. > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 2.3.0, 2.2.6 > > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-22380. The public > secureBulkLoadHFiles method parameter copyFiles was not passed to the > refactoring method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128245#comment-17128245 ] Qilin Cao edited comment on HBASE-24516 at 6/8/20, 12:30 PM: - [~zhangduo]，the PR is #1868, [~wchevreuil], the Jira description has already been updated, i make a mistake, this problem is caused by HBASE-22380, not by HBASE-23136. was (Author: qilin cao): [~zhangduo]，the PR is #1868, [~wchevreuil], the Jira description has already been updated. > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-22380. The public > secureBulkLoadHFiles method parameter copyFiles was not passed to the > refactoring method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-22380. The public secureBulkLoadHFiles method parameter copyFiles was not passed to the refactoring method. (was: When refactor SecureBulkLoadClient started in HBASE-23136. The public secureBulkLoadHFiles method parameter copyFiles was not passed to the refactoring method.) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-22380. The public > secureBulkLoadHFiles method parameter copyFiles was not passed to the > refactoring method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128245#comment-17128245 ] Qilin Cao commented on HBASE-24516: --- [~zhangduo]，the PR is #1868, [~wchevreuil], the Jira description has already been updated. > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The public > secureBulkLoadHFiles method parameter copyFiles was not passed to the > refactoring method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-23136. The public secureBulkLoadHFiles method parameter copyFiles was not passed to the refactoring method. (was: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter copyFiles was not passed in a public secureBulkLoadHFiles method in SecureBulkLoadClient.java.) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The public > secureBulkLoadHFiles method parameter copyFiles was not passed to the > refactoring method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter copyFiles was not passed in a public secureBulkLoadHFiles method in SecureBulkLoadClient.java. (was: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter copyFiles was not passed in a public secureBulkLoadHFiles method in ) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The parameter > copyFiles was not passed in a public secureBulkLoadHFiles method in > SecureBulkLoadClient.java. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter copyFiles was not passed in a public secureBulkLoadHFiles method in (was: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter Parameter pass incorrectly pass incorrectly ) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The parameter > copyFiles was not passed in a public secureBulkLoadHFiles method in -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter Parameter pass incorrectly pass incorrectly (was: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter pass incorrectly ) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The parameter > Parameter pass incorrectly pass incorrectly -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Summary: Parameter copyFiles should be passed in SecureBulkLoadClient (was: Parameter pass incorrectly when refactor SecureBulkLoadClient) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > Parameter pass incorrectly when refactor SecureBulkLoadClient started in > HBASE-23136. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter copyFiles should be passed in SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Description: When refactor SecureBulkLoadClient started in HBASE-23136. The parameter pass incorrectly (was: Parameter pass incorrectly when refactor SecureBulkLoadClient started in HBASE-23136.) > Parameter copyFiles should be passed in SecureBulkLoadClient > > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > When refactor SecureBulkLoadClient started in HBASE-23136. The parameter > pass incorrectly -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24516) Parameter pass incorrectly when refactor SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128041#comment-17128041 ] Qilin Cao commented on HBASE-24516: --- [~zhangduo] I will open a PR later. > Parameter pass incorrectly when refactor SecureBulkLoadClient > - > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > Parameter pass incorrectly when refactor SecureBulkLoadClient started in > HBASE-23136. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (HBASE-24516) Parameter pass incorrectly when refactor SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127938#comment-17127938 ] Qilin Cao edited comment on HBASE-24516 at 6/8/20, 8:11 AM: Submit a patch! thks! was (Author: qilin cao): commit a patch! thks! > Parameter pass incorrectly when refactor SecureBulkLoadClient > - > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.2, 2.2.5 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > Parameter pass incorrectly when refactor SecureBulkLoadClient started in > HBASE-23136. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-24516) Parameter pass incorrectly when refactor SecureBulkLoadClient
[ https://issues.apache.org/jira/browse/HBASE-24516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-24516: -- Attachment: HBASE-24516.branch-2.2.patch Status: Patch Available (was: Open) commit a patch! thks! > Parameter pass incorrectly when refactor SecureBulkLoadClient > - > > Key: HBASE-24516 > URL: https://issues.apache.org/jira/browse/HBASE-24516 > Project: HBase > Issue Type: Bug > Components: Replication >Affects Versions: 2.2.5, 2.2.2 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-24516.branch-2.2.patch > > > Parameter pass incorrectly when refactor SecureBulkLoadClient started in > HBASE-23136. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24516) Parameter pass incorrectly when refactor SecureBulkLoadClient
Qilin Cao created HBASE-24516: - Summary: Parameter pass incorrectly when refactor SecureBulkLoadClient Key: HBASE-24516 URL: https://issues.apache.org/jira/browse/HBASE-24516 Project: HBase Issue Type: Bug Components: Replication Affects Versions: 2.2.5, 2.2.2 Reporter: Qilin Cao Assignee: Qilin Cao Parameter pass incorrectly when refactor SecureBulkLoadClient started in HBASE-23136. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Affects Version/s: (was: 3.0.0) > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning infomation, I must to debug the code to find > out the real cause of it. Actually, it was caused by hbase client connection . > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems becomes > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Description: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning infomation, I must to debug the code to find out the real cause of it. Actually, it was caused by hbase client connection . I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems becomes simple. was: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by hbase client connection . I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems becomes simple. > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning infomation, I must to debug the code to find > out the real cause of it. Actually, it was caused by hbase client connection . > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems becomes > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Description: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by hbase client connection . I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems becomes simple. was: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by hbase client connection. I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems become simple. > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by hbase client connection . > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems becomes > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Description: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by hbase client connection. I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems become simple. was: The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by connection. I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems become simple. > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by hbase client connection. > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems become > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Attachment: (was: -HBASE-22683-v1.patch) > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by connection. > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems become > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Attachment: -HBASE-22683-v1.patch Status: Patch Available (was: Open) submit a patch > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch, -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by connection. > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems become > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-22683: -- Attachment: -HBASE-22683-v1.patch > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by connection. > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems become > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
[ https://issues.apache.org/jira/browse/HBASE-22683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao reassigned HBASE-22683: - Assignee: Qilin Cao > IOException should be recorded in log file when rest server obtain hbase > connection > --- > > Key: HBASE-22683 > URL: https://issues.apache.org/jira/browse/HBASE-22683 > Project: HBase > Issue Type: Improvement > Components: REST >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: -HBASE-22683-v1.patch > > > The REST server is successfully started, when I send a http request to the > server, it response "Unavailable" result.Then I check the log file, there is > no obviously error or warning logs, I must to debug the code to find out the > real cause of it. Actually, it was caused by connection. > I think it is neccessary to record the class RESTServlet.java getAdmin() and > getTable() IOException to log file, it can make finding problems become > simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (HBASE-22683) IOException should be recorded in log file when rest server obtain hbase connection
Qilin Cao created HBASE-22683: - Summary: IOException should be recorded in log file when rest server obtain hbase connection Key: HBASE-22683 URL: https://issues.apache.org/jira/browse/HBASE-22683 Project: HBase Issue Type: Improvement Components: REST Affects Versions: 3.0.0 Reporter: Qilin Cao The REST server is successfully started, when I send a http request to the server, it response "Unavailable" result.Then I check the log file, there is no obviously error or warning logs, I must to debug the code to find out the real cause of it. Actually, it was caused by connection. I think it is neccessary to record the class RESTServlet.java getAdmin() and getTable() IOException to log file, it can make finding problems become simple. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Attachment: HBASE-19521-v3.patch Patch 3 to repair the checkstyle error! > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch, > HBASE-19521-v3.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Attachment: HBASE-19521-v2.patch > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Attachment: (was: HBASE-19521-v2.patch) > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294482#comment-16294482 ] Qilin Cao commented on HBASE-19521: --- [~tedyu]Sorry, It is available now. > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Status: Patch Available (was: In Progress) > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Attachment: HBASE-19521-v2.patch update the patch log level! > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16294423#comment-16294423 ] Qilin Cao edited comment on HBASE-19521 at 12/18/17 1:02 AM: - [~yuzhih...@gmail.com]update the patch log level! was (Author: qilin cao): update the patch log level! > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch, HBASE-19521-v2.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Attachment: HBASE-19521-v1.patch submit a patch! > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > Attachments: HBASE-19521-v1.patch > > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Work started] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-19521 started by Qilin Cao. - > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Description: When HBase master configuration is not set hfile.format.version to 3, and user already run compact mob, this operation will cause compactor write V2 ref hfile, the result is that user can not scan the correct cell value since the mob cell ref tags are not written. So it is necessary to check the hfile version before to run mob compaction. (was: When HBase master configuration is not set hfile.format.version to 3, and user already run compact mob, this operation will cause compactor write V2 hfile, the result is that user can not scan the correct cell value since the mob cell ref tags are not written. So it is necessary to check the hfile version before to run mob compaction.) > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > ref hfile, the result is that user can not scan the correct cell value since > the mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Priority: Critical (was: Minor) > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Critical > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > hfile, the result is that user can not scan the correct cell value since the > mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19521: -- Component/s: mob > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Priority: Minor > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > hfile, the result is that user can not scan the correct cell value since the > mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (HBASE-19521) HBase mob compaction need to check hfile version
[ https://issues.apache.org/jira/browse/HBASE-19521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao reassigned HBASE-19521: - Assignee: Qilin Cao > HBase mob compaction need to check hfile version > > > Key: HBASE-19521 > URL: https://issues.apache.org/jira/browse/HBASE-19521 > Project: HBase > Issue Type: Improvement > Components: Compaction, mob >Affects Versions: 2.0.0, 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > > When HBase master configuration is not set hfile.format.version to 3, and > user already run compact mob, this operation will cause compactor write V2 > hfile, the result is that user can not scan the correct cell value since the > mob cell ref tags are not written. So it is necessary to check the hfile > version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19521) HBase mob compaction need to check hfile version
Qilin Cao created HBASE-19521: - Summary: HBase mob compaction need to check hfile version Key: HBASE-19521 URL: https://issues.apache.org/jira/browse/HBASE-19521 Project: HBase Issue Type: Improvement Components: Compaction Affects Versions: 2.0.0, 3.0.0 Reporter: Qilin Cao Priority: Minor When HBase master configuration is not set hfile.format.version to 3, and user already run compact mob, this operation will cause compactor write V2 hfile, the result is that user can not scan the correct cell value since the mob cell ref tags are not written. So it is necessary to check the hfile version before to run mob compaction. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Fix Version/s: (was: 1.2.0) Release Note: If BigDecimal is stored as value, and you need to add a matched comparator to the value filter when scanning, a BigDecimalComparator can be used. I already fill out the release note, thks! > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch, > HBASE-19103-trunk-v3.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240013#comment-16240013
]
Qilin Cao commented on HBASE-19076:
---
{code:java}
Where do you get the failure mentioned in the description? When running mvn
clean install against the current master the enforcer rule passes.
{code}
[~Jan Hentschel]This happened when I run mvn clean package assembly:single
-DskipTests.
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Status: Patch Available (was: Open) > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 3.0.0, 1.2.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch, > HBASE-19103-trunk-v3.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-trunk-v3.patch > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch, > HBASE-19103-trunk-v3.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233542#comment-16233542 ] Qilin Cao commented on HBASE-19103: --- [~tedyu][~Jan Hentschel] Thanks for your suggestion! I should optimize it. > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-trunk-v2.patch > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: (was: HBASE-19103-trunk-v2.patch) > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-1.2.0-v2.patch Add hashCode() and equals() to BigDecimalComparator, thks! > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-1.2.0-v2.patch, > HBASE-19103-trunk-v1.patch, HBASE-19103-trunk-v2.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-trunk-v2.patch > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-trunk-v1.patch, > HBASE-19103-trunk-v2.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-trunk-v1.patch Patch for trunk > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-trunk-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Fix Version/s: 3.0.0 > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0, 3.0.0 > > Attachments: HBASE-19103-1.2.0-v1.patch, HBASE-19103-trunk-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16224543#comment-16224543 ] Qilin Cao commented on HBASE-19103: --- [~tedyu] OK! I will do it later. > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0 > > Attachments: HBASE-19103-1.2.0-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Fix Version/s: 1.2.0 Status: Patch Available (was: Open) Patch for hbase1.2.0 > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 1.2.0 > > Attachments: HBASE-19103-1.2.0-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Attachment: HBASE-19103-1.2.0-v1.patch > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-19103-1.2.0-v1.patch > > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-19091) Code annotation wrote "BinaryComparator" instead of "LongComparator"
[ https://issues.apache.org/jira/browse/HBASE-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16221873#comment-16221873 ] Qilin Cao commented on HBASE-19091: --- Thanks for the review! > Code annotation wrote "BinaryComparator" instead of "LongComparator" > > > Key: HBASE-19091 > URL: https://issues.apache.org/jira/browse/HBASE-19091 > Project: HBase > Issue Type: Improvement > Components: Client >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2, 1.5.0, 1.2.7 > > Attachments: HBASE-19091-v1.patch > > > LongComparator class code annotation wrote "BinaryComparator" instead of > "LongComparator" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19103) Add BigDecimalComparator for filter
[ https://issues.apache.org/jira/browse/HBASE-19103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19103: -- Description: Should I add BigDecimalComparator for filter? Some scenarios need to calculate the data accurately may use it. (was: Should I add BigDecimalComparator for filter? Some scenarios need to calculate the data accurately may be use it.) > Add BigDecimalComparator for filter > --- > > Key: HBASE-19103 > URL: https://issues.apache.org/jira/browse/HBASE-19103 > Project: HBase > Issue Type: New Feature > Components: Client >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > > Should I add BigDecimalComparator for filter? Some scenarios need to > calculate the data accurately may use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19103) Add BigDecimalComparator for filter
Qilin Cao created HBASE-19103: - Summary: Add BigDecimalComparator for filter Key: HBASE-19103 URL: https://issues.apache.org/jira/browse/HBASE-19103 Project: HBase Issue Type: New Feature Components: Client Reporter: Qilin Cao Assignee: Qilin Cao Priority: Minor Should I add BigDecimalComparator for filter? Some scenarios need to calculate the data accurately may be use it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qilin Cao updated HBASE-19076:
--
Priority: Major (was: Blocker)
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19091) Code annotation wrote "BinaryComparator" instead of "LongComparator"
[ https://issues.apache.org/jira/browse/HBASE-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19091: -- Status: Patch Available (was: Open) > Code annotation wrote "BinaryComparator" instead of "LongComparator" > > > Key: HBASE-19091 > URL: https://issues.apache.org/jira/browse/HBASE-19091 > Project: HBase > Issue Type: Improvement > Components: Client >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-19091-v1.patch > > > LongComparator class code annotation wrote "BinaryComparator" instead of > "LongComparator" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19091) Code annotation wrote "BinaryComparator" instead of "LongComparator"
[ https://issues.apache.org/jira/browse/HBASE-19091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-19091: -- Attachment: HBASE-19091-v1.patch submit a patch! > Code annotation wrote "BinaryComparator" instead of "LongComparator" > > > Key: HBASE-19091 > URL: https://issues.apache.org/jira/browse/HBASE-19091 > Project: HBase > Issue Type: Improvement > Components: Client >Affects Versions: 3.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-19091-v1.patch > > > LongComparator class code annotation wrote "BinaryComparator" instead of > "LongComparator" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-19091) Code annotation wrote "BinaryComparator" instead of "LongComparator"
Qilin Cao created HBASE-19091: - Summary: Code annotation wrote "BinaryComparator" instead of "LongComparator" Key: HBASE-19091 URL: https://issues.apache.org/jira/browse/HBASE-19091 Project: HBase Issue Type: Improvement Components: Client Affects Versions: 3.0.0 Reporter: Qilin Cao Assignee: Qilin Cao Priority: Minor LongComparator class code annotation wrote "BinaryComparator" instead of "LongComparator" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qilin Cao updated HBASE-19076:
--
Description:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
with the hbase-error-prone module.
{code}
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(min-maven-min-java-banned-xerces) @ hbase-error-prone ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
hbase-error-prone ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
with message:
We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
was:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
with the hbase-error-prone module.
{code}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(min-maven-min-java-banned-xerces) @ hbase-error-prone ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
hbase-error-prone ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
with message:
We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Blocker
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qilin Cao updated HBASE-19076:
--
Status: Patch Available (was: Open)
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Blocker
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone
> ---
> [INFO] Deleting
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qilin Cao updated HBASE-19076:
--
Attachment: HBASE-19076.patch
submit a patch!
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Blocker
> Attachments: HBASE-19076.patch
>
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone
> ---
> [INFO] Deleting
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
[
https://issues.apache.org/jira/browse/HBASE-19076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qilin Cao updated HBASE-19076:
--
Description:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
with the hbase-error-prone module.
{code}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(min-maven-min-java-banned-xerces) @ hbase-error-prone ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
hbase-error-prone ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
with message:
We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{code}
was:
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
with the hbase-error-prone module.
{panel:title=My title}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(min-maven-min-java-banned-xerces) @ hbase-error-prone ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
hbase-error-prone ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
with message:
We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{panel}
> Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
>
>
> Key: HBASE-19076
> URL: https://issues.apache.org/jira/browse/HBASE-19076
> Project: HBase
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Qilin Cao
>Assignee: Qilin Cao
>Priority: Blocker
>
> After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
> with the hbase-error-prone module.
> {code}
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone
> ---
> [INFO] Deleting
> /home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
> (min-maven-min-java-banned-xerces) @ hbase-error-prone ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
> hbase-error-prone ---
> [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
> with message:
> We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
> Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
> Use 'mvn dependency:tree' to locate the source of the banned dependencies.
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (HBASE-19076) Ensure findbugs jsr305 jar isn't present in hbase-error-prone module
Qilin Cao created HBASE-19076:
-
Summary: Ensure findbugs jsr305 jar isn't present in
hbase-error-prone module
Key: HBASE-19076
URL: https://issues.apache.org/jira/browse/HBASE-19076
Project: HBase
Issue Type: Bug
Components: dependencies
Affects Versions: 3.0.0
Reporter: Qilin Cao
Assignee: Qilin Cao
Priority: Blocker
After HBASE-16321 ensure findbugs jsr305 jar isn't present, we have failures
with the hbase-error-prone module.
{panel:title=My title}
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ hbase-error-prone ---
[INFO] Deleting
/home/caoqilin/Codebase/github/hbase/hbase-build-support/hbase-error-prone/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(min-maven-min-java-banned-xerces) @ hbase-error-prone ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (banned-jsr305) @
hbase-error-prone ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed
with message:
We don't allow the JSR305 jar from the Findbugs project, see HBASE-16321.
Found Banned Dependency: com.google.code.findbugs:jsr305:jar:1.3.9
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{panel}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058565#comment-16058565 ] Qilin Cao edited comment on HBASE-18119 at 6/23/17 12:28 AM: - OK, [~zyork] I recreated a patch. was (Author: qilin cao): OK, I recreated a patch. > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v3.patch, > HBASE-18119-v4.patch, HBASE-18119-v5.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v5.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v3.patch, > HBASE-18119-v4.patch, HBASE-18119-v5.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: (was: HBASE-18119-v5.patch) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v3.patch, > HBASE-18119-v4.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: (was: HBASE-18119-v2.patch) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v3.patch, > HBASE-18119-v4.patch, HBASE-18119-v5.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16058565#comment-16058565 ] Qilin Cao commented on HBASE-18119: --- OK, I recreated a patch. > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch, HBASE-18119-v4.patch, HBASE-18119-v5.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v5.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch, HBASE-18119-v4.patch, HBASE-18119-v5.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18252) Resolve BaseLoadBalancer bad practice warnings
[ https://issues.apache.org/jira/browse/HBASE-18252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18252: -- Attachment: HBASE-18252-v1.patch submit an improvement patch. > Resolve BaseLoadBalancer bad practice warnings > -- > > Key: HBASE-18252 > URL: https://issues.apache.org/jira/browse/HBASE-18252 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18252-v1.patch > > > FindBugs Report BaseLoadBalancer class had bad practice warnings, let's > resolve it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18252) Resolve BaseLoadBalancer bad practice warnings
[ https://issues.apache.org/jira/browse/HBASE-18252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18252: -- Affects Version/s: 2.0.0 > Resolve BaseLoadBalancer bad practice warnings > -- > > Key: HBASE-18252 > URL: https://issues.apache.org/jira/browse/HBASE-18252 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > > FindBugs Report BaseLoadBalancer class had bad practice warnings, let's > resolve it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (HBASE-18252) Resolve BaseLoadBalancer bad practice warnings
Qilin Cao created HBASE-18252: - Summary: Resolve BaseLoadBalancer bad practice warnings Key: HBASE-18252 URL: https://issues.apache.org/jira/browse/HBASE-18252 Project: HBase Issue Type: Improvement Reporter: Qilin Cao Assignee: Qilin Cao Priority: Minor FindBugs Report BaseLoadBalancer class had bad practice warnings, let's resolve it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056786#comment-16056786 ] Qilin Cao edited comment on HBASE-18119 at 6/21/17 1:45 AM: Hi, [~zyork],I think my original test code(modify key/value then expect exception) was wrong, for the configuration is only created once, if the test case runs successfully, the modified key/value may affect the class other tests. was (Author: qilin cao): Hi, [~zyork],I think my original test code(modify key/value then expect exception) was wrong, for the configuration is only created once, if I modify the configuration key/value successfully, this may affect the class other tests. > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch, HBASE-18119-v4.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v4.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch, HBASE-18119-v4.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056786#comment-16056786 ] Qilin Cao commented on HBASE-18119: --- Hi, [~zyork],I think my original test code(modify key/value then expect exception) was wrong, for the configuration is only created once, if I modify the configuration key/value successfully, this may affect the class other tests. > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v3.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch, > HBASE-18119-v3.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v2.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: (was: HBASE-18119-v2.patch) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16053537#comment-16053537 ] Qilin Cao commented on HBASE-18119: --- [~zyork]Thanks for reply. I was just confused for recording the message to info? It seems that I was worrying too much. The test mistakes you point out are correct, I will optimize the test code. > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v2.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch, HBASE-18119-v2.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Description: It is confused when I read the HFile.checkHFileVersion method, so I change the if expression. Simultaneously, I change ChecksumUtil the info log level to trace. (was: It is confused when I read the HFile.checkHFileVersion method, so I change the source code. Simultaneously, I change ChecksumUtil the info log level to trace.) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the if expression. Simultaneously, I change ChecksumUtil the info log level > to trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Issue Comment Deleted] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Comment: was deleted (was: Unit tests of this change are already included by original hbase-server unit test cases. thks!) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v1.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: (was: HBASE-18119-v1.patch) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: (was: HBASE-18119-v1.patch) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v1.patch > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16026025#comment-16026025 ] Qilin Cao commented on HBASE-18119: --- Unit tests of this change are already included by original hbase-server unit test cases. thks! > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Affects Version/s: 2.0.0 Status: Patch Available (was: Open) > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18119: -- Attachment: HBASE-18119-v1.patch Submit a patch! > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > Attachments: HBASE-18119-v1.patch > > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
[ https://issues.apache.org/jira/browse/HBASE-18119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao reassigned HBASE-18119: - Assignee: Qilin Cao > Improve HFile readability and modify ChecksumUtil log level > --- > > Key: HBASE-18119 > URL: https://issues.apache.org/jira/browse/HBASE-18119 > Project: HBase > Issue Type: Improvement >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Minor > > It is confused when I read the HFile.checkHFileVersion method, so I change > the source code. Simultaneously, I change ChecksumUtil the info log level to > trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-18119) Improve HFile readability and modify ChecksumUtil log level
Qilin Cao created HBASE-18119: - Summary: Improve HFile readability and modify ChecksumUtil log level Key: HBASE-18119 URL: https://issues.apache.org/jira/browse/HBASE-18119 Project: HBase Issue Type: Improvement Reporter: Qilin Cao Priority: Minor It is confused when I read the HFile.checkHFileVersion method, so I change the source code. Simultaneously, I change ChecksumUtil the info log level to trace. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18007) Clean up rest model code
[ https://issues.apache.org/jira/browse/HBASE-18007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18007: -- Attachment: HBASE-18007-v001.patch > Clean up rest model code > - > > Key: HBASE-18007 > URL: https://issues.apache.org/jira/browse/HBASE-18007 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Attachments: HBASE-18007-v001.patch > > > HBase rest model has many dead code, let's remove the dead code and clean up > warnings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18007) Clean up rest model code
[ https://issues.apache.org/jira/browse/HBASE-18007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18007: -- Attachment: (was: HBASE-18007-v001.patch) > Clean up rest model code > - > > Key: HBASE-18007 > URL: https://issues.apache.org/jira/browse/HBASE-18007 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > > HBase rest model has many dead code, let's remove the dead code and clean up > warnings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18007) Clean up rest model code
[ https://issues.apache.org/jira/browse/HBASE-18007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18007: -- Attachment: HBASE-18007-v001.patch > Clean up rest model code > - > > Key: HBASE-18007 > URL: https://issues.apache.org/jira/browse/HBASE-18007 > Project: HBase > Issue Type: Improvement >Reporter: Qilin Cao >Priority: Trivial > Attachments: HBASE-18007-v001.patch > > > HBase rest model has many dead code, let's remove the dead code and clean up > warnings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-18007) Clean up rest model code
[ https://issues.apache.org/jira/browse/HBASE-18007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-18007: -- Assignee: Qilin Cao Affects Version/s: 2.0.0 Status: Patch Available (was: Open) > Clean up rest model code > - > > Key: HBASE-18007 > URL: https://issues.apache.org/jira/browse/HBASE-18007 > Project: HBase > Issue Type: Improvement >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Attachments: HBASE-18007-v001.patch > > > HBase rest model has many dead code, let's remove the dead code and clean up > warnings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-18007) Clean up rest model code
Qilin Cao created HBASE-18007: - Summary: Clean up rest model code Key: HBASE-18007 URL: https://issues.apache.org/jira/browse/HBASE-18007 Project: HBase Issue Type: Improvement Reporter: Qilin Cao Priority: Trivial HBase rest model has many dead code, let's remove the dead code and clean up warnings. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17835) Spelling mistakes in the Java source
[ https://issues.apache.org/jira/browse/HBASE-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-17835: -- Status: Patch Available (was: Reopened) > Spelling mistakes in the Java source > > > Key: HBASE-17835 > URL: https://issues.apache.org/jira/browse/HBASE-17835 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17835-001.patch > > > I found spelling mistakes in the hbase java source files viz. recieved > instead of received, and SpanReciever instead of SpanReceiver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (HBASE-17835) Spelling mistakes in the Java source
[ https://issues.apache.org/jira/browse/HBASE-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao reopened HBASE-17835: --- > Spelling mistakes in the Java source > > > Key: HBASE-17835 > URL: https://issues.apache.org/jira/browse/HBASE-17835 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17835-001.patch > > > I found spelling mistakes in the hbase java source files viz. recieved > instead of received, and SpanReciever instead of SpanReceiver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (HBASE-17835) Spelling mistakes in the Java source
[ https://issues.apache.org/jira/browse/HBASE-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qilin Cao updated HBASE-17835: -- Resolution: Fixed Status: Resolved (was: Patch Available) > Spelling mistakes in the Java source > > > Key: HBASE-17835 > URL: https://issues.apache.org/jira/browse/HBASE-17835 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17835-001.patch > > > I found spelling mistakes in the hbase java source files viz. recieved > instead of received, and SpanReciever instead of SpanReceiver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (HBASE-17835) Spelling mistakes in the Java source
[ https://issues.apache.org/jira/browse/HBASE-17835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15985867#comment-15985867 ] Qilin Cao edited comment on HBASE-17835 at 4/27/17 11:08 AM: - [~busbey]I had already updated the patch. thks! was (Author: qilin cao): [~busbey]I fix it. thks! > Spelling mistakes in the Java source > > > Key: HBASE-17835 > URL: https://issues.apache.org/jira/browse/HBASE-17835 > Project: HBase > Issue Type: Improvement > Components: documentation >Affects Versions: 2.0.0 >Reporter: Qilin Cao >Assignee: Qilin Cao >Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-17835-001.patch > > > I found spelling mistakes in the hbase java source files viz. recieved > instead of received, and SpanReciever instead of SpanReceiver -- This message was sent by Atlassian JIRA (v6.3.15#6346)
