Release Notes

6.1.1

2024-01-03

Remove recently introduced constraint preventing ObjectifyService.init() from being called more than once. You shouldn't do this in application code, but it's common for tests.

6.1.0

2023-11-27

Objectify is easier to use with multiple datastores. Several methods have been deprecated; see UpgradeVersion6ToVersion61.
Add support for OR queries in composite filters
Make count() operations operate via server-side aggregation queries
Add sum(), avg(), and aggregate() [aggregation queries|AggregationQueries]
Add ofy().load().readTime() convenience method to perform queries with a ReadOption.readTime()
Add support for IN/!IN queries (technically this was already present; they were "enabled" by updating the google-cloud-datastore jar dependency).
Example applications have been added at https://github.com/objectify/objectify-examples

6.0.9

2022-10-05

Fix the .toLegacySafe() format to exactly match the values returned by 6.0.7 (and prior) when you are not using namespaces.

6.0.8

2022-09-27

Add support for not-equal filters (!=)
Add support for in and not-in filters (IN, !IN)
Add support for composite filters (.filter(Filter)). OR support will be enabled as soon as it is available in the underlying Google SDK.
Add .stream() method to queries (eg, ofy().load().type(Foo.class).stream().map(...)
Remove deprecated Key.getString() and Key.toWebSafeString() methods (use toUrlSafe() instead)
Change Key.getId() to return Long instead of long. It was documented to return 0 when not numeric, but actually threw NPE. Now returns null.
Address a potential race condition when using memcached (issue #451)
Accommodate namespaces in the toLegacyUrlSafe() value

WARNING: The toLegacyUrlSafe() value changed slightly in this version to allow for namespaces, even if you aren't using namespaces. We recommend you use 6.0.9 instead, which fixes this issue.

5.1.25

2021-04-23

Don't raise exceptions when memcache unreachable

6.0.7

2020-08-31

Improve the error message when loading data that is incompatible with the Java schema
Handle namespaces in legacy urlsafe string keys

6.0.6

2020-01-27

Fixed a bug that might "forget" the setting of ofy().cache(false) or ofy().namespace(...) in queries
Fixed several places that ofy().namespace() was being ignored (notably, when saving entities).
Automatically batch requests that exceed datastore request count limits (ie, 1000 reads or 500 writes).
Removed some long-deprecated methods.

6.0.5

2019-11-21

Add support for java.time.Instant

5.1.23

2019-07-29

Allow some control over MemcacheService instantiation.
Minor performance improvements.

6.0.4

2019-06-03

Explicit support for Namespaces

6.0.3

2019-01-29

Fix ofy().load().ids(long...) autoboxing problem.
Better error handling when reading old-style GAE string keys.

6.0.2

2018-09-20

Fix NPE when loading a collection field which has been previously stored as null in an entity (outside of Objectify).

6.0.1

2018-08-08

Fix error when trying to fetch more than 1000 keys at a time
Expose transaction handle
Better exception when an error occurs deserializing a @Serialize field

6.0

2018-04-06

If upgrading from a previous version, be sure to read UpgradeVersion5ToVersion6!

Made the cache implementation pluggable. See the constructor javadocs for ObjectifyFactory.

6.0b1

2018-02-15

You must call one of the overloads of ObjectifyService.init() during your application bootstrap (see UpgradeVersion5ToVersion6).
Creating a key from a string now accepts both the old-style ("agblahblahzxcpvouaw") and new-style urlsafe strings. You can generate them with Key.toUrlSafe() and Key.toLegacyUrlSafe().
Added ofy().load().option(...) to allow manual control of read consistency.

5.1.22

2018-01-29

POJOs fields with the @Serialize annotation now load correctly even when the underlying data type is ShortBlob. This can happen if you write the data outside of Objectify.

6.0a1

2017-12-23

This is the first version of Objectify that works with the new Google Cloud SDK. A list of changes is being maintained here: https://github.com/objectify/objectify/wiki/UpgradeVersion5ToVersion6

5.1.21

2017-07-06

Fixed issue causing the alsoLoad attribute of the @Subclass annotation to be ignored.

5.1.20

2017-07-03

Fixed bug in autoconversion of long unicode strings to Text, introduced in v5.1.18. The conversion limit is 1500 bytes not characters.

5.1.19

2017-06-28

Fixed performance bug causing memcache operations even for non-cacheable entities.

5.1.18

2017-06-28

At some point the max char limit for a String in the datastore was raised from 500 to 1500. Objectify's autoconvert-to-Text code now reflects this new higher limit.

5.1.17

2017-04-09

Optimized performance of query list(); async query was not being kicked off until first element accessed, which means it wasn't actually async at all. iterable() still has this undesirable behavior, although iterator() is properly async.

5.1.16

2017-03-16

Add ofy().mandatoryTransactions(true) to force users to create a transaction context for any save() or delete() operations. A useful defensive check.

5.1.15

2017-02-15

Expose constructor for EntityMemcache which allows MemcacheServiceFactory to be passed in. No behavioral changes.

5.1.14

2016-12-23

Ensure lifecycle events are fired in ofy().load().fromEntity()
Support fields of type Number

5.1.13

2016-05-25

Fixed bug causing collection fields to be ignored if they contain an empty nested subcollection.

5.1.12

2016-03-17

User code can now attach arbitrary data to transaction contexts through the TransactionImpl.bag property.

5.1.11

2016-03-07

ShortBlob properties are automatically converted to byte[] fields. byte[] fields are still saved as Blob.

5.1.10

2016-01-28

Added ofy().transact(Runnable) overload for Java8/retrolambda users

5.1.9

2015-11-08

With a few exceptions, @Load annotations no longer produce load effects in transactions. This reduces the tendency of @Load to bring in unwanted entity groups. Within transactions, @Parent relationships and @Load with explicitly activated groups will still force loading.
Deferred saves within @OnSave methods now work properly.
execute(TxnType.REQUIRES_NEW) now starts a new transaction like it's supposed to

5.1.8

2015-09-12

Relaxes requirement that a class have the @Entity annotation to be used to create a Key<?>. The kind will be the simplename of that class. Registered POJO entity classes still require the @Entity annotation; this only affects key creation.

5.1.7

2015-08-30

Classes marked @Entity which are stored embedded are allowed to have null keys. Previously, any @Id Long fields had to be populated with a real value. Now they are allowed to be null, which will leave the underlying EmbeddedEntity with a null key. The underlying datastore allows this. Note that unlike with top level entities, saving a null @Id does NOT autogenerate an id.

5.1.6

2015-08-09

Objectify.transactNew(count, work) was documented as # of tries but behaved as # of retries. Behavior now reflects documentation - # of tries.
Added missing overload for Query.filterKey(Object)
In transactions, only the first layer of fetching is performed asynchronously. All subsequent loads (via @Load annotations) are performed synchronously when the first layer of entities are materialized. This eliminates a rare edge case that produced spurious 'transaction closed' exceptions during transaction collisions. Outside of transactions, all fetches are performed asynchronously as normal.

5.1.5

2015-02-04

Fix NPE when doing kind() queries.
Fix NPE when a null value is projected.

5.1.4

2015-01-06

When an entity is explicitly saved or deleted, clear any pending deferred operations on that entity
Fix NPE when projecting properties with null values
Allow deleting of native Entity objects
Added ofy().load().kind(...) method
No longer need to de-hybridize IN and NOT queries

5.1.3

2014-12-01

Fixed a cross-compilation problem which produced a corrupt artifact for 5.1.2. No other changes.

5.1.2

2014-11-27

Don't use this version; the published artifact is corrupt.

Call superclass @OnSave methods before subclass @OnSave methods
Allow deferred save of entities with autogenerated ids.

5.1.1

2014-10-13

Fixed a problem with ObjectifyFilter re-entrancy that manifested when using dispatch.forward().
- Note that this means you will not be warned if you leak Objectify contexts via ObjectifyService.begin()

5.1

2014-10-09

Added ofy().defer() and ofy().flush()
An exception will be thrown if you try to use Objectify without the ObjectifyFilter
A new method for using Objectify outside of normal request handling (unit tests, remote api, etc)

If you are using Objectify outside of a normal GAE http request (eg, unit tests or the the remote api), there is a new method you must invoke. See javadocs for ObjectifyService.run(). The old ObjectifyFilter.complete() method has been removed.