No Mick. I wasn't exactly trying to do this. But start from a wide row with a very large number of columns, and allow a Hadoop integration based on that.
So basically, in the map phase, we'll be dealing with multiple CFs, and hence I wanted to solve this problem of identifying which key/CF belongs to which Cassandra node. On Mon, Sep 26, 2011 at 12:37 AM, Mick Semb Wever <m...@apache.org> wrote: > On Thu, 2011-09-22 at 23:34 +0530, Tharindu Mathew wrote: > > I managed to modify the Hadoop-Cassandra integration to start with a > > column of a CF used for indexing. > > Are you chasing CASSANDRA-2878 here? > The above issue is waiting on CASSANDRA-1600 which in turn in waiting on > CASSANDRA-1034 > > ~mck > > -- > "Although the Buddhists will tell you that desire is the root of > suffering, my personal experience leads me to point the finger at system > administration." Philip Greenspun > > | http://semb.wever.org | http://sesat.no | > | http://tech.finn.no | Java XSS Filter | > -- Regards, Tharindu blog: http://mackiemathew.com/
