Google Drive API v2 vs v3

Feature
1

Can we have a flag to set which API we want to use? The migration to v3 broke or crippled rclone for my use.

First, the max download speed via v3 API is 20-30MB/s (I can pull 100MB/s via v2).

Second, since rclone now uses v3 of the API, files that are flagged as being a virus can not be downloaded. https://github.com/ncw/rclone/issues/2317 This is not an issue when using the v2 API.

These changes have broken rclone for my applications and made it unusable/slow.

Also why did we migrate to v3 of the API? v2 is vastly better.

Edit: Just seen https://github.com/ncw/rclone/issues/2317#issuecomment-395791378 Now if it works, having a way to strictly use v2 API would be excellent :wink:

2

There a a small number of things you can’t do in the v2 API like this one for instance: https://github.com/ncw/rclone/issues/1525

However having a v3 API is a strong signal to developers that v2 will be deprecated (or won’t get new features) at some point and that is the real reason for the change. My (possibly faulty memory) tells me team drives were only available on the v3 API but google relented and put them in the v2 API too.

Did that get reported to google? Here is the place to search: https://issuetracker.google.com/

Google do fix stuff eventually!

@B4dM4n did a work-around to use just the v2 API for download which we could merge (under a flag most likely).

Unfortunately it isn’t a simple matter switching between the v2 and v3 API - they are quite different :frowning:

Just waiting for a few more test resuts to come in for https://github.com/ncw/rclone/issues/2317 and then I’ll merge it. This will give a work-around for downloading blocked files.

1 Like