Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQ] Add ListBlobsShowOnly value of directories to DataLake #31894

Open
paulbrittain opened this issue Dec 16, 2024 · 1 comment
Open
Assignees
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. data-plane feature-request This issue requires a new behavior in the product in order be resolved. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@paulbrittain
Copy link

paulbrittain commented Dec 16, 2024

API Spec link

https://github.com/Azure/azure-rest-api-specs/tree/main/specification/storage/data-plane/Azure.Storage.Files.DataLake

API Spec version

2025-05-05

Please describe the feature.

Hi folks, @seanmcc-msft (tagging you here as I see you're actively involved in the datalake spec development :) )

I'm working on adding a feature request to azure-sdk-for-go that adds a NewListDirectoryPathsPager which is needed to return directories in a hierarchical namespaced File System in a reasonably fast and scalable operation. The pager makes use of the showonly request argument of the ListBlobs REST API seen here. The possible values are an enum that include: {deleted,files,directories}.

The azure-sdk-for-go currently supports listing deleted files through use of the showonly enum parameter, so it's a matter of extending the azure-sdk-for-go datalake package to use the other available value for directories. At present, the REST api spec for the DataLake FileSystem_ListBlobHierarchySegment function accepts deleted. I'd like to extend this to include directories so that the azure-sdk-for-go can generate the code it needs for the feature request linked above.

I am willing to add the new spec that includes this change, but would need a little guidance on what new version to use as I don't have the information available to me on how they're versioned (given the versions are not the date of the change, but future dates).

Can we make this change to unblock the azure-sdk-for-go feature?

@paulbrittain paulbrittain added the feature-request This issue requires a new behavior in the product in order be resolved. label Dec 16, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Dec 16, 2024
@tanyasethi-msft
Copy link
Member

@paulbrittain - Using transforms to update API spec in azure sdk for go - Azure/azure-sdk-for-go#23801

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. data-plane feature-request This issue requires a new behavior in the product in order be resolved. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

4 participants