TRUNK comes with the usual disclaimer: no guarantees that its stable. Whereas with releases, if they are not stable, we'll stop work on TRUNK to fix release problems and try and roll a new one quicIkly. If you're trying to run hbase in a production context, would suggest you use release unless there is an explicit feature you need that is only in TRUNK.
If logging is not working correctly in TRUNK then its going to be hard for us to help you out since you can't pass us detail of sufficient detail (Its broke for you, right)? I was going to look at trying to figure it in a bit.... St.Ack On Tue, Apr 29, 2008 at 11:01 AM, David Alves <[EMAIL PROTECTED]> wrote: > > The NPE problem I'm currently having didn't happen with the released > version but I still got time outs and offline region problems. > So I tryed migrating and have already migrated most of my code to comply > to the new APIs (which are a lot better by the way congrats). Due to > this fact I would like to keep using trunk but will get back to the > released version if you think is better. > > Best Regards > David > > > On Fri, 2008-04-18 at 10:49 -0700, stack wrote: > > It didn't? Wasn't it the same issue of table regions being offlined or > was > > it something else? > > Thanks, > > St.Ack > > > > On Tue, Apr 29, 2008 at 10:28 AM, David Alves < > [EMAIL PROTECTED]> > > wrote: > > > > > Hi Again > > > > > > On another note from the previous email my even though I > followed > > > the > > > faq my ..master...log is showing only one error entry and the .out is > > > showing only INFO entries is this normal? (i'm logging to a different > > > dir that default by altering the relevant property in hbase-env.sh) > > > > > > Regards > > > David Alves > > > > > > > >
