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
Cannot locate the azure data lake file when tried to open the adl url in browser #950
Comments
@jian1981 , Thanks for your feedback. And located to the related folder required:
|
Thanks for reply. The version I am using is 1.6.0. Repro: I can confirm all subscriptions are selected before I try to locale that file. By the way, the folder we are trying to access contains large number of subfolders (40000), is it the possible reason? Thanks again |
In addition, the search in the explorer also doesn't work. It seems it only can search the cached files/folders. Because in my case there are large number of folders, I cannot get the folder/file I need when I tried to use the search. |
Yes, it is. We have two dl account under the same subscription. By the way, the search feature in the Explorer for the data lake seems only search the cached files. Please do the fix as well for this. Thanks a lot. |
Thanks @jian1981. For the search feature, I will create a new issue to track it. |
Yes, we need to click "load more" to load the second account we need. Thanks. |
Thanks @jian1981 . Then it will be the same root cause with my reproduced steps. I'm working on the fix. |
Have created #988 to track the search not work bug. |
Storage Explorer Version: In which Storage Explorer version was the bug encountered?
Platform/OS: Linux? macOS? Windows?
Architecture:
Regression From: Was this working in a previous version? If so, which one?
Bug description
A clear and concise description of what the bug is.
When I tried to open a azure data lake resource link (e.g. adl://myaccount.azuredatalakestore.net/abc/def/2018/12/4/89dfe0d4c9464239accd5bf40056b343.zip) in browser, the explorer cannot locate the related folder. It was working previously.
Steps to Reproduce
List the minimal steps clearly and concisely to reproduce the behavior:
Expected Experience
A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain what you expected.
Actual Experience
A clear and concise description of what actually happens. If applicable, add screenshots to help explain what actually happened.
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: