-
Notifications
You must be signed in to change notification settings - Fork 72
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
docs: How to get specific fields when listing files. #42
Comments
it is actively maintained, at least as long as `iterative/dvc is alive and maintained.
I assume you already found the file listing API - https://pythonhosted.org/PyDrive/filelist.html#file-listing-made-easy right? Then it already has a small example how to get |
Yes, I can see how get the attributes after the download. But how do you select to only download the attributes you need. Which will reduce data and time needed. |
Have you tried to pass |
Yes I did but got an ApiRequestError.
|
Try this: |
Thank you, I see now that you are still using the v2 version. Although this is not clear on the home page. |
Yes, but I think the syntax for fields is the same across v2 and v3 - check these examples https://developers.google.com/drive/api/v3/fields-parameter |
Ah oke, I was looking at this one: https://developers.google.com/drive/api/v3/search-files |
@Cing2 sure. I keep it open with the |
Hi, As v3 has been out for many years, it is natural for people to develop using the v3 documentation as reference (my case). I couldn't figure out why I could download specific fields only with the API and not with PyDrive2, and the only explanation I could find is this issue. Can PyDrive2 be updated to use the v3 fields? |
Hey,
How is it going with this project? I am planning to use this for my own project and was trying some things. However I could not find how to get certain fields of a file, like id, name, parents. etc..
The documentation also isn't clear this one.
I am willing to help with the project, to get it more usable. Love to hear from you.
Regards,
The text was updated successfully, but these errors were encountered: