[Developers] Query worked last night, today it times out

Mike Travers mt at alum.mit.edu
Mon Apr 9 21:30:43 UTC 2007


Well, now it's working, but there was a short period after your reboot
where it wasn't. Mysterious.

Mike

On 4/9/07, Mike Travers <mt at alum.mit.edu> wrote:
> I'm still getting the timeouts as before.
>
> Mike
>
> On 4/9/07, Tim Kientzle <tim at metaweb.com> wrote:
> > We were having some system problems starting around 11am PDT.
> > Those seem to be resolved now.
> >
> > Please try again and let us know if you're still having
> > problems.
> >
> > Tim Kientzle
> >
> > On Apr 9, 2007, at 1:02 PM, Mike Travers wrote:
> >
> > > I made a simple page with mjt to show the most recently created
> > > objects, using this query:
> > > [{
> > >     "creator":{name: null},
> > >     "limit":100,
> > >     "name":null,
> > >     "id": null,
> > >     "sort":"-timestamp",
> > >     "timestamp":null,
> > >     "type": [{name: null, id: null}]
> > >   }]
> > >
> > > This worked fine until this morning, now it doesn't. It appears to be
> > > timing out (when I run it from the query editor page). Removing the
> > > "type" clause seems to fix the timeout, but I'd like to be getting
> > > that information.
> > >
> > > Maybe this is a bad query to be doing since it ranges over the whole
> > > universe. But it's strange that the behavior changed abruptly. It
> > > works OK on sandbox.
> > >
> > > Mike
> > > _______________________________________________
> > > Developers mailing list
> > > Developers at freebase.com
> > > http://lists.freebase.com/mailman/listinfo/developers
> >
> >
>



More information about the Developers mailing list