Billy Pearson wrote:
...
Maybe this is a api triping me up and eclipse is not finding the
change with the new jar for 0.2.0
Incompatible classes whose serialization/deserializations don't matchup
can manifest as socket timeout.
I have a map class that has below code shortened
public HBaseConfiguration c = new HBaseConfiguration();
public static HTable getTable(HBaseConfiguration c) throws IOException {
c.set("hbase.master", CompSpySet.hbasemaster);
HTable table = new HTable(c, "webdata");
return table;
}
map{
the map splits the record into row,column,timestamp,data
then it builds a backUpdate called update
then the map calls the above code
HTable table = getTable(c);
table.commit(update);
}
Your hadoop instance has the new hbase 0.2 jars in its CLASSPATH? Your
not mistakenly pointing at an older hbase?
not sure whats going on this import class it was working about 2 weeks
ago and I have not had any luck in the last 4-5 days sense
I updated to latest trunk and tryed RC 1 but eclipse is not showing
any errors or warring.
Lets try and figure out whats going on Billy,
St.Ack
