Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of zzdtsv@gmail.com designates
 209.85.213.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABFUDMzcTn-59tcLSFvSUxofsFqysuig0YdSLCJ0wD2YUhkFdQ@mail.gmail.com>
References: 
 <6F4660EF6A95604382F58BC9C07FF4BF1811238F6A@P3PW5EX1MB13.EX1.SECURESERVER.NET>
 <84B5E4309B3B9F4ABFF7664C3CD7698302D0DD14@kairo.scch.at>
 <CABFUDMzcTn-59tcLSFvSUxofsFqysuig0YdSLCJ0wD2YUhkFdQ@mail.gmail.com>
From: zizon <zzdtsv@gmail.com>
Date: Fri, 12 Aug 2011 15:42:57 +0800
Message-ID: 
 <CAKTRiEJa5N1rn3b76DKubQd9kQ8VCDkuXBjtyJ40U2H4hB5Yrg@mail.gmail.com>
Subject: Re: autoFlush
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=90e6ba6e89ea0bf25104aa4a11db

--90e6ba6e89ea0bf25104aa4a11db
Content-Type: text/plain; charset=UTF-8

or do something like this:

HTablePool pool = new HTablePool(config, maxSize, new HTableFactory() {
@Override
public HTableInterface createHTableInterface(Configuration config,
 byte[] tableName) {
try {
HTable table= new HTable(config, tableName);
 *table.setAutoFlush(false);*
return table;
} catch (IOException ioe) {
 throw new RuntimeException(ioe);
}
}
 });

pass a user define  HTableInterfaceFactory to instantiate htabl pool

On Fri, Aug 12, 2011 at 3:33 PM, Allan Yan <hailunyan@gmail.com> wrote:

> HTablePool uses HTableInterfaceFactory to return a HTableInterface.
> While HTable implements HTableInterface, it doesn't mean calling
> getTable method will always return HTable. Depends on how your
> HTablePool is instantiated, your HTablePool instance may or may not
> gives you HTable instance when you call getTable. For example, if you
> create HTablePool instance without passing your own
> HTableInterfaceFactory instance, as following:
>
> HTablePool htablePool = new HTablePool(config, 10);
>
> Internally, a HTableFactory is created and used for returning a HTable
> instance whenever the htablePool.getTable() method is called.
>
> However, to make your code bug free, you could check the object type
> first before you cast it , like this:
>
> HTableInterface table = tablePool.getTable(myTable);
> if(table instanceof HTable)
>    ((HTable)table).setAutoFlush(true)
>
>
> On Thu, Aug 11, 2011 at 11:32 PM, Steinmaurer Thomas
> <Thomas.Steinmaurer@scch.at> wrote:
> > Typecast the return value of the table pool to HTable and you shoud be
> > fine. E.g. I'm doing this:
> >
> > ...
> > HTable table = (HTable) tablePool.getTable(this.hbaseTable);
> > table.setAutoFlush(this.hbaseAPIuseAutoFlush);
> > table.setWriteBufferSize(this.hbaseAPIwriteBufferSize);
> > ...
> >
> >
> > lg,
> > Thomas
> >
> > -----Original Message-----
> > From: steve.boyle@connexity.com [mailto:steve.boyle@connexity.com]
> > Sent: Freitag, 12. August 2011 08:01
> > To: user@hbase.apache.org
> > Subject: autoFlush
> >
> > I want to do client-side write-caching to hbase.  I see the setAutoFlush
> > method in HTable.  I do not see that in the HTableInterface that is
> > returned from HTablePool.  Is there something equivalent to setAutoFlush
> > on table instances from HTablePool?
> >
> > Thanks!
> >
>

--90e6ba6e89ea0bf25104aa4a11db--