Uploaded image for project: 'Apache Avro'
  1. Apache Avro
  2. AVRO-3720

Handling of out of order field in resolvingDecoder

Add voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.11.1
    • None
    • c, c++
    • None

    Description

      There's a `FIXME` comment on avro::resolvingDecoder function in avro-cpp code base. Please see https://avro.apache.org/docs/1.11.1/api/cpp/html/namespaceavro.html#aeef8b583abe36b25a8d2094d7a3d4b96 

      Does this comment mean resolvingDecoder does not work when the fields are out of order in reader and writer schemas?

      We would also like to know if avro cpp supports full avro schema compatibility rules while resolving schema. These rules are mentioned on https://avro.apache.org/docs/1.11.1/specification/_print/#schema-resolution 

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            viv1k Vivek Kumar

            Dates

              Created:
              Updated:

              Slack

                Issue deployment