Bug Description
The same processor can be deployed many times. Execution nodes check if a processor with proc_id is already deployed. However, proc_id is based on the object id. DOR produces unique object ids based on hashes that include a timestamp. This means that object ids are not suitable to for duplicate checks. Instead the content hash c_hash should be used.
Steps To Reproduce
Simply deploy the same processor by uploading the same GPP multiple times.
Expected behaviour
Despite having multiple GPP data objects, the processor should only be deployed once since they all point at the same processor.
Actual behaviour
Execution nodes deploy multiple instances of the same processor.
Bug Description The same processor can be deployed many times. Execution nodes check if a processor with
proc_idis already deployed. However,proc_idis based on the object id. DOR produces unique object ids based on hashes that include a timestamp. This means that object ids are not suitable to for duplicate checks. Instead the content hashc_hashshould be used.Steps To Reproduce Simply deploy the same processor by uploading the same GPP multiple times.
Expected behaviour Despite having multiple GPP data objects, the processor should only be deployed once since they all point at the same processor.
Actual behaviour Execution nodes deploy multiple instances of the same processor.