I created an extra app, named peechobloog. The indexes get stuck in
that one, too. However, I played around with the actual order of the
indexes in the index.yaml file, and it seems that this index...
- kind: Article
properties:
- name: published
direction: desc
...is causing problems. It doesn't show up in the list of indexes, and
everything after it is mentioned doesn't show up either. If I put the
indexes below it on top of the list, they do show up - but not this
one. Isn't that weird?
It seems like the simplest index.
On Aug 11, 4:28 pm, Peecho <san...@peecho.com> wrote:
> Yes, I have run these commands, but the indexes are still stuck
> (again). Since the indexes are standard Bloog (and I don't see anybody
> else complaining), would it be worth a try to deploy the code into
> another app to see if it would work there? Or is there anything else I
> could do?
>
> Thanks for your help so far, anyway.
>
> By the way, the Bloog coders did not deploy the search fix into the
> code yet, but I did send Bill Katz a message.
>
> On Aug 11, 1:18 pm, "Nick Johnson (Google)" <nick.john...@google.com>
> wrote:
>
>
>
> > On Mon, Aug 10, 2009 at 8:46 PM,Peecho<san...@peecho.com> wrote:
>
> > > Thanks, I could vacuum them now.
>
> > > However, my second attempt does not seem to do much either. I am a
> > > Python newbie, so I fear I do something wrong...
> > > For some reason, I see only 4 indexes 'building' in my console, while
> > > my index.yaml actually describes 7 indexes. Does that mean some error
> > > in the other three?
>
> > Have you run 'update_indexes' or 'update' since you last vacuumed?
>
> > > This is my index.yaml (standard Bloog - I added only one line of code
> > > to fix the search - see note below):
>
> > > indexes:
>
> > > - kind: Article
> > > properties:
> > > - name: __searchable_text_index
> > > - name: published
> > > direction: desc
>
> > > - kind: Article
> > > properties:
> > > - name: article_type
> > > - name: published
> > > direction: desc
>
> > > - kind: Article
> > > properties:
> > > - name: article_type
> > > - name: title
>
> > > - kind: Article
> > > properties:
> > > - name: display_type
> > > - name: published
> > > direction: desc
>
> > > - kind: Article
> > > properties:
> > > - name: published
> > > direction: desc
>
> > > - kind: Article
> > > properties:
> > > - name: tags
> > > - name: published
> > > direction: desc
>
> > > - kind: Comment
> > > properties:
> > > - name: article
> > > - name: thread
>
> > > Note: I added the following line in def _ToPb (search.py) at line
> > > number 270:
>
> > > prop.set_multiple(len(keywords) > 1)
>
> > > Does this compromise the indexes, you think?
>
> > No, it doesn't. Have you checked if bloog has fixed this, however? You
> > may not need to make the change yourself.
>
> > -Nick Johnson
>
> > > Thanks again!
>
> > > Sander
> > > On Aug 10, 2:59 pm, "Nick Johnson (Google)" <nick.john...@google.com>
> > > wrote:
> > >> HiPeecho,
>
> > >> I've moved your indexes to 'error'. Try vacuuming them now.
>
> > >> -Nick Johnson
>
> > >> On Sat, Aug 8, 2009 at 2:48 PM,Peecho<san...@peecho.com> wrote:
>
> > >> > Hi,
> > >> > My indexes seem stuck in Building for over 4 days now. I tried to
> > >> > vacuum them but alas. Could anybody help me out, please?
> > >> > My app's name is peechotest.
>
> > >> > Thanks!
>
> > >> --
> > >> Nick Johnson, Developer Programs Engineer, App Engine
>
> > --
> > Nick Johnson, Developer Programs Engineer, 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-appengine@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
-~----------~----~----~----~------~----~------~--~---
