Google Drive Support

[Xuanwo]

Some notes about google drive API:

OpenDAL requires a path-based API, but google drive located files via its internal id. So we need to maintain:

• a convert util function that converts a given path to id.
• maintain an internal cache for the path -> id mapping, so we don't need to send requests every time.

API references: https://developers.google.com/drive/api/v3/reference

[Xuanwo]

Cc @theshashankpal, I wrote some notes for you. Feel free to ask any questions here~

[Xuanwo]

Hi, @theshashankpal, are there any updates? What help can I give?

[imWildCat]

I may take a look at either Dropbox/GDrive/OneDrive after finishing the list op of web dav.

I will choose the easiest one of these three first. Still learn Rust/OpenDAL in progress.

[Xuanwo]

I think Dropbox should be an easier entry point.

[Young-Flash]

I will choose the easiest one of these three first. Still learn Rust/OpenDAL in progress.

hi, I also interested in this, which one would you chose? I may take another one to work on.

[imWildCat]

@Young-Flash I'd like DropBox / OneDrive first

[Young-Flash]

I'd like to work on google drive support for opendal and I have make some investigation, the basic idea here is to use google-drive3 dependency, which support google drive api v3 and under well maintenance. what do you think ? @Xuanwo

[Xuanwo]

the basic idea here is to use google-drive3 dependency, which support google drive api v3 and under well maintenance

Sorry, I have to say NO to this idea. OpenDAL prefers to maintain all HTTP based services ourselves.

Reasons:

• OpenDAL only needs a subset of APIs like read/write/delete/... which are easy to implement.
• OpenDAL provides well maintained HTTP infrastructure that is production ready and tested.
• Avoid introducing new deps to reduce the extra maintenance work around licences, version bump, ...
• And believe me, talking directly to the HTTP API is a lot easier and more fun than playing with the SDK 🤣

[Young-Flash]

I see. and what about the path -> id cache? use other dep (like lru-cache) or do it ourselves (maybe a simple HashMap) ?

BTW, google drive access need oauth authorization, seems no easy to deal with it without extra deps.

[Xuanwo]

use other dep (like lru-cache) or do it ourselves (maybe a simple HashMap) ?

Let's get started with a simple hashmap.

BTW, google drive access need oauth authorization, seems no easy to deal with it without extra deps.

Should be handled by reqsign. We can start with just accept a token file path.

[Young-Flash]

I will take a look, but I may not get the work done soon cause I am struggling with my degree paper 😅

[imWildCat]

@Young-Flash how's it going with your implementation? If not, I would pick this up in a few weeks.

[Young-Flash]

I just submitted my degree thesis. I will work on this these days.

[imWildCat]

@Young-Flash Thank you!

I will go for Dropbox first after OneDrive.

[Xuanwo]

Basic support for gdrive has been added.

[imWildCat]

@Young-Flash would you like to implement the list operation of Google Drive? If not, I can take it.

[Young-Flash]

@Young-Flash would you like to implement the list operation of Google Drive? If not, I can take it.

go ahead 😄