[
https://issues.apache.org/jira/browse/BIGTOP-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay vyas updated BIGTOP-1221:
-----------------------------
Attachment: BIGTOP-1221-tested-refined-2.patch
Thanks cos. Responses inline + a new patch.
- mark mentioned maybe we should keep the HDFS test, so I opted to add this as
a new test rather than delete it. I will attach with deleted TestHDFS test.
- indentation: okay, ive given it another go. Looks like some of the stuff was
double indented.
- I'm using /bin/cp to avoid any issues with aliasing of cp. Since CP is an
error prone command (i.e. we know it can break hadoop FUSE), we want to be very
careful that we call it using exact "cp" program and not a common aliases (cp
is normally aliased with overwrite interactive prompt, which we certainly dont
want in a unit test).
- Fixed up the indents and formats some more. Looks better? I still dont
have a good groovy formatter. Right now im using eclipse's java one and it
seems to choke on the functional stuff.
> Expand and updated FUSE tests
> -----------------------------
>
> Key: BIGTOP-1221
> URL: https://issues.apache.org/jira/browse/BIGTOP-1221
> Project: Bigtop
> Issue Type: Bug
> Components: Tests
> Affects Versions: 0.7.0
> Reporter: jay vyas
> Assignee: jay vyas
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1221-cos-fixes.patch,
> BIGTOP-1221-tested-refined-2.patch, BIGTOP-1221.patch
>
>
> The BigTop TestFuseDFS need
> - tests for consistency after individual writes : consistency in FUSE mounts
> is important since there are often associated multitenant workloads. Writes
> should result in immediate recognition of a file.
> - Should use HCFS semantics (That way we can confidently use and maintain
> this for alternative file system implementations).
> - should use logging instead of System.out. That way all the logs can be
> picked up from the same place in case we change the logging framework.
> Logging in trace mode, in any case, will allow us to see everything that the
> ITest shell does, and so might as well use it for other logs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
