[ 
https://issues.apache.org/jira/browse/HADOOP-17592?focusedWorklogId=569504&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-569504
 ]

ASF GitHub Bot logged work on HADOOP-17592:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Mar/21 02:43
            Start Date: 22/Mar/21 02:43
    Worklog Time Spent: 10m 
      Work Description: aajisaka merged pull request #2780:
URL: https://github.com/apache/hadoop/pull/2780


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 569504)
    Time Spent: 40m  (was: 0.5h)

> Fix the wrong CIDR range example in Proxy User documentation
> ------------------------------------------------------------
>
>                 Key: HADOOP-17592
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17592
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 3.2.2
>            Reporter: Kwangsun Noh
>            Priority: Trivial
>              Labels: pull-request-available
>         Attachments: HADOOP-17592.patch
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> The CIDR range example on the Proxy user description page is wrong.
>  
> In the Configurations section of Proxy user page, CIDR format 10.222.0.0/16 
> means 10.222.0.0-15.
>  
> But It's not true. the CIDR format 10.222.0.0/16 means 
> 10.222.0.0-10.222.255.255.
>  
> as-is : hosts in the range `10.222.0.0-15` and
> to-be : hosts in the range `10.222.0.0-10.222.255.255` and



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to