Using Java Files API for Google Cloud Storage results in corrupt files

[Tim Rob]

Hi,

We are currently using the Java Files API to store generated files in Google Cloud Storage. When we try to store 'larger' (1 to 15MB) generated reports (CSV and Excel) or backups of a namespace in the Datastore (stored as JSON text) we always end up with corrupt files. For example when writing something like 'ABCDEFG', we end up with 'ABCDEAB'.

When we switch to Blobstore this all works fine again. I know the Java Files API to Google Cloud Storage is 'experimental', but I was hoping this functionality would work. Is this maybe a known issue?

PS: The main reason to prefer GCS over Blobstore is the lack of support for namespaces in Blobstore. With GCS we can create a bucket per namespace.

Thanks

[Christina Ilvento]

Hi Tim,

We've diagnosed the issue on our side and should have a fix pushed out soon. Thanks for reporting this.

Thanks,

Christina

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/aOnH13zhIKUJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--

Christina Ilvento | Google App Engine | cilv...@google.com | (650)-201-9399

[Tim Rob]

Great, thanks Christina

[Tim Rob]

Thanks Mike, I just checked and it's working fine now - our files no longer contain corrupt data.

I was actually thinking of switching back to Blobstore again, but I guess we should expect the GCS interface to be stable as well?

On Saturday, September 22, 2012 2:57:08 AM UTC+2, Mike Aizatsky wrote:

The fix is live. We'll have more details about what has happened soon.

Can you confirm that it is now working as expected on your end?