Skip to content
This repository has been archived by the owner on Aug 18, 2019. It is now read-only.

Add ability to specify indexing in CounterData Entity class #18

Closed
sappenin opened this issue Mar 14, 2015 · 1 comment
Closed

Add ability to specify indexing in CounterData Entity class #18

sappenin opened this issue Mar 14, 2015 · 1 comment

Comments

@sappenin
Copy link
Member

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.

@sappenin
Copy link
Member Author

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.

sappenin added a commit that referenced this issue Mar 14, 2015
Adds optionally specified indexing to the CounterData properties as well as to a Counter's eventually consistent "count" as found in CounterData.CounterGroupData.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant