amazon s3

Lee Butts's picture

Grails Amazon S3 0.7.4 Released

A new version of the S3 plugin is now available. This was primarily a Hibernate mapping update to improve performance after excessive querying was noticed in a client application using the old version. As such, there are some database schema changes to required when you upgrade your application.

Release Notes

  • Versioning has been removed from S3Asset, as such you should drop the version column from the s3asset table
  • Versoning was added to the S3Asset options collection. You will need to add a version column (bigint) with a default of zero to s3asset_options
  • A foreign key on the options column and index on options_idx have been added to the s3asset_options table. This should increase performance for applications with a large number of assets.
    You may need to remove old rows from s3asset_options that do not reference a valid S3Asset due to the previous mapping not properly cascading deletes in some cases
  • Hibernate second level caching is now enabled for S3Asset and it's options. If you are not using second level caching (you'll get an error if you're not), you can disable this by setting aws.disableHibernateCaching to true in Config.groovy
Lee Butts's picture

Grails Amazon S3 Plugin 0.6.5 Released

A new version of the Amazon S3 plugin is now available.

The new release contains changes to help the plugin play nicely in a clustered environment:

  • Quartz jobs are now non-volatile and durable to stop them being deleted/recreated when a node is stopped/started
  • S3Asset now contains a hostName property (and hence a new column that you will need to add to the DB) which holds the host name of the server that created the row. This allows the plugin job to only try and upload assets where the local file exists on the server that it is running on.
Lee Butts's picture

Grails Amazon S3 Plugin 0.6 Released

Version 0.6 of the Grails Amazon S3 plugin has been released. This version adds further configuration options to the plugin as well as making better use of jets3t's multi threaded API methods to improve upload/delete performance (the number of concurrent threads is controlled by jets3t configuration - see http://jets3t.s3.amazonaws.com/index.html for details).

See http://grails.org/plugin/amazon-s3 for the latest documentation.

Syndicate content