Uploaded image for project: 'Apache Ozone'
  1. Apache Ozone
  2. HDDS-3595

Add a maven proto file backward compatibility checker into Ozone.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.0.0
    • None

    Description

      The plugin proto-backwards-compat-maven-plugin flags incompatible protobuf changes.

      cc arp avijayan elek

      https://github.com/salesforce/proto-backwards-compat-maven-plugin
      and
      https://mvnrepository.com/artifact/com.salesforce.servicelibs/proto-backwards-compatibility

      To test, I modified the following code in proto

      
      diff --git a/hadoop-ozone/csi/src/main/proto/csi.proto b/hadoop-ozone/csi/src/main/proto/csi.proto
      index 3bd53a075..b8a984de2 100644
      --- a/hadoop-ozone/csi/src/main/proto/csi.proto
      +++ b/hadoop-ozone/csi/src/main/proto/csi.proto
      @@ -119,7 +119,7 @@ message GetPluginInfoResponse {
         // characters or less, beginning and ending with an alphanumeric
         // character ([a-z0-9A-Z]) with dashes (-), dots (.), and
         // alphanumerics between. This field is REQUIRED.
      -  string name = 1;
      +  string newName = 1;
      

      and this flagged the following change

      [ERROR] CONFLICT: "GetPluginInfoResponse" field: "name" has been removed, but is not reserved [csi.proto]
      [ERROR] CONFLICT: "GetPluginInfoResponse" field: "newName" ID: 1 has an updated name, previously "name" [csi.proto]
      

      Attachments

        Issue Links

          Activity

            People

              msingh Mukul Kumar Singh
              msingh Mukul Kumar Singh
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: