Should functional blob and bucket operations enforce metageneration match upon updates

This topic was also discussed in #171.

Currently the functional blob and bucket pin to their metadata and provide the user with the option of enforcing metadata version check in updates operation. However this check is not triggered by default.

An alternative to what we have now is to enforce the version check by default and to provide options to disable the check instead.

My preference is to keep the existing way (no enforcement by default but have an option to support such check).

I am +1 for not checking by default and adding an option.

@mziccard

@mziccard Just to make sure I understand your preference.
Is your preference to keep the existing way or are you suggesting to add a new option?

@aozarov

@aozarov I want to keep update as it is (no enforment by default). If we want we can add support for generation checks by allowing something like:

blob.update(newInfo, 
  UpdateOptions.generationMatch(), UpdateOptions.metagenerationMatch());

Ok, thanks for making it clear.

Isn't that already supported?

blob.update(newInfo,
    BlobTargetOption.generationMatch(), BlobTargetOptions.metagenerationMatch());

Yeah my bad :) Then it's ok how it is for me!

This has been open for a while. As I already said I believe that the way we do these checks now is ok and consistent with other uses of generationMatch() and metagenerationMatch() options. I am closing this. Feel free to reopen if you believe we should give this more thoughts.