[ 
https://issues.apache.org/jira/browse/HDFS-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782897#comment-17782897
 ] 

ASF GitHub Bot commented on HDFS-17249:
---------------------------------------

GauthamBanasandra commented on PR #6249:
URL: https://github.com/apache/hadoop/pull/6249#issuecomment-1793473155

   > > > @LiuGuH could you please file a new bug on issues.apache.org and use 
it instead of tagging to `HDFS-17248`?
   > > 
   > > 
   > > Sure. I can. But what's the difference between them that I need to 
notice? Thanks
   > 
   > @LiuGuH in the Hadoop community we normally follow the convention where 
the bug title in JIRA matches that of the Github PR.
   > 
   > In this case, 
[HDFS-17248](https://issues.apache.org/jira/browse/HDFS-17248) in JIRA has the 
title `Fix shaded client for building Hadoop on Windows`. So, it can't have the 
title that you have put currently (`Fix isValidName error`).
   > 
   > Thus, you'll need to create a new JIRA for this.
   
   @LiuGuH I apologize for the confusion. The JIRA that you had created 
originally (HDFS-17248) had no issues. I overlooked the number and thought it 
was the same as HDFS-17246.
   
   Anyway, we can go ahead with what you've tagged currently.




> Fix TestDFSUtil.testIsValidName() run failure
> ---------------------------------------------
>
>                 Key: HDFS-17249
>                 URL: https://issues.apache.org/jira/browse/HDFS-17249
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: liuguanghua
>            Assignee: liuguanghua
>            Priority: Minor
>              Labels: pull-request-available
>
> TestDFSUtil.testIsValidName runs failed when  
> assertFalse(DFSUtil.isValidName("/foo/:/bar")) , fixed it. 
> Add test case in TestDFSUtil.testIsValidName.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to