PR for #2380 and #1400.

The strings are kept for backward compatibility. The objects are stored redundantly in new fields with name (old_field_name)_object. The affected fields are listed below.

• maps are stored as [ { "key_(type)": k, "data_(type)": d } , ... ], where (type) can be int, bool, string or object. The fields are:
  • account_auths in account_object and related operations
  • address_auths in account_object and related operations
  • key_auths in account_object and related operations
  • feeds in asset_bitasset_data_object
  • acceptable_collateral in credit_offer_object and related operations
  • acceptable_borrowers in credit_offer_object and related operations
• static_variants are stored as { "which": w, "data_(type)" : d }, where (type) can be int, bool, string or object. The fields are:
  • op in proposal_create_operation.proposed_ops
  • initializer in worker_create_operation
  • policy in vesting_balance_create_operation and etc
  • active_special_authority in account_object and related operations
  • owner_special_authority in account_object and related operations
  • htlc_preimage_hash in htlc_create_operation
  • argument in restriction class, used in custom authority operations (added in Adapt restriction::argument as an object for ES #2681)
  • operation_result
• object arrays are stored normally as object arrays, especially, among them, static_variant arrays are stored as object arrays, including:
  • parameters in committee_update_chain_parameters_operation.**.current_fees
  • proposed_ops in proposal_create_operation
  • operations in proposal_object
  • predicates in assert_operation

Note: more disk space is required for ES to store the redundant data. Here is some data for comparison.

BTW #2568 is the next work to be done.