Synchronization allows objects with incomplete system metadata to proceed into system
During testing of the urn:node:mnTestSEAD MN, two objects (sead-Martin-John-f1dbc3df-c27c-4647-b05a-4b1f05c99a24 and seadva-ZhouQuan388469d5-33bb-491c-867b-c515ff715594) were only partially synchronized (see attached files) on cn-stage when the system metadata for each object was found to be missing the "dateUploaded" field. Each object and corresponding system metadata are available through the REST API (it is hypothesized that the system metadata only resides in the memory part of the Hazelcast Map) and the object was written to Metacat storage; however, the object's system metadata failed to be stored by Metacat due to an Null Pointer Exception resulting from the missing field.
This issue manifest when these objects failed to be indexed by Solr because of an "Object path not available error" in the Solr index processor process.
cn-index-processor-daemon.log:[ INFO] 2015-05-26 17:53:50,051 (IndexTaskProcessor:isObjectPathReady:263) Object path for pid: sead-Martin-John-f1dbc3df-c27c-4647-b05a-4b1f05c99a24 is not available. Task will be retried.
cn-index-processor-daemon.log:[ INFO] 2015-05-26 17:53:50,060 (IndexTaskProcessor:getNextIndexTask:164) Task for pid: sead-Martin-John-f1dbc3df-c27c-4647-b05a-4b1f05c99a24 not processed.
The synchronization processor should test for complete system metadata and fail fast if it is incomplete.