Missing private data reconciliation

[dexa187]

An edge case may exist where the peer that fabric-logger is connected to does not have the private data and only the hash. If this case occurs it would be desirable to mark the block or transaction to be further processed when the private data becomes available.

Something to keep in mind that when processing historical blocks the private data may no longer exist on any peers due to the collection policy blockToLive

[dexa187]

https://hyperledger-fabric.readthedocs.io/en/release-2.2/private-data-arch.html?highlight=collections
Considerations:

1. We getting historical blocks the private data may already be deleted due to block to live time.
2. The time for the peer to receive the data could be variable. This may need retries and timeouts.
3. The peer may never receive the private data. Is it possible to request from another peer through the sdk.
4. In the case of guaranteeing fabric logger delivery private data to splunk provide a recommendation to the user on how to connect to X number of specific peers.