[jira] [Commented] (BIGTOP-1317) Make variable names in Flume Test reflect the HCFS Compliance.

["jay vyas (JIRA)" <ji...@apache.org>]

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

jay vyas commented on BIGTOP-1317:
----------------------------------

Qiuck note while we are improving flume tests, is that  there is also a way to launch a flume agent from pure java rather than using properties files, this is probably more self contained and a better way to test the API, http://flume.apache.org/FlumeDeveloperGuide.html#embedded-agent.  


> Make variable names in Flume Test reflect the HCFS Compliance.
> --------------------------------------------------------------
>
>                 Key: BIGTOP-1317
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1317
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Tests
>            Reporter: jay vyas
>             Fix For: backlog
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> This is a pretty quick task we can do : The Flume tests appear to be HCFS Compliant, because they use a variable for the file system URI, but there are a bunch of variables (like nn, hdfs_sink, ...)  which at first glance make it look to be hard coded to hdfs. 
> Lets clean up the variable names, for example
> {noformat}
>   private static String hdfs_sink_dir = "${nn}/user/${System.properties['user.name']}/$tmp";
> {noformat}
> could be alot simpler:
> {noformat}
>   //will write, for example, to hdfs://user/bigtop-tester/tmp/
>   private static String hcfs_sink_dir = "${System.properties['user.name']}/$tmp";
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)