You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2019. It is now read-only.
Currently, if a library user wants to index (e.g.) the CounterData.CounterStatus field, it's not easily possible. We should introduce a new mechanism to allow people to specify which fields of CounterData should be indexed in the Datastore and which fields should not.
Plausibly, this could be accomplished with a combination of Objectify's If.java interface (essentially a poor-man's interceptor framework) and objectify-utils' annotation-based config see here for the Money.java annotation.
The text was updated successfully, but these errors were encountered:
This is complete and will be available in the 1.1.1 version. The default indexing option is to not index any of these fields, so compatibility with 1.1.x is acheived. Hence, adding to version 1.1.1.
Adds optionally specified indexing to the CounterData properties as well as to a Counter's eventually consistent "count" as found in CounterData.CounterGroupData.
Currently, if a library user wants to index (e.g.) the CounterData.CounterStatus field, it's not easily possible. We should introduce a new mechanism to allow people to specify which fields of CounterData should be indexed in the Datastore and which fields should not.
Plausibly, this could be accomplished with a combination of Objectify's If.java interface (essentially a poor-man's interceptor framework) and objectify-utils' annotation-based config see here for the Money.java annotation.
The text was updated successfully, but these errors were encountered: