[
https://issues.apache.org/jira/browse/BIGTOP-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355509#comment-14355509
]
jay vyas edited comment on BIGTOP-1748 at 3/10/15 7:20 PM:
-----------------------------------------------------------
Hi dasha. im not sure why this happened but just for some context, martin
works on HCFS stuff, trying to make sure in general that tests arent specific
to HDFS.
Is there any reason why HDFS trash enablement would break ability to run the
general HCFS tests? Possibly, since "trash" is not an offical part of the
HCFS specifications (i.e.
https://issues.apache.org/jira/secure/attachment/12572328/HadoopFilesystemContract.pdf
)...
was (Author: jayunit100):
Hi dasha. im not sure why this happened but just for some context, martin
works on HCFS stuff, trying to make sure in general that tests arent specific
to HDFS.
Is there any reason why HDFS trash enablement would break HCFS tests? If so
that might be a hint. Just thinking out loud... :) i'll dig some to see as
well.....
> Remove assert on fs.trash.interval from TestCLI and TestDFSCLI
> --------------------------------------------------------------
>
> Key: BIGTOP-1748
> URL: https://issues.apache.org/jira/browse/BIGTOP-1748
> Project: Bigtop
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Dasha Boudnik
> Assignee: Dasha Boudnik
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1748.patch
>
>
> Currently, the following assert causes these CLI tests (and TestHDFSCLI,
> which extends TestCLI) to fail on clusters where this configuration is set
> otherwise:
> {noformat}Assert.assertEquals("HDFS trash should be disabled via
> fs.trash.interval",
> 0, conf.getInt("fs.trash.interval", 0));{noformat}
> I believe this isn't necessary for these tests, so let's remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
