search

Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.47k stars 4.8k forks source link

[BUG] Issue with Date Range Filtering in FindBlobsByTagsAsync in Azure Blob Storage #40135

Open eramireziceibm opened 11 months ago

eramireziceibm commented 11 months ago

Library name and version

Azure.Storage.Blobs:12.13.1

Describe the bug

Encountering an issue with date range filtering in both FindBlobsByTagsAsync in Azure Blob Storage and Microsoft Azure Storage Explorer. This issue arises even when using the example provided in the Azure Docs (https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/storage/blobs/storage-blob-tags.md). While individual date filter queries work correctly, combining them for a date range returns no results, despite the presence of blobs meeting the criteria.

Expected behavior

Both the SDK query and Azure Storage Explorer should return all blobs with TAG_CREATION_DATE within the specified range.

Actual behavior

No blobs are returned in either the SDK or Azure Storage Explorer, despite meeting the filter conditions.

Reproduction Steps

  1. Tag blobs in Azure Blob Storage with a TAG_CREATION_DATE tag.
  2. Execute a query in FindBlobsByTagsAsync with the filter "TAG_CREATION_DATE >= '21-08-2023 18:08:53' AND TAG_CREATION_DATE <= '21-11-2023 18:08:53'".
  3. Perform the same query in Microsoft Azure Storage Explorer.
  4. Both methods return no results, despite the presence of blobs within the specified date range.

Environment

Environment

Has anyone else experienced this issue in both FindBlobsByTagsAsync and Azure Storage Explorer, or does anyone have insights into what might be causing this behavior?

### Tasks
github-actions[bot] commented 11 months ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.