In Cloud Datastore, Movie entities have multi-valued properties 'actors' and 'tags' and a single-valued 'date_released'. Queries filter by actor or tag ordered by date_released. How do you avoid a combinatorial explosion of indexes?

The correct approach is to declare only the necessary composite indexes. Cloud Datastore automatically creates single-property indexes. For queries involving multi-valued properties with an ORDER BY clause on another property, composite indexes are required. By explicitly defining (actor, datereleased) and (tag, datereleased) indexes, you support the specified query patterns efficiently. Manually declaring all multi-valued property combinations leads to a combinatorial explosion, creating many unnecessary indexes that consume storage and increase write latency. Excluding multi-valued properties from indexing (excludefromindexes = 'actors, tags') would prevent filtering or ordering on those fields, making the desired queries impossible. Excluding datepublished would prevent ordering by that field.