I thought about it. Decided that hdfs-630 would be fixed by the time 0.21 released.
For 0.20.2RC1, let me test with hdfs-630 in place to make sure its still good for the branch. St.Ack On Thu, Nov 12, 2009 at 6:23 AM, Dave Latham <[email protected]> wrote: > So, would it be worth removing the recommendation to use HDFS-630 from the > getting started page? > > Dave > > On Wed, Nov 11, 2009 at 9:51 PM, stack (JIRA) <[email protected]> wrote: > > > > > [ > > > https://issues.apache.org/jira/browse/HBASE-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776860#action_12776860 > ] > > > > stack commented on HBASE-1974: > > ------------------------------ > > > > Also removed: > > > > -import com.sun.corba.se.pept.transport.Connection; from > > HBaseTestingUtility. > > > > Cleaned up HLog to remove params that passed in a forced sync (sync is > done > > up on HRS now). > > > > Otherwise, updated the hadoop libs to today. hdfs-127 has been committed > > to hdfs so we don't need to patch it any more. HDFS-630 seems like it > > breaks things so leaving it out. > > > > > > > > > Update to latest on hadoop 0.21 branch (November11th, 2009) > > > ----------------------------------------------------------- > > > > > > Key: HBASE-1974 > > > URL: https://issues.apache.org/jira/browse/HBASE-1974 > > > Project: Hadoop HBase > > > Issue Type: Task > > > Reporter: stack > > > Fix For: 0.21.0 > > > > > > > > > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > > > >
