[
https://issues.apache.org/jira/browse/HDFS-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HDFS-1807:
-------------------------------------
Description:
Running TestCLI in a real cluster environment I came across a problem where a
regexp like this
{noformat}
^-rw-r--r--( )*1( )*[a-z]*( )*supergroup( )*.*
{noformat}
doesn't match
{noformat}
-rw-r--r-- 1 testuser1 supergroup 0 2011-04-05 13:21
/tmp/testcli/file1
{noformat}
It turns out that {{[a-z]*}} doesn't match username {{testuser1}}
It'd be nice to have a regexp which works (esp. in light of HDFS-1762)
was:
Running TestCLI in a real cluster environment I came across a problem where a
regexp like this
{{^-rw-r--r--( )*1( )*[a-z]*( )*supergroup( )*.*}}
doesn't match
{{-rw-r--r-- 1 testuser1 supergroup 0 2011-04-05 13:21
/tmp/testcli/file1}}
It turns out that {{[a-z]*}} doesn't match username {{testuser1}}
It'd be nice to have a regexp which works (esp. in light of HDFS-1762)
> TestCLI xml config should be able to recognize real user names which might
> include digits in the name
> -----------------------------------------------------------------------------------------------------
>
> Key: HDFS-1807
> URL: https://issues.apache.org/jira/browse/HDFS-1807
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Konstantin Boudnik
>
> Running TestCLI in a real cluster environment I came across a problem where a
> regexp like this
> {noformat}
> ^-rw-r--r--( )*1( )*[a-z]*( )*supergroup( )*.*
> {noformat}
> doesn't match
> {noformat}
> -rw-r--r-- 1 testuser1 supergroup 0 2011-04-05 13:21
> /tmp/testcli/file1
> {noformat}
> It turns out that {{[a-z]*}} doesn't match username {{testuser1}}
> It'd be nice to have a regexp which works (esp. in light of HDFS-1762)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
