Google Drive API方法Drive.File.update无法更新文件内容 [英] Google Drive API method Drive.File.update Can Silently Fail to Update File Content

查看:263
本文介绍了Google Drive API方法Drive.File.update无法更新文件内容的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

使用Java Google Drive API v2r109lv1.16.0-rc,我们发现偶尔使用Drive.Files.update方法无法正确更新文件。这似乎是自2014年4月22日以来偶尔发生的客户。在此之前它工作得很好。



我们正在用新内容和元数据更新文件。元数据更新正常但文件内容未被触摸。没有任何错误,只要操作成功就没有问题。



只有当用户访问文件时才会看到问题我们。例如,如果所需的文件内容更新大于先前的内容,则元信息(文件大小)将不正确,读取将失败。



我们真的很挣扎创建一个复制场景。是否有其他人遇到过这个问题,或者知道一个修补程序,或者Google是否发现了一个潜在的问题(希望)被修复? 解决方案

我不相信这个问题是可靠的固定的。

我真的很想从谷歌的一些清晰。这是一个非常糟糕的问题。数据似乎正在丢失,文件元数据和实际数据流不同步。

Using Java Google Drive API v2r109lv1.16.0-rc we have found that occasionally files are not updated correctly using the Drive.Files.update method. This seems to have occurred among customers sporadically since 22nd April 2014. Before then it was working just fine.

We are updating the file with new content and meta data. The meta data updates OK but the file content is not touched. There are no errors and as far as can be told the operation succeeds without an issue.

It is only when a user goes to access the file that a problem is seen by us. If for example the desired file content update is greater than the previous content then the meta information (file size) will be incorrect and the read will fail.

We are really struggling to create a reproduction scenario. Has anyone else experienced this problem, or know of a fix, or if Google has found an underlying problem that is (hopefully) fixed?

解决方案

I am not convinced this issue is reliably fixed.

I would really like some clarity from google. This is a very bad problem. Data appears to be being lost, and file meta data and the actual data stream are out of sync.

这篇关于Google Drive API方法Drive.File.update无法更新文件内容的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆