Hi all, I have a question related to aspect versioning: • Let's say there's some failure somewhere which results in

version 2

of some metadata aspect being sent to datahub before

version 1

is sent (note, the versions here are some non-datahub internal versioning of dataset aspects) • As I understand it, the above will result in "version 1" becoming the newest version, which is not what we want • What are recommended solutions to handle the above? • E.g. would there be a way, using either the Python or Java emitters, to do some check on the

version 1

metadata before sending it and then either discarding it or sending it but setting it to a lower version?

This is a great question. We don't yet have a way to support this kind of conditional write.

Thank you!