Suppose we have a Model with at least several properties with explicitly disabled indexes:

class A(db.Model):
foo = db.IntegerProperty(indexed=False)
bar = db.IntgereProperty(indexed=False)

Then Python AppEngine SDK 1.4.0 refuses to create and use composite indexes, which contain at least one property with explicitly disabled index:

A.all().filter('foo =', 1).filter('bar >', 2)
A.all().filter('foo =', 1).order('bar')
A.all().filter('foo =', 1).order('-bar')
A.all().ancestor(some_key).order('bar')
A.all().filter('foo =', 1).order('-__key__')

The same applies for GQL queries:

A.gql('WHERE foo = 1 AND bar > 2')
A.gql('WHERE foo = 1 ORDER BY bar')
A.gql('WHERE foo = 1 ORDER BY bar DESC')
A.gql('WHERE ANCESTOR IS :1 ORDER BY bar', some_key)
A.gql('WHERE foo = 1 ORDER BY __key__ DESC')

If indexed=False is substituted by indexed=True for each property from composite index, then queries mentioned above work as expected. But it is unclear why distinct per-property indexes are required when only composite index is used? Redundant per-property indexes in this case waste CPU time and datastore storage for no reason.

See also the https://groups.google.com/group/google-appengine/browse_thread/thread/c40346a1d8cc63b8 .

Issue 35888740

Links (5)

Issue metadata