Details
-
Type:
Sub-task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: fs
-
Labels:None
Description
We should have an automated test for checking that programs written against an old version of the FileSystem API still run with a newer version.
Issue Links
- relates to
-
MAPREDUCE-1637
Create a test for API compatibility between releases
-
- Open
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to MAPREDUCE-1637 [ MAPREDUCE-1637 ] |
I totally agree, but we need to start somewhere. My hope is to have some basic sanity checks for compatibility which we can release 0.21 with. Over time I would hope that the API tests are built out to cover more of the codebase.
I'm going to test this and MAPREDUCE-1637 by compiling and running a few simple programs (e.g. word count) against both 0.20.2 and 0.21.0. This will also get more testing as folks try out their programs against the 0.21.0 release candidates and the release.
This seems to be a very reasonable and sorta cheap approach of testing backward compatibility. The only thing needs to be kept in mind that set of test applications needs to be consistent from release to release. Otherwise, such verification won't be representative enough. But I guess word count doesn't go nowhere 
| Fix Version/s | 0.21.0 [ 12313563 ] |
This would certainly be nice to have and can be considered a prerequisite for the fabled 1.0, but should it be listed as a blocker? I'd like to move this down to major and keep it in the hopper for 1.0 work.
| Priority | Blocker [ 1 ] | Major [ 3 ] |
I believe the effort needs to go beyond FileSystem API.