It's possible to make it searchable, you will need to store and update two
entities. MyEntity will have a Properties to Values map, and you have a
PropertiesEntity that has a MyEntity to Values map.
class MyEntity {
@Id Long id;
@Serialized MapString,Object properties
}
class MyProperties {
@Id String id;
@Serialized MapLong,Object values
}
Searching by property will become very cheap and fast since you'll simply
fetch the property entity. Updates and Writes will be more complex since
you will need to write 2 entities, but there should only be a total of 4
write ops. The other way is likely to be more expensive since you will use
(2 + 2 * properties) write ops for each entity because each property will
need to be indexed.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/gIqiaTmB3SIJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
