Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-3519 Finalize network and storage protocol of Ozone
  3. HDDS-3621

Separate client/server/admin proto files of HDDS to separated subprojects

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.0.0
    • None

    Description

      As described in the parent Jira admin/client/server protocols need different compatibility guarantees. It's better to separate them to separated maven project to make it easy to follow the changes.

      I propose to create 3 new projects

      hadoop-hdds/interface-client
      hadoop-hdds/interface-server
      hadoop-hdds/interface-admin

      I called it -interface instead of -proto because we can include some basic Java classes not just proto files (for example utilities to serialize/deserialize proto files)

      This first patch will include only the move without refactoring any RPC. While the new proto file names represent the proposed naming convention (Datanode/Scm + Server/Client/Admin + additional postfix) the name of the generated classes and the name of the RPC interfaces (Client/Server translator) not yet renamed to make the patch small.

      Also: some methods should be moved between admin/server but it can be done in separated issue to make it easier to follow the change.

      Attachments

        Issue Links

          Activity

            People

              elek Marton Elek
              elek Marton Elek
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: