Geocoded OR search broken?
14 views
Skip to first unread message
Mack D. Male
Sep 8, 2009, 8:48:17 PM9/8/09
to Twitter Development Talk
Until a couple of hours ago, searching for something like "edmonton OR
#yeg OR near:edmonton" (or the API equivalent) worked just fine. Now
it doesn't return anything new, and seems to return an odd set of old
results.
You can search for them separately, as in "edmonton OR #yeg" and
"near:edmonton" but not together.
What gives?
#yeg OR near:edmonton" (or the API equivalent) worked just fine. Now
it doesn't return anything new, and seems to return an odd set of old
results.
You can search for them separately, as in "edmonton OR #yeg" and
"near:edmonton" but not together.
What gives?
Alex Payne
Sep 8, 2009, 9:05:32 PM9/8/09
to twitter-deve...@googlegroups.com
Our Search Team informs me that they shipped a new query parser today.
This is likely a bug in the new parser, and I've let them know about
it.
This is likely a bug in the new parser, and I've let them know about
it.
--
Alex Payne - Platform Lead, Twitter, Inc.
http://twitter.com/al3x
Mack D. Male
Sep 8, 2009, 9:13:02 PM9/8/09
to Twitter Development Talk
Awesome, thanks!
On Sep 8, 7:05 pm, Alex Payne <a...@twitter.com> wrote:
> Our Search Team informs me that they shipped a new query parser today.
> This is likely a bug in the new parser, and I've let them know about
> it.
>
On Sep 8, 7:05 pm, Alex Payne <a...@twitter.com> wrote:
> Our Search Team informs me that they shipped a new query parser today.
> This is likely a bug in the new parser, and I've let them know about
> it.
>
Jose Tinoco
Sep 8, 2009, 9:25:14 PM9/8/09
to Twitter Development Talk
Geocoded API searches are also broken. This is the geocoding example
from the API documentation, which used to work and now doesn't:
http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C25km
My website (blablabra.net) does similar searches and now receives only
403 Forbidden errors or an empty XML/JSON with "You must enter a
query" if I try this search on my browser window.
On Sep 8, 10:05 pm, Alex Payne <a...@twitter.com> wrote:
> Our Search Team informs me that they shipped a new query parser today.
> This is likely a bug in the new parser, and I've let them know about
> it.
>
from the API documentation, which used to work and now doesn't:
http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%2C25km
My website (blablabra.net) does similar searches and now receives only
403 Forbidden errors or an empty XML/JSON with "You must enter a
query" if I try this search on my browser window.
On Sep 8, 10:05 pm, Alex Payne <a...@twitter.com> wrote:
> Our Search Team informs me that they shipped a new query parser today.
> This is likely a bug in the new parser, and I've let them know about
> it.
>
Dewald Pretorius
Sep 8, 2009, 10:04:17 PM9/8/09
to Twitter Development Talk
FFS.
Any chance that things will actually be tested before they are rolled
out into PRODUCTION?
Dewald
On Sep 8, 10:25 pm, Jose Tinoco <jose.tin...@gmail.com> wrote:
> Geocoded API searches are also broken. This is the geocoding example
> from the API documentation, which used to work and now doesn't:
>
> http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%...
Any chance that things will actually be tested before they are rolled
out into PRODUCTION?
Dewald
On Sep 8, 10:25 pm, Jose Tinoco <jose.tin...@gmail.com> wrote:
> Geocoded API searches are also broken. This is the geocoding example
> from the API documentation, which used to work and now doesn't:
>
Hrishikesh Bakshi
Sep 8, 2009, 10:10:16 PM9/8/09
to twitter-deve...@googlegroups.com
Quick fix:
Add q=* to your URL--
Hrishikesh Bakshi
Add q=* to your URL
Hrishikesh Bakshi
Hrishikesh Bakshi
Sep 8, 2009, 10:13:36 PM9/8/09
to twitter-deve...@googlegroups.com
Jose Tinoco
Sep 9, 2009, 6:35:12 AM9/9/09
to Twitter Development Talk
You're a LIFE SAVER man. Thank you very much.
And I couldn't agree more: @twitterapi should have notified us. I sent
him a @reply but got no answer so far.
On Sep 8, 11:10 pm, Hrishikesh Bakshi <bakshi.hrishik...@gmail.com>
wrote:
And I couldn't agree more: @twitterapi should have notified us. I sent
him a @reply but got no answer so far.
On Sep 8, 11:10 pm, Hrishikesh Bakshi <bakshi.hrishik...@gmail.com>
wrote:
Samuel Luckenbill
Sep 9, 2009, 2:19:32 PM9/9/09
to Twitter Development Talk
Hey Folks,
The bug is specifically that all queries using the geocode parameter
with no query string return no results. We'll launch a bug fix today.
In the interim, you can use the geocode: operator in the query string
or add a bogus string as someone else has suggested. Sorry for the
inconvenience and we appreciate your patience.
Sam
On Sep 8, 6:25 pm, Jose Tinoco <jose.tin...@gmail.com> wrote:
> Geocoded API searches are also broken. This is the geocoding example
> from the API documentation, which used to work and now doesn't:
>
> http://search.twitter.com/search.atom?geocode=40.757929%2C-73.985506%...
The bug is specifically that all queries using the geocode parameter
with no query string return no results. We'll launch a bug fix today.
In the interim, you can use the geocode: operator in the query string
or add a bogus string as someone else has suggested. Sorry for the
inconvenience and we appreciate your patience.
Sam
On Sep 8, 6:25 pm, Jose Tinoco <jose.tin...@gmail.com> wrote:
> Geocoded API searches are also broken. This is the geocoding example
> from the API documentation, which used to work and now doesn't:
>
Alex Payne
Sep 9, 2009, 2:52:19 PM9/9/09
to twitter-deve...@googlegroups.com
Another note: the Search API documentation has been updated to reflect
that querying based on geocode is not compatible with disjunctions (OR
queries).
that querying based on geocode is not compatible with disjunctions (OR
queries).
Please see the "Operator Limits" section of
http://apiwiki.twitter.com/Twitter-Search-API-Method:-search.
Mack D. Male
Sep 9, 2009, 5:14:46 PM9/9/09
to Twitter Development Talk
Sorry, why is it not compatible with disjunctions? That seems like a
bug, not a change in functionality. Basically what you're saying is
that if I search for "edmonton" and geocode it, I get location
information. Or if I search for "#yeg" and geocode it, I get location
information. But if I search for "edmonton OR #yeg" and geocode it, I
don't get location information? When I did until yesterday? And
received no warning about a change?
On Sep 9, 12:52 pm, Alex Payne <a...@twitter.com> wrote:
> Another note: the Search API documentation has been updated to reflect
> that querying based on geocode is not compatible with disjunctions (OR
> queries).
>
> Please see the "Operator Limits" section ofhttp://apiwiki.twitter.com/Twitter-Search-API-Method:-search.
bug, not a change in functionality. Basically what you're saying is
that if I search for "edmonton" and geocode it, I get location
information. Or if I search for "#yeg" and geocode it, I get location
information. But if I search for "edmonton OR #yeg" and geocode it, I
don't get location information? When I did until yesterday? And
received no warning about a change?
On Sep 9, 12:52 pm, Alex Payne <a...@twitter.com> wrote:
> Another note: the Search API documentation has been updated to reflect
> that querying based on geocode is not compatible with disjunctions (OR
> queries).
>
Voolkan
Sep 11, 2009, 2:20:20 PM9/11/09
to Twitter Development Talk
Something really weird seems to be going on with the search today.
I first noticed I couldn't search for my own Tweets; a query for
"voolkan #jobs ny" for instance used to turn up my latest tweets about
jobs in New York, now it won't return any results posted since
yesterday.
When trying to investigate this, I just did some more general
searches--just the #jobs hash, for instance--and noticed some strange
things going on. First, every result coming back was posted three
minutes ago or longer--#jobs is a very active hash, so that's
obviously not the case.
Later, more recent results were coming back, but seemed to be mixed in
all together. Searching repeatedly would show the same tweets shifting
up and down, before and after other tweets that had supposedly been
posted at different times.
Finally, updating search results doesn't really updating anything. I'm
informed that there are "98 new posts since my search," click the
refresh button, and have a small handful pop up.
Does anyone know what's going on here?
I first noticed I couldn't search for my own Tweets; a query for
"voolkan #jobs ny" for instance used to turn up my latest tweets about
jobs in New York, now it won't return any results posted since
yesterday.
When trying to investigate this, I just did some more general
searches--just the #jobs hash, for instance--and noticed some strange
things going on. First, every result coming back was posted three
minutes ago or longer--#jobs is a very active hash, so that's
obviously not the case.
Later, more recent results were coming back, but seemed to be mixed in
all together. Searching repeatedly would show the same tweets shifting
up and down, before and after other tweets that had supposedly been
posted at different times.
Finally, updating search results doesn't really updating anything. I'm
informed that there are "98 new posts since my search," click the
refresh button, and have a small handful pop up.
Does anyone know what's going on here?
Dewald Pretorius
Sep 11, 2009, 3:46:44 PM9/11/09
to Twitter Development Talk
Search has been doing that for a month or two, as far as I know.
It tells you there are new tweets, but when you click refresh, it does
not show you the new tweets. Or it would say there are 35 new tweets,
and show you only 5 when you click refresh.
Dewald
It tells you there are new tweets, but when you click refresh, it does
not show you the new tweets. Or it would say there are 35 new tweets,
and show you only 5 when you click refresh.
Dewald
Chad Etzel
Sep 11, 2009, 6:15:51 PM9/11/09
to twitter-deve...@googlegroups.com
This usually happens during peak tweet times and the search servers
get out of sync updating the indexes across all of the boxes. So, when
you refresh, you might be getting results from a different server with
a non-identical set of results. We're working to eliminate these
discrepancies, but as you can imagine it's a tricky problem.
-Chad
get out of sync updating the indexes across all of the boxes. So, when
you refresh, you might be getting results from a different server with
a non-identical set of results. We're working to eliminate these
discrepancies, but as you can imagine it's a tricky problem.
-Chad
Voolkan
Sep 14, 2009, 9:48:50 AM9/14/09
to Twitter Development Talk
Hey Chad,
Thanks for the reply, and I can understand how tricky that must be.
It's kind of curious though--at some point over the weekend, several
more (but still not all) of our tweets were indexed and searchable,
yet our live tweets still aren't. This at least leads me to believe
that our account wasn't banned for some reason, so that's a relief!
Still odd that over the weekend, even our old tweets were and are only
partially searchable...
Thanks for the reply, and I can understand how tricky that must be.
It's kind of curious though--at some point over the weekend, several
more (but still not all) of our tweets were indexed and searchable,
yet our live tweets still aren't. This at least leads me to believe
that our account wasn't banned for some reason, so that's a relief!
Still odd that over the weekend, even our old tweets were and are only
partially searchable...
Reply all
Reply to author
Forward
0 new messages