Hi,

Looking for answers to the following questions.

1) If one invokes the firehose yql call in a loop, are we guaranteed to get different data set ever time e.g., in the first call we get "x" updates and in the second call we get "y" updates where Intersection(x,y) = null?
2) I was under the impression that once you connect to Y! servers you keep getting the data back as long as one holds the connection open, doesn't look like this is the supported semantics.
3) Looks like the firehose API supports pagination parameters? what is the semantics of such pagination do one get to go back in time and get the data? is it allowed? Looks like a wrong capability for firehose like API's? I guess it is the result of YQL abstraction!
4) Does it have twitter or facebook updates too? especially if Y! accounts are linked to facebook.

I guess I will buy a lottery ticket if I get a response :-) quickly i.e.,.

After using the firehose successfully for a while, last week I stopped receiving information from the fire hose. Testing in the development console provides the following error. The "Connect Failure" has been seen all along.

Any information available on this error?

--Thank you,
--Tyler MacLeod

    yahoo:count="0" yahoo:created="2011-01-18T19:00:03Z" yahoo:lang="en-US">

false

276
275
10682

Hi people,

I have doubt about the count limit of queries on update firehose table. Say, I've typed this query on my console:
"select source, suid, type from social.updates.search(1100,100) |sort(field="pubDate");"

But I got no update json object, and I've noted this point, at tree output, inside the console:

http-status-code : 400
http-status-message : Bad Request
content : http://social.yahooapis.com/yosapt_mt_feed...00&hits=100

So, anybody could answer me what these things mean? Can I get more than 1100 updates json objects?

Cheers and hugs,
Saulo

After further exploration, this seems to be related (as a theory) to "execution time". Empirically, any queries that take over 1000 (don't know the units here) tend to return zero results, those that take less than that succeed.

In my usage, the firehose query "Select * from social.updates.search;" in the YQL console often takes over 1000 (units?) to complete.

HI - I'm exploring the Yahoo Firehose YQL query via the YQL console and I'm getting inconsistent behavior. Most times the query returns zero responses and occasionally I get a resultset. I've attached 2 screenshots from sequential queries.

Anyone else seeing this behavior? Is this a known issue?

Cool data here, but I'm not feeling very confident that it's reliable.

Screenshot of query with no results (note the count=0 and results=null)


Screenshot of very next query with 10 results


Rob Johnson
Gnip

Hi Chris,

It looks like the problem has an easy fix: replace the "*" char in "select * from ..." w/ "%2A".

In other words, you need to percent-encode the star. Your oauth lib is doing this for you when generating the base string for the signature, but the query in your request has the unencoded char, so the signature we generate from your request doesn't match the one you send over.

I just ran this successfully using the oauth gem (v 4.0):

# replace w/ your key/secret from https://developer.apps.yahoo.com/projects
consumer_key = "k9TDNTVXpvRnpsbjJHJmQ9WVdrOVpXRlBkWEJETQS0tJnM9Y29uc3VtZXJzZWNyZXQmeD0wYw--"
consumer_secret = "4fe7cfc3d744d5dad769d21dd9c804"

@consumer = OAuth::Consumer.new(consumer_key, consumer_secret, :site => "http://query.yahooapis.com")

access_token = OAuth::AccessToken.new @consumer

# note the %2A in query
print access_token.get("/v1/yql?q=select%20%2A%20from%20social.updates.search%20where%20query%3D%22search%20terms%22&diagnostics=false").body

Hi Chris,

I've tried w/ a couple different libraries in ruby (incl http://github.com/mojodna/oauth ) and js, and think it might be on our side. Would you mind trying w/ a different 2-leg oauth API, like Photobucket's login token request ( http://photobucket.com/developer , http://pic.pbsrc.com/dev_help/WebHelpPubli...tPublicHelp.htm ) as a sanity check?

Can you successfully fetch a Y! request token ( http://developer.yahoo.com/oauth/guide/oau...questtoken.html )? This would help isolate the issue by demonstrating that your lib/env can make a 2-leg req to a Y! endpoint.

Thanks

Hi, I'm new to the Yahoo APIs, so sorry in advance if this is a common question. I'm trying to programmatically connect to the new firehose API. I used the console to build a test query and it gave me the url:

"http://query.yahooapis.com/v1/yql?q=select%20*%20from%20social.updates.search%20where%20query%3D%22iceland%22&diagnostics=true"

I then went and created a project with a consumer key of type "OAuth Application" with permissions set to

"All public APIs, Web Services, or RSS feeds including those provided by Yahoo!"

key = "dj0yJmk9Z2VMcG9TTXpuRXMyJmQ9WVdrOVdFSm1lVWs0TkRJbWNHbzlNakV4TURRMU5EWTJNZy0
tJnM9Y29uc3VtZXJzZWNyZXQmeD0zNA--"

But when I plug the key, the secret & the url into some existing oauth code, that works with other endpoints, I get back an error message:

Please provide valid credentials

If you can deal with a Ruby object dump, the request object looks like:

>> request.to_hash
=> {"accept"=>["*/*"], "user-agent"=>["OAuth gem v0.3.6"], "connection"=>["close"], "authorization"=>["OAuth oauth_nonce=\"d0D4DyugcpjDYfPAUVy6gPHbhlkP0gCCdyuMdxavwk\", oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1271877158\", oauth_consumer_key=\"dj0yJmk9Z2VMcG9TTXpuRXMyJmQ9WVdrOVdFSm1lVWs0TkRJbWNHbzlNakV4TURRMU5EWTJNZy0
tJnM9Y29uc3VtZXJzZWNyZXQmeD0zNA--\", oauth_signature=\"ycm5V%2BXmdU861gMc%2Fn53FWlZPF8%3D\", oauth_version=\"1.0\""], "host"=>["query.yahooapis.com"]}


Oddly, I get the exact same error message if I try to load that url via curl without any oauth at all.

Any ideas what I'm doing wrong?

Thanks,
-Chris

Please let us know if you have any questions or suggestions!

Cheers!
Robyn Tippins
@duzins on Twitter
Community Manager, YDN