hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Leblang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18020) Update API Compliance Checker to Incorporate Improvements Done in Hadoop
Date Thu, 11 May 2017 22:08:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007286#comment-16007286

Alex Leblang commented on HBASE-18020:

If I'm not mistaken, I believe that we currently do not have an hbase project pylint rc file.
We should make one! That would presumably require us to decide on some stylistic questions.
I kept the spacing here at 2 spaces as that's how it was in hadoop. I couldn't find a uniform
standard in the hbase code base. Some files go with two spaces and other use four. In fact,
this file seems to use both (which is ironic considering its name) https://github.com/apache/hbase/blob/master/dev-support/checkstyle_report.py

> Update API Compliance Checker to Incorporate Improvements Done in Hadoop
> ------------------------------------------------------------------------
>                 Key: HBASE-18020
>                 URL: https://issues.apache.org/jira/browse/HBASE-18020
>             Project: HBase
>          Issue Type: Improvement
>          Components: API, community
>            Reporter: Alex Leblang
>            Assignee: Alex Leblang
>             Fix For: 2.0.0
>         Attachments: HBASE-18020.0.patch
> Recently the Hadoop community has made a number of improvements in their api compliance
checker based on feedback from the hbase and kudu community. We should adopt these changes

This message was sent by Atlassian JIRA

View raw message