Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-1975

TBinaryProtocol CheckLength can't be used for a client

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.9.1
    • Java - Library
    • None

    Description

      If you look at CASSANDRA-5529 you can see the Hadoop format will throw an exception because the limit is set for the protocol but it's used for many calls since it's called from a thrift client.

      We need a way to reset the call at the end of each rpc.

      Attachments

        Issue Links

        duplicates

        Bug - A problem which impairs or prevents the functions of the product. THRIFT-820 The readLength attribute of TBinaryProtocol is used as an instance variable and is decremented on each call of checkReadLength

        • Major - Major loss of function.
        • Closed

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

          People

            Unassigned Unassigned
            tjake T Jake Luciani
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment