Provide support to fetch GDataFeed by `orderBy=modifiedDate` to avoid issues with volatile entries in Google Backend
The !58 (merged) MR augments the move and copy operation in the Google backend to use volatile entries to perform these operations.
When performing a copy/move operation from a folder into another folder where there already exists some file with same title or volatile entry, we need to fetch the updated GDataFeed such that it is ordered by modifiedDate
. The file which has been copied/moved latest will always have the most recent modifiedDate
and that file will be inserted into the cache at the last, thereby ensuring consistency. By consistency, I mean that a query_info
operation called using title/volatile_entry just after move/copy will get resolved with the file that is actually moved/copied and not the other one with the same title/volatile_entry.
Depends upon: