[ https://issues.apache.org/jira/browse/HDFS-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547296#comment-13547296 ]
Hadoop QA commented on HDFS-3272: --------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12563796/HDFS-3272.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2 warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/3798//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3798//console This message is automatically generated. > Make it possible to state MIME type for a webhdfs OPEN operation's result > ------------------------------------------------------------------------- > > Key: HDFS-3272 > URL: https://issues.apache.org/jira/browse/HDFS-3272 > Project: Hadoop HDFS > Issue Type: Improvement > Components: webhdfs > Affects Versions: 1.0.1, 2.0.2-alpha > Reporter: Steve Loughran > Priority: Minor > Attachments: HDFS-3272.patch > > > when you do a GET from the browser with webhdfs, you get the file, but it > comes over as a binary as the browser doesn't know what type it is. Having a > mime mapping table and such like would be one solution, but another is simply > to add a {{mime}} query parameter that would provide a string to be reflected > back to the caller as the Content-Type header in the HTTP response. > e.g. > {code} > http://ranier:50070/webhdfs/v1/results/Debounce/part-r-00000.csv?op=open&mime=text/csv > > {code} > would generate a 307 redirect to the datanode, with the > {code} > http://dn1:50075/webhdfs/v1/results/Debounce/part-r-00000.csv?op=open&mime=text/csv > > {code} > which would then generate the result > {code} > 200 OK > Content-Type:text/csv > GATE4,eb8bd736445f415e18886ba037f84829,55000,2007-01-14,14:01:54, > GATE4,ec58edcce1049fa665446dc1fa690638,8030803000,2007-01-14,13:52:31, > ... > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira