Hadoop Common
  1. Hadoop Common
  2. HADOOP-5064 Hadoop 1.0
  3. HADOOP-6733

Create a test for FileSystem API compatibility between releases

    Details

    • Type: Sub-task Sub-task
    • Status: Open
    • Priority: Major 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

          Activity

          Hide
          Tom White added a comment -

          Agreed. Downgrading to major.

          Show
          Tom White added a comment - Agreed. Downgrading to major.
          Hide
          Jakob Homan added a comment -

          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.

          Show
          Jakob Homan added a comment - 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.
          Hide
          Konstantin Boudnik added a comment -

          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

          Show
          Konstantin Boudnik added a comment - 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
          Hide
          Tom White added a comment -

          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.

          Show
          Tom White added a comment - 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.
          Hide
          Tom White added a comment -

          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.

          Show
          Tom White added a comment - 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.
          Hide
          Konstantin Boudnik added a comment -

          I believe the effort needs to go beyond FileSystem API.

          Show
          Konstantin Boudnik added a comment - I believe the effort needs to go beyond FileSystem API.

            People

            • Assignee:
              Unassigned
              Reporter:
              Tom White
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:

                Development