[THRIFT-3359] Binary field incompatibilities

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.3
• Fix Version/s: 0.10.0
• Component/s: C# - Library, C++ - Library, Java - Library, JavaScript - Library, Node.js - Library, Python - Library
• Assignee: Nobuaki Sukegawa
• Reporter: Nobuaki Sukegawa
• Created: 27/Sep/15 14:28
• Updated: 06/Jan/16 02:06
• Resolved: 13/Dec/15 16:14

Description

Binary fields in TJSONProtocols of many languages are incompatible to each other.
Also, those in all protocols of NodeJS cannot reliably talk to other languages.

Issue Links

• breaks: THRIFT-3483 Incorrect empty binary handling introduced by THRIFT-3359
• contains: THRIFT-3200 JS and nodejs do not encode JSON protocol binary fields as base64
• contains: THRIFT-3276 Binary data does not decode correctly using the TJSONProtocol when the base64 encoded data is padded.
• contains: THRIFT-3350 Python JSON protocol does not encode binary as Base64
• relates to: THRIFT-3276 Binary data does not decode correctly using the TJSONProtocol when the base64 encoded data is padded.

Sub-Tasks

• Fix ruby binary field encoding in TJSONProtocol: Closed
• NodeJS binary field issues: Closed
• Haskell JSON protocol does not encode binary field as Base64: Closed