Yes, one index needs to be created per property. You can also set this field
to unindexed if you do not need to search on this data.
On Tue, Apr 6, 2010 at 9:50 AM, Petrov Aleksander <ass.pet...@gmail.com>wrote:
> I have an entity with Collection property like this:
>
> class MyEntity{
> List<String> myStrCollection = new ArrayList<String>();
> .....other properties......
> }
>
> Instance of MyEntity can contain myStrCollection property with 200
> values;
> I have about 10 different indexes containing filter by
> myStrCollection.
>
> So the question is:
> is it OK to do such queries?
> I read that BigTable would create a lot of index rows for one entity
> with collection property and now I feel that such a big collection
> could affect efficiency (saving or searching).
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appeng...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
--
Ikai Lan
Developer Programs Engineer, Google App Engine
http://googleappengine.blogspot.com | http://twitter.com/app_engine
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
