I just found out why it fails... First my bad, the exception i was talking about originates from our code. Now when i fetch users i get the handle from the search and put the data returned by user lookup in a Map using the screenName as key. the problem is that there is a case mismatch for the screenName between the handle in the search and the UserInfo. Here are some examples
(search screen name after "added" & UserInfo screen name after "screenName") added rjmontalvo to cache with screenName : RJMontalvo added anaespindola to cache with screenName : AnaEspindola added stream97fm to cache with screenName : Stream97FM added manomoraes to cache with screenName : ManoMoraes added stream97fm to cache with screenName : Stream97FM added stream97fm to cache with screenName : Stream97FM added Antonio171 to cache with screenName : antonio171 added LisOliveira_ to cache with screenName : lisoliveira_ added stream97fm to cache with screenName : Stream97FM added tuvagancia to cache with screenName : TuVagancia added stclairjohn to cache with screenName : StClairJohn added 90sbaby_ to cache with screenName : 90sBABY_ added baleena to cache with screenName : Baleena added Captunes to cache with screenName : captunes added AxlVii to cache with screenName : axlvii added queengwen to cache with screenName : Queengwen added Caetanosanguine to cache with screenName : caetanosanguine added laurwen to cache with screenName : Laurwen added purasangre to cache with screenName : Purasangre added Joshmi to cache with screenName : JoshMI added thais_vial to cache with screenName : Thais_Vial On 2010-05-18, at 11:57 AM, Taylor Singletary wrote: > Hi Alain, > > The user ids in search results from search.twitter.com do not correspond to > the user ids in rest of Twitter and the Twitter API. We're working on > bridging this gap long-term. The work around is to do a user lookup based off > of the screen name instead of the member id. > > Taylor Singletary > Developer Advocate, Twitter > http://twitter.com/episod > > > On Tue, May 18, 2010 at 8:44 AM, Alain Gaeremynck <ga...@sanssucre.ca> wrote: > I am using search to gather a series of twits. I am then looking up the > users that wrote those tweets. Now sometimes for some reason i get an error > message "no user found on twitter : userhandle" > > The problem with this is that i have to parse the error message figure out > which user is missing. Rebuild the request with the rest of the users and try > again. > > It would be cool if instead when there are no such users i would get a list > of the user that exists and null or some string in the json for those that > don't. In an ideal world search would never give me results for users that > don't exists (although i guess profiles get deleted all the time). > > Does this make sense? > > Alain (@sanssucre) G > > P.S. Can you get the ops people to posts the VM startup parameters they use? > I'm very curious to see what they do in that regard. >
