Add NativeBlobSoftDeleteDeletionDetectionPolicy to Microsoft.Azure.Search library

[xantari]

Library or service name.

Microsoft.Auzre.Search

Is your feature request related to a problem? Please describe.

It appears that since the 09/2019 release you have had a public preview of "NativeBlobSoftDeleteDeletionDetectionPolicy" delete policy.

However the Microsoft.Azure.Search does not have an ability to define that deletion policy.

Information about Native blob soft delete is here: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-blob-storage

[AlexGhiondea]

/cc @tg-msft for our Track 2 library.

@xantari we have started work on a new version of the Search library -- we are going to consider including this for our upcoming library.

[tg-msft]

/cc @heaths as this would be on our data source APIs

[heaths]

Thanks for bringing this to my attention. The new packages do support it, but perhaps not in a very intuitive way. @brjohnstmsft, right now these are exposed as models that just need to exist in the JSON payload. I suggest we make them boolean properties like Data(Change|Deletion)DetectionPolicyEnabled. Perhaps we could drop "Policy" to shorten it, but I do like the symmetry with the documentation, such that searching for "DataDeletionDetectionPolicy", for example, yields a match.

[heaths]

Sorry, I see those classes should actually be abstract (see #9686) and I see that swagger does not actually define @odata.type "#Microsoft.Azure.Search.NativeBlobSoftDeleteDeletionDetectionPolicy". We can define one manually, but this should be in the Preview swagger as well if it's still supported.

[brjohnstmsft]

@heaths I defer to @bleroy or @arv100kri for API design opinions in this area.

[heaths]

Blocked on Azure/azure-rest-api-specs#9160. This could be done without but requires taking over de/serialization completely instead of using generated code, which continues to evolve. At least, we can wait until time no longer allows for getting a change to swagger.