Table instead@Deprecated @InterfaceAudience.Private @InterfaceStability.Stable public interface HTableInterface extends Table
HConnection.| Modifier and Type | Method and Description |
|---|---|
Boolean[] |
exists(List<Get> gets)
Deprecated.
Use
Table.existsAll(java.util.List) instead. |
void |
flushCommits()
Deprecated.
as of 1.0.0. Replaced by
BufferedMutator.flush() |
Result |
getRowOrBefore(byte[] row,
byte[] family)
Deprecated.
As of version 0.92 this method is deprecated without
replacement. Since version 0.96+, you can use reversed scan.
getRowOrBefore is used internally to find entries in hbase:meta and makes
various assumptions about the table (which are true for hbase:meta but not
in general) to be efficient.
|
byte[] |
getTableName()
Deprecated.
Use
Table.getName() instead |
long |
getWriteBufferSize()
Deprecated.
as of 1.0.0. Replaced by
BufferedMutator.getWriteBufferSize() |
long |
incrementColumnValue(byte[] row,
byte[] family,
byte[] qualifier,
long amount,
boolean writeToWAL)
Deprecated.
As of release 0.96
(HBASE-9508).
This will be removed in HBase 2.0.0.
Use
Table.incrementColumnValue(byte[], byte[], byte[], long, Durability). |
boolean |
isAutoFlush()
Deprecated.
as of 1.0.0. Replaced by
BufferedMutator |
void |
setAutoFlush(boolean autoFlush)
Deprecated.
in 0.96. When called with setAutoFlush(false), this function also
set clearBufferOnFail to true, which is unexpected but kept for historical reasons.
Replace it with setAutoFlush(false, false) if this is exactly what you want, though
this is the method you want for most cases.
|
void |
setAutoFlush(boolean autoFlush,
boolean clearBufferOnFail)
Deprecated.
in 0.99 since setting clearBufferOnFail is deprecated. Use
setAutoFlush(boolean)} instead. |
void |
setAutoFlushTo(boolean autoFlush)
Deprecated.
in 0.99 since setting clearBufferOnFail is deprecated. Use
setAutoFlush(boolean) instead, or better still, move on to BufferedMutator |
void |
setWriteBufferSize(long writeBufferSize)
Deprecated.
as of 1.0.0. Replaced by
BufferedMutator and
BufferedMutatorParams.writeBufferSize(long) |
append, batch, batch, batchCallback, batchCallback, batchCoprocessorService, batchCoprocessorService, checkAndDelete, checkAndDelete, checkAndMutate, checkAndPut, checkAndPut, close, coprocessorService, coprocessorService, coprocessorService, delete, delete, exists, existsAll, get, get, getConfiguration, getName, getOperationTimeout, getReadRpcTimeout, getRpcTimeout, getScanner, getScanner, getScanner, getTableDescriptor, getWriteRpcTimeout, increment, incrementColumnValue, incrementColumnValue, mutateRow, put, put, setOperationTimeout, setReadRpcTimeout, setRpcTimeout, setWriteRpcTimeout@Deprecated byte[] getTableName()
Table.getName() instead@Deprecated long incrementColumnValue(byte[] row, byte[] family, byte[] qualifier, long amount, boolean writeToWAL) throws IOException
Table.incrementColumnValue(byte[], byte[], byte[], long, Durability).IOException@Deprecated Boolean[] exists(List<Get> gets) throws IOException
Table.existsAll(java.util.List) instead.IOException@Deprecated void setAutoFlush(boolean autoFlush)
autoFlush - Whether or not to enable 'auto-flush'.@Deprecated void setAutoFlush(boolean autoFlush, boolean clearBufferOnFail)
setAutoFlush(boolean)} instead.
When enabled (default), Put operations don't get buffered/delayed
and are immediately executed. Failed operations are not retried. This is
slower but safer.
Turning off #autoFlush means that multiple Puts will be
accepted before any RPC is actually sent to do the write operations. If the
application dies before pending writes get flushed to HBase, data will be
lost.
When you turn #autoFlush off, you should also consider the
#clearBufferOnFail option. By default, asynchronous Put
requests will be retried on failure until successful. However, this can
pollute the writeBuffer and slow down batching performance. Additionally,
you may want to issue a number of Put requests and call
flushCommits() as a barrier. In both use cases, consider setting
clearBufferOnFail to true to erase the buffer after flushCommits()
has been called, regardless of success.
In other words, if you call #setAutoFlush(false); HBase will retry N time for each
flushCommit, including the last one when closing the table. This is NOT recommended,
most of the time you want to call #setAutoFlush(false, true).
autoFlush - Whether or not to enable 'auto-flush'.clearBufferOnFail - Whether to keep Put failures in the writeBuffer. If autoFlush is true, then
the value of this parameter is ignored and clearBufferOnFail is set to true.
Setting clearBufferOnFail to false is deprecated since 0.96.BufferedMutator.flush()@Deprecated void setAutoFlushTo(boolean autoFlush)
setAutoFlush(boolean) instead, or better still, move on to BufferedMutatorclearBufferOnFail.@Deprecated boolean isAutoFlush()
BufferedMutatortrue if 'auto-flush' is enabled (default), meaning
Put operations don't get buffered/delayed and are immediately
executed.@Deprecated void flushCommits() throws IOException
BufferedMutator.flush()Put operations.
This method gets called once automatically for every Put or batch
of Puts (when put(List<Put>) is used) when
isAutoFlush() is true.
IOException - if a remote or network exception occurs.@Deprecated long getWriteBufferSize()
BufferedMutator.getWriteBufferSize()
The default value comes from the configuration parameter
hbase.client.write.buffer.
getWriteBufferSize in interface Table@Deprecated void setWriteBufferSize(long writeBufferSize) throws IOException
BufferedMutator and
BufferedMutatorParams.writeBufferSize(long)If the new size is less than the current amount of data in the write buffer, the buffer gets flushed.
setWriteBufferSize in interface TablewriteBufferSize - The new write buffer size, in bytes.IOException - if a remote or network exception occurs.@Deprecated Result getRowOrBefore(byte[] row, byte[] family) throws IOException
row - A row key.family - Column family to include in the Result.IOException - if a remote or network exception occurs.Copyright © 2007–2019 The Apache Software Foundation. All rights reserved.