Contact Free trial Login

Object Store v2 Release Notes

Support Category: Select

Object Store v2 enables applications and users to share data and share states across batch processes, Mule components, and multiple distributed applications. Object Store v2 works with Mule runtime engine version 3.8.5 and later, and all 4.x versions.

2.5.26 (Mule 4.3.0, 4.2.2, and 4.2.1)

September 21, 2020

Updated Feature

  • If the entryTtl value is greater than 30 days, TTL is set to the maximum value (2592000 seconds/30 days) without returning an error.

2.5.25 (Mule 4.3.0, 4.2.2, and 4.2.1)

September 15, 2020

This release provides fixed issues.

Fixed Issues

The following fixed issues apply to apps running on Mule versions 4.3.0, 4.2.2, and 4.2.1 with the September 8, 2020 CloudHub Runtime patch update. For information about this patch update, see September 8, 2020.

  • Fixed an issue in which, when entryTtl was set, and a read request performed in the original TTL window, the TTL was extended indefinitely, rather than for 30 days.

  • Fixed an issue that occurred when entryTtl was set to 0 or -1, which caused the entry to be evicted immediately rather than being set to the maximum TTL (30 days).

  • Fixed an issue in which you could set entryTtl to a value greater than the maximum TTL (30 days).

2.5.24 (Mule 4.3.0, 4.2.2, and 4.2.1)

September 8, 2020

The Cloud Object Store now works with apps running on Mule versions 4.3.0, 4.2.2, and 4.2.1 with the September 8, 2020 CloudHub Runtime patch update. For information about this patch update, see September 8, 2020.

Known Issues

This release contains the following known issues:

  • When you set entryTtl and perform a read request in the original TTL window, the TTL is extended indefinitely, rather than for 30 days.

  • When entryTtl is set to 0 or -1, Object Store evicts the entry immediately rather than setting TTL to the maximum TTL (30 days).

  • You can set entryTtl to a value greater than the maximum TTL (30 days).

2.5.23 (Mule 4.3.0 and 4.2.2)

August 4, 2020

This release provides new features and fixed issues for apps running on Mule versions 4.3.0 and 4.2.2 with the August 4, 2020 CloudHub Runtime patch update. For information about this patch update, see August 4, 2020.

New Features

This release contains the following new features:

  • Added support for dirty-read TTL updates for apps using Mule version 4.2.1 and later. (MQ-1591)

    Object stores in a Mule app that are defined without configuring an entry TTL now have a rolling TTL, specifying when to evict the key-value pairs from the store. If the data is accessed at least once a week, the TTL is extended for 30 days. Otherwise, it is evicted in the next 7 to 30 days from the last expiration date.

    This feature is available for both new and existing apps using Mule versions later than 4.2.1. For apps using Mule versions earlier than 4.2.1, if entryTtl is not specified, the TTL is set to 30 days.

Fixed Issues

This release contains the following fixed issues:

  • Fixed an issue in which Object Store v2 did not honor the TTL (time to live) configured in the Mule app Cache scope. (MQ-1423)

    Object stores created in Mule apps now honor the TTL definition for the entries. This change affects all apps that declare an object store with a custom TTL explicitly in the app XML.

    To enable this behavior, redeploy the applications using Mule version 4.2.1 or later.

    Existing data is not updated with the custom TTL. The key-value pairs continue to have a TTL of 30 days.

2.5.0 (Mule 4.2.1)

July 13, 2020

This release provides new features and fixed issues for apps running on Mule 4.2.1 with the July 13, 2020 CloudHub Runtime patch update. For information about this patch update, see July 13, 2020.

New Features

This release contains the following new features:

  • Added support for dirty-read TTL updates for apps using Mule version 4.2.1 and later. (MQ-1591)

    Object stores in a Mule app that are defined without configuring an entry TTL now have a rolling TTL, specifying when to evict the key-value pairs from the store. If the data is accessed at least once a week, the TTL is extended for 30 days. Otherwise, it is evicted in the next 7 to 30 days from the last expiration date.

    This feature is available for both new and existing apps using Mule versions later than 4.2.1. For apps using Mule versions earlier than 4.2.1, if entryTtl is not specified, the TTL is set to 30 days.

Fixed Issues

This release contains the following fixed issues:

  • Fixed an issue in which Object Store v2 did not honor the TTL (time to live) configured in the Mule app Cache scope. (MQ-1423)

    Object stores created in Mule apps now honor the TTL definition for the entries. This change affects all apps that declare an object store with a custom TTL explicitly in the app XML.

    To enable this behavior, redeploy the applications using Mule version 4.2.1 or later.

    Existing data is not updated with the custom TTL. The key-value pairs continue to have a TTL of 30 days.

2.4.9

September 21, 2019

This release provides bug fixes.

Fixed Issues

  • Fixed errors when retrieving data from an endpoint. (SE-13058)

2.4.8

April 18, 2019

Minor improvements to Object Store performance.

2.4.7

February 7, 2019

This release provides bug fixes.

Fixed Issues

  • Fixed an incorrect API response which was returned when checking if an object store partition existed.

2.4.6

July 12, 2018

This release provides improved connection handling for REST API clients.

Fixed Issues

  • Implement exponential backoff in OSv2 client. (MQ-1209)

2.4.2

June 8, 2018

This release makes Object Store v2 available to everyone.

Fixed Issues

  • Allow all users to deploy applications using Object Store v2. (MQ-1148)

    To increase your usage limit beyond the base 10 TPS rate limit, contact your MuleSoft account team.

2.4.1

June 4, 2018

Fixed Issues

  • Disable TLS 1.0 and 1.1. (MQ-1093)

  • Increase default OSv2 object TTL to 30 days. (MQ-1147)

2.4.0

May 5, 2018

This version of Object Store adds full partition support to the cloud Object Store V2 service.

Fixed Issues

  • Update OSv2 backend service with improved partition support. (MQ-1123)

  • Update OSv2 Mule plugin to work with partitions. (MQ-1128)

  • Update OSv2 UI with partition support. (MQ-1122)

2.3.3

April 20, 2018

Anypoint Object Store v2 has added EU Ireland as a new region to the EU Control Plane.

2.3.2

March 13, 2018

This version of Object Store v2 adds a new feature where the maximum length of the storeId and key values are now 256 characters instead of the old 128 characters.

2.3.0

January 27, 2018

The Object Store v2 is now GA and suitable for both test and production applications. This new service is a re-architecture of the current Runtime Manager object store with a focus on performance, scalability, and data privacy. Customers now have the option to select Object Store v2 as a configuration option in the Runtime Manager application deployment settings.

Object Store v2 is supported in the following locations.

If Object Store v2 is not supported in a region, it transparently maps to the closest location.

Supported regions:

  • ap-northeast-1

  • ap-southeast-1

  • ap-southeast-2

  • ca-central-1

  • eu-central-1

  • eu-west-1

  • eu-west-2

  • sa-east-1

  • us-east-1

  • us-west-2

Compatibility

Anypoint Object Store v2 works with Mule 3.7.3 and later, and Mule 4 and later.

Anypoint Object Store v2 works with these browser versions:

  • Chrome - Version 34 or later

  • Firefox - Version 29 or later

  • Internet Explorer - Version 10 or later

  • Safari - Version 7 or later

Was this article helpful?

💙 Thanks for your feedback!