They ditched the effort to switch the status store to Cassandra though. http://engineering.twitter.com/2010/07/cassandra-at-twitter-today.html
Abraham ------------- Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Sep 29, 2010 at 18:10, M. Edward (Ed) Borasky < zn...@borasky-research.net> wrote: > Yeah - lots of them to choose from, although Twitter has invested a fair > amount of time in Cassandra and Hadoop/Pig. > > -- > M. Edward (Ed) Borasky > http://borasky-research.net http://twitter.com/znmeb > > "A mathematician is a device for turning coffee into theorems." - Paul > Erdos > > > Quoting Gabriel Harriman <mynameisg...@gmail.com>: > > Oh wow, I like the NoSQL data store idea. =) >> >> >> On Sep 29, 2010, at 3:55 PM, M. Edward (Ed) Borasky wrote: >> >> Quoting mynameisgabe <mynameisg...@gmail.com>: >>> >>> I've been googling like crazy and searching the streaming api docs for >>>> the answer to this question: Where would I find the latest definition >>>> for json objects returned by the stream? Specifically I'm looking for >>>> field names, data types and max lengths (if available) that will be >>>> returned. I'm using the filter tracking several keywords. >>>> >>>> Thanks! >>>> >>>> Gabe >>>> >>> >>> I don't think I've seen anything like that - Twitter tends to announce >>> format changes on this list, but I don't know that there's a "reference >>> document" anywhere. When I write Streaming tests, I usually just grab >>> whatever comes down the pipe and stash it away as text, or parse the JSON >>> to a Perl or Ruby object and "flatten" the resulting hash. Of course, I'm >>> just generating CSV - more advanced users might simply be using a >>> leading-edge NoSQL data store. ;-) >>> >>> -- >>> M. Edward (Ed) Borasky >>> http://borasky-research.net http://twitter.com/znmeb >>> >>> "A mathematician is a device for turning coffee into theorems." - Paul >>> Erdos >>> >>> >>> >>> >> >> > > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
