Lets say we have a RepeatedProperty in db, prop=[t1,t2,t3,t4,...,t20] Cost/performance-wise, would it be better to put them all in a TextField such as prop="t1 t2 t3 t4 t5 t6 t7 t8 t9 ... t20" Or would it be better to create 20 AtomField's such as t1=1,t2=1,t3=1,t4=1,....
It seems use of AtomField's would be performance-wise more efficient, however I'm not sure how Search indexing is priced the query would be "search_text prop:t1" *vs *"search_text t1:1" or "search_text t2:1" While the first scenario does a text search, the second just makes an atomic match, however I'm unsure whether using excessive (20~30) amount of document fields is good or bad -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
