Issue 800661 link

Starred by 2 users

Issue metadata

Status:	Available
Owner:	----
Cc:	fukino@chromium.org yamaguchi@chromium.org
Components:	Platform>Apps>FileManager
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	3
Type:	Bug
CrOSFilesFeature-CloudImport

Store the cloud import metadata locally

Project Member Reported by satorux@chromium.org, Jan 10 2018

Issue description

Cloud import feature in Files app uses chrome.syncFileSystem to store some metadata in the cloud. Seems to me that it'd be simpler to store the data locally which would reduce complexity around syncing, and a small amount of network traffic.

Comment 1 by yamaguchi@chromium.org, Jan 16 2018

I think there's a trade-off.
From the design document of cloud import:
> The index will be stored in the chrome.storage.sync storage area. This ensures that the deduplication index will be available across all of a user's devices.
The "deduplication" here means the quick and rough check by the hash of file metadata.

If file duplication was not detected here, the files are once treated as not yet backed up and user will be prompted to back up. Though, it would not actually transmit files after calculating content hash of local files to know those already exist in cloud storage -- which may take some local disk access and CPU time.