Allow synchronous Metadata mutations via Metadata storage request option
Description
Recent UI bugs related to metadata not populating when updated are due to asynchronous behavior of mutations to Elasticsearch when modifying CDAP Metadata (either via delay in storage or delayed failure caused by late OCC validation). To alleviate this, plan is to
Add MutationOptions parameter (currently with single sync/async field) to MetadataStorage interface/classes.
Use the option to determine whether Elastic's refresh policy should be IMMEDIATE or WAIT_UNTIL.
Set option as sync in MetadataStorage calls from the HTTP Handlers.
Recent UI bugs related to metadata not populating when updated are due to asynchronous behavior of mutations to Elasticsearch when modifying CDAP Metadata (either via delay in storage or delayed failure caused by late OCC validation). To alleviate this, plan is to
Add MutationOptions parameter (currently with single sync/async field) to MetadataStorage interface/classes.
Use the option to determine whether Elastic's refresh policy should be IMMEDIATE or WAIT_UNTIL.
Set option as sync in MetadataStorage calls from the HTTP Handlers.