Ok. So I've changed the entities to use entity.setUnindexedProperty(). To get rid of the superfluous the indices I'm doing something like this:
Query q = new Query(PlayerSnapshot.class.getName()); List<Entity> asList = ds.prepare(q).asList(FetchOptions.Builder.withLimit(n).offset(o)); ds.put(asList); Unfortunately I'm out of quota for the day, so I can't confirm that this will work. Will it work? --Erik On Wed, Feb 9, 2011 at 06:15, Robert Kluin <[email protected]> wrote: > Hi Erik, > If you mark them as unindexed, new entities will not be indexed, > but you'll have to re-put your existing data to clear up the space. > > > > > Robert > > > > > > > On Tue, Feb 8, 2011 at 16:54, Erik Lindblad <[email protected]> wrote: >> Hey guys! >> >> This seems to be exactly what's happening. I'll take a look at it >> tomorrow when I'm, ehrm, back in the game (happy birthday to me! :) >> >> I have 17 props/entity, so if GAE started to implicitly index the the >> quota makes sense. (code is available on >> http://github.com/onemanbucket/alleg-leaderboard ) >> >> I have a question though, can I update my model properties to be >> explicitly unindexed and drop the superfluous indices already created? >> One poster in the thread Robin posted says "The annotation applies to >> new data records only, you have to rewrite older ones or wait until >> they expire (as I do)". >> >> Cheers, >> Erik >> >> On Tue, Feb 8, 2011 at 19:47, Ikai Lan (Google) >> <[email protected]> wrote: >>> Hi Erik, >>> Can you post the definition for one of your entities? I look at look at your >>> dashboard, and here's what I see: >>> - 105mb used by datastore entities >>> - 0 tasks using task queue stored bytes quota >>> - 0 blobstore bytes used >>> - 1 COMPOSITE index >>> Note that built-index indices also consume storage. For instance, let's say >>> you have an entity with the properties: >>> - name : String >>> - createdAt : timestamp >>> Unless you explicitly mark these properties as unindexed, we will created >>> indexes for these properties, but we will NOT display them on the datastore >>> indexes tab in your admin console, since they are not composite indices. See >>> the bit here about setting indexed=False: >>> http://code.google.com/appengine/docs/python/datastore/propertyclass.html >>> >>> -- >>> Ikai Lan >>> Developer Programs Engineer, Google App Engine >>> Blogger: http://googleappengine.blogspot.com >>> Reddit: http://www.reddit.com/r/appengine >>> Twitter: http://twitter.com/app_engine >>> >>> >>> On Tue, Feb 8, 2011 at 10:21 AM, Robert Kluin <[email protected]> >>> wrote: >>>> >>>> Hi Erik, >>>> There are several things that can eat into your stored-data quota. >>>> >>>> Did you explicitly disable indexes on all of your properties except >>>> the timestamp? If not you have two indexes on each property. Indexes >>>> can easily double your stored data size. If you'd like to see index >>>> stats, star issue 2740: >>>> http://code.google.com/p/googleappengine/issues/detail?id=2740 >>>> >>>> Does your app use tasks? Tasks now use some of your stored data quota. >>>> >>>> Also, any data you have stored in the blobstore will use your >>>> stored-data quota. >>>> >>>> Some of the stored-data counts do not reset in real-time, but are >>>> periodically updated. So you might see a sudden drop in your >>>> stored-data. >>>> >>>> Robert >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Tue, Feb 8, 2011 at 03:19, Erik Lindblad <[email protected]> >>>> wrote: >>>> > Hello! >>>> > >>>> > I've been experimenting with GAE for a couple of weeks. My project is >>>> > a leaderboard java/js app for an online game. It's currently backed by >>>> > ~200k data point entities that should use <200 mb of storage. >>>> > >>>> > The datastore statistics tab reports that size of all entities (153k) >>>> > is 105mb. I have one index (ascending on timestamp). Yet the quota is >>>> > now 100%. Any ideas? >>>> > >>>> > The app-id is 'alleg-leaderboard', if anyone from google wants to take >>>> > a look. >>>> > >>>> > -- >>>> > You received this message because you are subscribed to the Google >>>> > Groups "Google App Engine" group. >>>> > To post to this group, send email to [email protected]. >>>> > To unsubscribe from this group, send email to >>>> > [email protected]. >>>> > For more options, visit this group at >>>> > http://groups.google.com/group/google-appengine?hl=en. >>>> > >>>> > >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Google App Engine" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]. >>>> For more options, visit this group at >>>> http://groups.google.com/group/google-appengine?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google App Engine" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> For more options, visit this group at >>> http://groups.google.com/group/google-appengine?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
