-
InterfaceDescriptionSince 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManagersince 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManagerSince 2.0. Will be removed in 3.0Since 2.0.0 to be removed in 3.0.0. The hope is that by 3.0.0 we will not need this facility as CoreCoprocessors are integated into core.Since 2.0.0 to be removed in 3.0.0. The hope is that by 3.0.0 we will not need this facility as CoreCoprocessors are integated into core.Since 2.0. Will be removed in 3.0only used for
RecoverMetaProcedure
. Should be removed along withRecoverMetaProcedure
.As of release 2.0.0, this will be removed in HBase 3.0.0. For customization, use Coprocessors instead.Since 2.3.0. To be removed in hbase4. Use HBCK2 instead. Remove whenHBaseFsck
is removed.
-
ClassDescriptionsince 2.2.0, to be marked as
InterfaceAudience.Private
in 4.0.0.since 2.2.0, will be removed in 3.0.0, without replacement. Please useBufferedMutator
for batching mutations.since 2.2.0, will be removed in 3.0.0, without replacement. Please useBufferedMutator
for batching mutations.as of 2.4.0. Will be removed in 4.0.0.Since 2.5.0, will be removed in 4.0.0. UseRpcConnectionRegistry
instead.useAdmin
instead.As of release 2.0.0, this will be removed in HBase 3.0.0.As of 2.6.0, replaced byRpcConnectionRegistry
, which is the default connection mechanism as of 3.0.0. Expected to be removed in 4.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterMetrics
instead.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter (see SplitWALManager) which doesn't use this zk-based coordinator.Deprecated in 2.0.0 and will be removed in 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0. useRegionInfoBuilder
to buildRegionInfo
.As of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptorBuilder
to buildHTableDescriptor
.: UseCellComparatorImpl
. Deprecated for hbase 2.0, remove for hbase 3.0.:MetaCellComparator.META_COMPARATOR
to be used. Deprecated for hbase 2.0, remove for hbase 3.0.UseImport.CellImporter
. Will be removed from 3.0 onwardsUseImport.CellReducer
. Will be removed from 3.0 onwardsUseImport.CellSortImporter
. Will be removed from 3.0 onwardsUseImport.CellWritableComparablePartitioner
. Will be removed from 3.0 onwardsUseCellSerialization
. Will be removed from 3.0 onwardsUseCellSortReducer
. Will be removed from 3.0 onwardsAs of release 2.0.0, this will be removed in HBase 3.0.0. UseLoadIncrementalHFiles
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseLoadIncrementalHFiles.LoadQueueItem
instead.UseWALPlayer.WALCellMapper
. Will be removed from 3.0 onwardsDo not use any more.2.3.0 UseGCMultipleMergedRegionsProcedure
.Do not use any more.Do not use any more.Do not use any more.Since 2.3.0, will be removed in 4.0.0. We will not use the procedure wal to store procedure any more.Since 2.0.0. To be removed in 3.0.0.only used forRecoverMetaProcedure
. Should be removed along withRecoverMetaProcedure
.Do not use any more, leave it here only for compatible. The recovery work will be done inServerCrashProcedure
directly, and the initial work for meta table will be done byInitMetaProcedure
.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManager.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionMetrics
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionSplitRestriction
, instead.Keep it here only for compatiblesince 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManagersince 2.5.0 and will be removed in 4.0.0. UseRegionSplitRestriction
, instead.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALRemoteProcedureAs of release 2.0.0, this will be removed in HBase 3.0.0 UseServerMetrics
instead.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManagersince 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter, see SplitWALManagersince 2.2.0, will be removed in 3.0.0. UseBulkLoadHFiles
instead. Please rewrite your code if you rely on methods other than theLoadIncrementalHFiles.run(Map, TableName)
andLoadIncrementalHFiles.run(String, TableName)
, as all the methods other than them will be removed with no replacement.since 2.2.0 and will be removed in 3.0.0. UseBulkLoadHFiles
instead.Will be removed in 3.0.0 without replacement. It should not be a public API as it exposes the protobuf stuff. Users who depend on this class should just copy the code your own code base.This class will become IA.Private in HBase 3.0. Downstream folks shouldn't use it.Since 2.0.6/2.1.3/2.2.0since 2.0.0 and will be removed in 3.0.0. UseLongAdder
instead.For removal in hbase-4.0.0. Use HBCK2 instead.Since 2.0.0. Will be removed in 3.0.0. We've deprecated this tool in hbase-2+ because it destroyed the hbase2 meta table.Since 2.0.0. To be removed in hbase-3.0.0.Not usedsince 2.4.0 and 3.0.0 replaced by procedure-based WAL splitting; see SplitWALManager.Unused
-
ExceptionsDescriptionsince 2.3.0, and will be removed in 4.0.0.Since 2.3.0, will be removed in 4.0.0. Keep here only for rolling upgrading, now we use the new region based procedure store.replaced by
RpcThrottlingException
since hbase-2.0.0.since 0.99.0. UseRowTooBigException
instead.
-
FieldDescriptionAs of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-17886). Use
ServerSideScanMetrics.COUNT_OF_ROWS_FILTERED_KEY_METRIC_NAME
.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-17886). UseServerSideScanMetrics.COUNT_OF_ROWS_SCANNED_KEY_METRIC_NAME
.since 1.0.0. UseScan.setScanMetricsEnabled(boolean)
It is used internally. As of release 2.0.0, this will be removed in HBase 3.0.0.It is used internally. As of release 2.0.0, this will be removed in HBase 3.0.0.It is used internally. As of release 2.0.0, this will be removed in HBase 3.0.0.It is used internally. As of release 2.0.0, this will be removed in HBase 3.0.0.It is used internally. As of release 2.0.0, this will be removed in HBase 3.0.0.since 2.4.0 and in 3.0.0, to be removed in 4.0.0.Since 2.4.0, will be removed in 4.0.0. Please change the meta replicas number by altering meta table, i.e, set a new 'region replication' number and call modifyTable.useHConstants.DEFAULT_ZOOKEEPER_CLIENT_PORT
insteaduseHConstants.DEFAULT_ZOOKEEPER_MAX_CLIENT_CNXNS
insteadsince 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.since 2.3.0, and in 3.0.0 the actually implementation will be removed so config this value will have no effect. The constants itself will be removed in 4.0.0.Since 2.5.0, will be removed in 4.0.0. Please use hbase.client.pause.server.overloaded instead.Since hbase-2.3.0; no replacement as not used any more (internally at least)This config option is deprecated. Will be removed at later releases after 0.96.since 2.4.0 and in 3.0.0, to be removed in 4.0.0, replaced by procedure-based distributed WAL splitter; see SplitWALManager.Since 2.3.0 and 2.2.1. Not used anymore. Instead we look for theHConstants.MERGE_QUALIFIER_PREFIX_STR
prefix.Since 2.3.0 and 2.2.1. Not used anymore. Instead we look for theHConstants.MERGE_QUALIFIER_PREFIX_STR
prefix.the name "META_QOS" is a bit ambiguous, actually only meta region transition can use this priority, and you should not use this directly. Will be removed in 3.0.0.Since 2.4.0, will be removed in 4.0.0. Please change the meta replicas number by altering meta table, i.e, set a new 'region replication' number and call modifyTable.Should not be public since hbase-1.3.0. For internal use only. Move internal to Scanners flagged as special timestamp value never to be returned as timestamp on a Cell.since 3.0.0, will be removed in 4.0.0. DLR has been purged for a long time and region replication has its own 'replay' method.moved it into HBaseInterClusterReplicationEndpointSince 0.99.0. Use builder pattern viaHttpServer.Builder.addEndpoint(URI)
instead.Since 0.99.0. Use builder pattern viaHttpServer.Builder.setAppDir(String)
instead.Since 0.99.0. Use builder pattern viaHttpServer.Builder.addEndpoint(URI)
instead.since 2.3.0 and will be removed in 4.0.0. UseByteBuffAllocator.ALLOCATOR_POOL_ENABLED_KEY
instead.since 2.3.0 and will be removed in 4.0.0. UseByteBuffAllocator.BUFFER_SIZE_KEY
instead.since 2.3.0 and will be removed in 4.0.0. UseByteBuffAllocator.MAX_BUFFER_COUNT_KEY
instead.useBlockCacheFactory.BLOCKCACHE_BLOCKSIZE_KEY
instead.UseCellComparator.getInstance()
instead. Deprecated for hbase 2.0, remove for hbase 3.0.UseMetaCellComparator.META_COMPARATOR
instead. Deprecated for hbase 2.0, remove for hbase 3.0.since 0.90.0since 0.90.0LOG variable would be made private. fix in hbase 3.0since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.3.0 and 3.0.0 to be removed in 4.0.0; replaced bySplitWALManager
.since 2.5.0 and will be removed in 4.0.0. UseSimpleRegionNormalizer.MERGE_MIN_REGION_COUNT_KEY
instead.Since 2.3.0, will be removed in 4.0.0. We do not use this style of procedure wal file name any more.Use hbase-metrics/hbase-metrics-api module interfaces for new metrics. Defining BaseSources for new metric groups (WAL, RPC, etc) is not needed anymore, however, for existingBaseSource
implementations, please use the field named "registry" which is aMetricRegistry
instance together with theHBaseMetrics2HadoopMetricsAdapter
.since 2.4.0 and will be removed in 4.0.0. UseHRegionServer.UNSAFE_RS_HOSTNAME_DISABLE_MASTER_REVERSEDNS_KEY
instead.since 1.3.0. UseMetricsReplicationGlobalSourceSourceImpl.shippedBytesCounter
instead.since 1.3.0. UseMetricsReplicationSourceSourceImpl.shippedBytesKey
instead.Since 2.4.18/2.5.9/2.6.0, will be removed in 4.0.0. Please useConstants.FILTER
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerMetricsBuilder.of(ServerName)
instead.UseSnapshotDescriptionUtils.DEFAULT_MAX_WAIT_TIME
instead.since 2.2.0, will be removed in 3.0.0, with no replacement. End user should not depend on this value.since 2.4.0 and will be removed in 4.0.0. UseDNS.UNSAFE_RS_HOSTNAME_KEY
instead.Since 2.3.0. Make it protected, internal-use only. UseWALEdit.isCompactionMarker(Cell)
Since 2.3.0. Make it protected, internal-use only.Since 2.3.0. Not used.Since 2.3.0. Remove. Not for external use. Not used.Since 2.6.0, will be removed in 4.0.0. We use master local region to store this state.Since 2.6.0, will be removed in 4.0.0. We use master local region to store this state.Since 2.6.0, will be removed in 4.0.0. We use master local region to store this state.Since 2.6.0, will be removed in 4.0.0. We use master local region to store this state.
-
MethodDescriptionDeprecated since 2.2.0, this method will be
InterfaceAudience.Private
use only after 4.0.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0. Tags are are now internal.As of HBase-2.0. Will be removed in HBase-3.0. Tags are are now internal.As of HBase-2.0. Will be removed in HBase-3.0. Tags are are now internal.As of HBase-2.0. Will be removed in HBase-3.0. UseCell.getType()
.As of HBase-2.0. Will be removed in HBase-3.0. UseRawCell.cloneTags()
As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in 3.0.As of release 2.0.0, this will be removed in HBase 3.0.0. UseCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseExtendedCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseExtendedCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseExtendedCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of HBase-2.0. Will be removed in HBase-3.0As of release 2.0.0, this will be removed in HBase 3.0.0. UseRawCell.getTags()
As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0.As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be removed in HBase-3.0As of release 2.0.0, this will be removed in HBase 3.0.0.As of 2.0.0 and will be removed in HBase-3.0.0 UseRawCell.getTag(byte)
As of HBase-2.0. Will be removed in HBase-3.0As of 2.0.0 and will be removed in 3.0.0As of HBase-2.0. Will be removed in 3.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useCellUtil.matchingRows(Cell, byte[])
As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useCellUtil.matchingRows(Cell, Cell)
As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useCellUtil.matchingRows(Cell, Cell)
As of HBase-2.0. Will be removed in HBase-3.0As of 2.0.0 and will be removed in 3.0.0As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be a LimitedPrivate API in HBase-3.0.As of HBase-2.0. Will be a LimitedPrivate API in HBase-3.0.As of 2.0.0 and will be removed in 3.0.0 Instead usePrivateCellUtil.tagsIterator(Cell)
As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be removed in HBase-3.0As of HBase-2.0. Will be removed in HBase-3.0As of 2.0. Will be removed in hbase-3.0since 2.1.1 and will be removed in 4.0.0.since 2.1.1 and will be removed in 4.0.0.As of release 2.0.0. This will be removed in HBase 3.0.0. UseAdmin.addColumnFamily(TableName, ColumnFamilyDescriptor)
.Since 2.5.0. Will be removed in 4.0.0. UseAdmin.balance(BalanceRequest)
instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.balance()
instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.balance(BalanceRequest)
instead.since 2.3.0, will be removed in 3.0.0. UseAdmin.cloneSnapshot(String, TableName)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.unassign(byte[], boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.unassign(byte[], boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-18231). UseAdmin.unassign(byte[], boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.unassign(byte[], boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.compactRegionServer(ServerName)
orAdmin.majorCompactRegionServer(ServerName)
.As of release 2.0.0. This will be removed in HBase 3.0.0. UseAdmin.deleteColumnFamily(TableName, byte[])
}.Since 2.2.0. Will be removed in 3.0.0. UseAdmin.deleteSnapshot(String)
instead.since 2.0 version and will be removed in 3.0 version. UseAdmin.deleteSnapshots(Pattern)
instead.since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(Pattern)
andAdmin.deleteTable(TableName)
since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(java.util.regex.Pattern)
andAdmin.deleteTable(TableName)
since 2.0 version and will be removed in 3.0 version. UseAdmin.deleteTableSnapshots(Pattern, Pattern)
instead.since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(Pattern)
andAdmin.disableTable(org.apache.hadoop.hbase.TableName)
since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(java.util.regex.Pattern)
andAdmin.disableTable(org.apache.hadoop.hbase.TableName)
Since 2.0.0. Will be removed in 3.0.0. UseAdmin.catalogJanitorSwitch(boolean)
} instead.since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(Pattern)
andAdmin.enableTable(org.apache.hadoop.hbase.TableName)
since 2.0 version and will be removed in 3.0 version This is just a trivial helper method without any magic. Consider usingAdmin.listTableDescriptors(java.util.regex.Pattern)
andAdmin.enableTable(org.apache.hadoop.hbase.TableName)
Since 2.0.0. Will be removed in 3.0.0. UseAdmin.execProcedureWithReturn(String, String, Map)
} instead.Since 2.0.0. Will be removed in 3.0.0. No longer needed now you get a Future on an operation.Since 2.0.0. Will be removed in 3.0.0. No longer needed now you get a Future on an operation.since 2.0 version and will be removed in 3.0 version. useAdmin.getClusterMetrics()
since 2.0 version and will be removed in 3.0 version. useAdmin.getMasterCoprocessorNames()
As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-17980). UseAdmin.getRegions(ServerName sn)
.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.getQuota(QuotaFilter)
.since 2.4.0 and will be removed in 4.0.0. UseAdmin.getLogEntries(Set, String, ServerType, int, Map)
instead.since 2.0 version and will be removed in 3.0 version. UseAdmin.getDescriptor(TableName)
.since 2.0 version and will be removed in 3.0 version. useAdmin.listTableDescriptors(List)
since 2.0 version and will be removed in 3.0 version. useAdmin.listTableDescriptors(List)
As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-17980). UseAdmin.getRegions(TableName)
.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.isSplitEnabled()
orAdmin.isMergeEnabled()
instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.isTableAvailable(TableName)
since 2.0 version and will be removed in 3.0 version. UseAdmin.listSnapshots(Pattern)
instead.since 2.0 version and will be removed in 3.0 version. useAdmin.listTableDescriptorsByNamespace(byte[])
since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableNames(Pattern)
instead.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableNames(Pattern, boolean)
instead.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableDescriptors()
.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableDescriptors(Pattern)
instead.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableDescriptors(Pattern, boolean)
.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableDescriptors(java.util.regex.Pattern)
.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableDescriptors(java.util.regex.Pattern, boolean)
.since 2.0 version and will be removed in 3.0 version. UseAdmin.listTableSnapshots(Pattern, Pattern)
instead.Since 2.0. Will be removed in 3.0. UseAdmin.mergeRegionsAsync(byte[], byte[], boolean)
instead.since 2.3.0 and will be removed in 4.0.0. Multi-region merge feature is now supported. UseAdmin.mergeRegionsAsync(byte[][], boolean)
instead.As of release 2.0.0. This will be removed in HBase 3.0.0. UseAdmin.modifyColumnFamily(TableName, ColumnFamilyDescriptor)
.since 2.0 version and will be removed in 3.0 version. useAdmin.modifyTable(TableDescriptor)
since 2.0 version and will be removed in 3.0 version. useAdmin.modifyTableAsync(TableDescriptor, boolean)
since 2.2.0 and will be removed in 4.0.0. UseAdmin.move(byte[], ServerName)
instead. And if you want to move the region to a random server, please useAdmin.move(byte[])
.since 2.3.0, will be removed in 3.0.0. UseAdmin.restoreSnapshot(String)
instead.since 2.3.0, will be removed in 3.0.0. UseAdmin.restoreSnapshot(String, boolean)
instead.since 2.3.0, will be removed in 3.0.0. The implementation does not take care of the failsafe property, so do not use it any more.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.runCatalogJanitor()
} instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.balancerSwitch(boolean, boolean)
instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.cleanerChoreSwitch(boolean)
} instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.normalizerSwitch(boolean)
} instead.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.splitSwitch(boolean, boolean)
orAdmin.mergeSwitch(boolean, boolean)
instead.since 2.3.0, will be removed in 3.0.0. UseAdmin.snapshot(String, TableName)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.splitRegionAsync(byte[], byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAdmin.splitRegionAsync(byte[], byte[])
.Since 2.0.0. Will be removed in 3.0.0. UseAdmin.snapshotAsync(SnapshotDescription)
instead.since 2.4.0 and will be removed in 4.0.0. UseAdmin.unassign(byte[])
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseAppend.addColumn(byte[], byte[], byte[])
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseAppend(byte[], long, NavigableMap)
insteadsince 2.1.1 and will be removed in 4.0.0.Since 2.5.0. Will be removed in 4.0.0. UseAsyncAdmin.balance(BalanceRequest)
instead.since 2.4.0 and will be removed in 4.0.0. UseAsyncAdmin.getLogEntries(Set, String, ServerType, int, Map)
instead.Since 2.2.0. Will be removed in 3.0.0. UseAsyncAdmin.isTableAvailable(TableName)
since 2.3.0 and will be removed in 4.0.0.UseAsyncAdmin.mergeRegions(List, boolean)
instead.since 2.4.0 and will be removed in 4.0.0. UseAsyncAdmin.unassign(byte[])
instead.Since 2.5.0, will be removed in 4.0.0. Please useAsyncAdminBuilder.setRetryPauseForServerOverloaded(long, TimeUnit)
instead.Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.5.0, will be removed in 4.0.0. Please useAsyncTableBuilder.setRetryPauseForServerOverloaded(long, TimeUnit)
instead.Since 2.3.0, will be removed in 4.0.0. UseBufferedMutatorParams.operationTimeout(int)
this has been deprecated without a replacementthis has been deprecated without a replacementAs of release 2.0.0, this will be removed in HBase 3.0.0. UseDelete.add(Cell)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseDelete(byte[], long, NavigableMap)
insteadsince 2.0.0 and will be removed in 3.0.0since 2.0.0 and will be removed in 3.0.0It is easy to misunderstand with column family's max versions, so useGet.readAllVersions()
instead.It is easy to misunderstand with column family's max versions, so useGet.readVersions(int)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseGet.setTimestamp(long)
insteadSince 2.0. Will be removed in 3.0. UseAdmin.deleteColumnFamily(TableName, byte[])
instead.since 2.0 version and will be removed in 3.0 version. useHBaseAdmin.getTableDescriptor(TableName, Connection, RpcRetryingCallerFactory,RpcControllerFactory,int,int)
As of release 2.0.0, this will be removed in HBase 3.0.0 UseHBaseAdmin.getRegions(ServerName)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseHBaseAdmin.getRegions(TableName)
.Since 2.0. Will be removed in 3.0. UseAdmin.mergeRegionsAsync(byte[], byte[], boolean)
instead.since 2.2.1. Will removed in 3.0.0.UseHTableMultiplexer.put(TableName, List)
instead.UseHTableMultiplexer.put(TableName, Put)
instead.UseHTableMultiplexer.put(TableName, Put)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseRow.COMPARATOR
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. No replacement.As of release 2.0.0, this will be removed in HBase 3.0.0. UseIncrement(byte[], long, NavigableMap)
insteadsince 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0, UseMutableRegionInfo.isSplit()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseRow.COMPARATOR
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseMutation.getTimestamp()
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseMutation(byte[], long, NavigableMap)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UsePut.add(Cell)
andCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UsePut.add(Cell)
andCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UsePut.add(Cell)
andCellBuilder
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UsePut(byte[], long, NavigableMap)
insteadsince 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0, UseRegionInfo.isSplit()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseRegionLoadStats.getMemStoreLoad()
insteadas release of 2.0.0, and it will be removed in 3.0.0, useReplicationAdmin.addPeer(String, ReplicationPeerConfig)
instead.as release of 2.0.0, and it will be removed in 3.0.0, useReplicationAdmin.appendPeerTableCFs(String, Map)
instead.useAdmin.disableReplicationPeer(String)
insteaduseAdmin.disableTableReplication(TableName)
insteaduseAdmin.enableReplicationPeer(String)
insteaduseAdmin.enableTableReplication(TableName)
insteaduseAdmin.getReplicationPeerConfig(String)
insteadas release of 2.0.0, and it will be removed in 3.0.0, useReplicationAdmin.getPeerConfig(String)
instead.useAdmin.listReplicationPeers()
insteaduseAdmin.listReplicatedTableCFs()
insteaduseAdmin.listReplicationPeers()
insteadas release of 2.0.0, and it will be removed in 3.0.0useAdmin.removeReplicationPeer(String)
insteadas release of 2.0.0, and it will be removed in 3.0.0, useReplicationAdmin.removePeerTableCFs(String, Map)
instead.the word 'partial' ambiguous, useResult.mayHaveMoreCellsInRow()
instead. Deprecated since 1.4.0.As of release 2.0.0, this will be removed in HBase 3.0.0. UseRow.COMPARATOR
insteadsince 2.0 version and will be removed in 3.0 version. useRowMutations.add(Mutation)
since 2.0 version and will be removed in 3.0 version. useRowMutations.add(Mutation)
As of release 2.0.0, this will be removed in HBase 3.0.0. UseRow.COMPARATOR
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. No replacementAs of release 2.0.0, this will be removed in HBase 3.0.0. No replacementUseResultScanner.getScanMetrics()
instead. And notice that, please do not use this method andResultScanner.getScanMetrics()
together, the metrics will be messed up.since 2.0.0 and will be removed in 3.0.0. See the comment ofScan.setSmall(boolean)
since 2.0.0 and will be removed in 3.0.0. It is easy to misunderstand with column family's max versions, so useScan.readAllVersions()
instead.since 2.0.0 and will be removed in 3.0.0. It is easy to misunderstand with column family's max versions, so useScan.readVersions(int)
instead.since 2.5.0, will be removed in 4.0.0. The name of this method is considered to be confusing as it does not use aFilter
but uses setting the startRow and stopRow instead. UseScan.setStartStopRowForPrefixScan(byte[])
instead.since 2.0.0 and will be removed in 3.0.0. UseScan.setLimit(int)
andScan.setReadType(ReadType)
instead. And for the one rpc optimization, now we will also fetch data when openScanner, and if the number of rows reaches the limit then we will close the scanner automatically which means we will fall back to one rpc.since 2.0.0 and will be removed in 3.0.0. UseScan.withStartRow(byte[])
instead. This method may change the inclusive of the stop row to keep compatible with the old behavior.since 2.0.0 and will be removed in 3.0.0. UseScan.withStopRow(byte[])
instead. This method may change the inclusive of the stop row to keep compatible with the old behavior.As of release 2.0.0, this will be removed in HBase 3.0.0. UseScan.setTimestamp(long)
insteadsince 2.0.0 and will be removed in 3.0.0. UseSnapshotDescription.getTableName()
orSnapshotDescription.getTableNameAsString()
instead.Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.4.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
Since 2.0.0. Will be removed in 3.0.0. UseTable.checkAndMutate(byte[], byte[])
since 2.0 version and will be removed in 3.0 version. useTable.exists(List)
since 2.0 and will be removed in 3.0 version useTable.getOperationTimeout(TimeUnit)
insteadsince 2.0 and will be removed in 3.0 version useTable.getReadRpcTimeout(TimeUnit)
insteadsince 2.0 version and will be removed in 3.0 version. useTable.getDescriptor()
since 2.0 and will be removed in 3.0 version useTable.getWriteRpcTimeout(TimeUnit)
insteadsince 2.0.0, useTableBuilder.setOperationTimeout(int)
insteadsince 2.0.0, useTableBuilder.setReadRpcTimeout(int)
insteadUse setReadRpcTimeout or setWriteRpcTimeout insteadsince 2.0.0, useTableBuilder.setWriteRpcTimeout(int)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptor.getCoprocessorDescriptors()
insteadsince 2.0.0 and will be removed in 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptorBuilder.setColumnFamily(ColumnFamilyDescriptor)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptorBuilder.setCoprocessor(String)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptorBuilder.setCoprocessor(CoprocessorDescriptor)
insteadAs of release 2.0.0, this will be removed in HBase 3.0.0. UseTableDescriptorBuilder.setCoprocessor(CoprocessorDescriptor)
insteadsince 2.0.0 and will be removed in 3.0.0.used by HTableDescriptor and admin.rb. As of release 2.0.0, this will be removed in HBase 3.0.0.since 2.0.0 and will be removed in 3.0.0.since 2.0.0 and will be removed in 3.0.0.since 2.0.0 and will be removed in 3.0.0.since 2.0.0 and will be removed in 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getBackupMasterNames()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getBackupMasterNames()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-13656). UseClusterStatus.getDeadServerNames()
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getDeadServerNames()
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterMetrics.getLastMajorCompactionTimestamp(byte[])
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterMetrics.getLastMajorCompactionTimestamp(TableName)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getLiveServerMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getMasterName()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getMasterCoprocessorNames()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterMetrics.getRegionCount()
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterMetrics.getRequestCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getLiveServerMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseClusterStatus.getLiveServerMetrics()
.As of release 2.0.0, this will be removed in HBase 3.0.0As of release 2.0.0, this will be removed in HBase 3.0.0 No flag in 2.0Since 2.1. Will be removed in 3.0.Since 2.1. Will be removed in 3.0.Since 2.1. Will be removed in 3.0.in 2.4.0. replaced by postUnassign(ctx, regionInfo). removed in hbase 3. until then safe to either leave implementation here or move it to the new method. default impl of that method calls this one.Since 2.1. Will be removed in 3.0.Since 2.1. Will be removed in 3.0.Since 2.1. Will be removed in 3.0.in 2.4.0. replaced by preUnassign(ctx, regionInfo). removed in hbase 3. until then safe to either leave implementation here or move it to the new method. default impl of that method calls this one.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.postAppend(ObserverContext, Append, Result, WALEdit)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.postDelete(ObserverContext, Delete, WALEdit)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.postIncrement(ObserverContext, Increment, Result, WALEdit)
instead.Since 2.0 with out any replacement and will be removed in 3.0since 2.2.0 and will be removedin 4.0.0. UseRegionObserver.postIncrementBeforeWAL(ObserverContext, Mutation, List)
orRegionObserver.postAppendBeforeWAL(ObserverContext, Mutation, List)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.postPut(ObserverContext, Put, WALEdit)
instead.For Phoenix only, StoreFileReader is not a stable interface.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.preAppend(ObserverContext, Append, WALEdit)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.preBatchMutate(ObserverContext, MiniBatchOperationInProgress)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.preDelete(ObserverContext, Delete, WALEdit)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.preIncrement(ObserverContext, Increment, WALEdit)
instead.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.preBatchMutate(ObserverContext, MiniBatchOperationInProgress)
instead.Since hbase-2.0.0. No replacement. To be removed in hbase-3.0.0 and replaced with something that doesn't expose IntefaceAudience.Private classes.since 2.5.0 and will be removed in 4.0.0. UseRegionObserver.prePut(ObserverContext, Put, WALEdit)
instead.For Phoenix only, StoreFileReader is not a stable interface.As of release 2.0.0 with out any replacement. This is maintained for internal usage by AccessController. Do not use these hooks in custom co-processors.As of release 2.0.0 with out any replacement. This is maintained for internal usage by AccessController. Do not use these hooks in custom co-processors.Since hbase-2.0.0. To be replaced with an alternative that does not expose InterfaceAudience classes such as WALKey and WALEdit. Will be removed in hbase-3.0.0.Since hbase-2.0.0. To be replaced with an alternative that does not expose InterfaceAudience classes such as WALKey and WALEdit. Will be removed in hbase-3.0.0.Since 2.0.0. Will be removed in 3.0.0. UseCompareFilter.compareFamily(CompareOperator, ByteArrayComparable, Cell)
Since 2.0.0. Will be removed in 3.0.0. UseCompareFilter.compareQualifier(CompareOperator, ByteArrayComparable, Cell)
Since 2.0.0. Will be removed in 3.0.0. UseCompareFilter.compareRow(CompareOperator, ByteArrayComparable, Cell)
Since 2.0.0. Will be removed in 3.0.0. UseCompareFilter.compareValue(CompareOperator, ByteArrayComparable, Cell)
since 2.0.0. Will be removed in 3.0.0. UseCompareFilter.getCompareOperator()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. Instead use filterCell(Cell)As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useFilter.filterRowKey(Cell)
As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useFilterBase.filterRowKey(Cell)
Since 2.0since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueFilter.getCompareOperator()
instead.it will be removed in 3.0.0. UseConfiguration.addDeprecation(String, String)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-13655). UseHColumnDescriptor.getCompactionCompressionType()
.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-13655). UseHColumnDescriptor.getCompressionType()
.since 2.0.0 and will be removed in 3.0.0. UseColumnFamilyDescriptorBuilder.isLegalColumnFamilyName(byte[])
instead.Since 2.0 and will be removed in 3.0 with out any replacement. Caching data in on heap Cache, when there are both on heap LRU Cache and Bucket Cache will no longer be supported from 2.0.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.areAdjacent(RegionInfo, RegionInfo)
.As of release 2.0.0, this will be removed in HBase 3.0.0 Use toRegionInfo(org.apache.hadoop.hbase.client.RegionInfo) in org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.As of release 2.0.0, this will be removed in HBase 3.0.0 Use toRegionInfo(HBaseProtos.RegionInfo) in org.apache.hadoop.hbase.shaded.protobuf.ProtobufUtil.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.createRegionName(TableName, byte[], byte[], boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.createRegionName(TableName, byte[], byte[], int, boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.createRegionName(TableName, byte[], long, boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.createRegionName(TableName, byte[], long, int, boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.createRegionName(TableName, byte[], String, boolean)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.encodeRegionName(byte[])
.Use Region#getCellComparator(). deprecated for hbase 2.0, remove for hbase 3.0As of release 2.0.0, this will be removed in HBase 3.0.0 Use RegionInfoDisplay#getDescriptiveNameFromRegionStateForDisplay(RegionState, Configuration) over in hbase-server module.As of release 2.0.0, this will be removed in HBase 3.0.0 Use RegionInfoDisplay#getEndKeyForDisplay(RegionInfo, Configuration) over in hbase-server module.As of release 2.0.0, this will be removed in HBase 3.0.0 Use RegionInfoDisplay#getRegionNameAsStringForDisplay(RegionInfo, Configuration) over in hbase-server module.As of release 2.0.0, this will be removed in HBase 3.0.0 Use RegionInfoDisplay#getRegionNameForDisplay(RegionInfo, Configuration) over in hbase-server module.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.getShortNameToLog(List)
)}.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.getShortNameToLog(RegionInfo...)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.getStartKey(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 Use RegionInfoDisplay#getStartKeyForDisplay(RegionInfo, Configuration) over in hbase-server module.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.getTable(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.isEncodedRegionName(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseDelimitedFrom(byte[], int, int)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseFrom(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseFrom(byte[], int, int)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseFrom(DataInputStream)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseFromOrNull(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseFromOrNull(byte[], int, int)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.parseRegionName(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.prettyPrint(String)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.toByteArray(RegionInfo)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.toDelimitedByteArray(RegionInfo)
.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionInfo.toDelimitedByteArray(RegionInfo...)
.Since 2.0.0. Will remove in 3.0.0. UseHRegionLocation.getRegion()
} instead.since 2.0.0 and will be removed in 3.0.0.since 2.0.0 and will be removed in 3.0.0. UseHTableDescriptor.getColumnFamilies()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-18008). UseHTableDescriptor.getColumnFamilyNames()
.since 2.0.0 and will be removed in 3.0.0. UseHTableDescriptor.getColumnFamily(byte[])
instead.since 0.94.1As of release 2.0.0, this will be removed in HBase 3.0.0. UseHTableDescriptor.hasRegionMemStoreReplication()
insteadsince 0.94.1since 0.94.1As of release 2.0.0, this will be removed in HBase 3.0.0. UseHTableDescriptor.setRegionMemStoreReplication(boolean)
insteadSince 0.99.0. UseHttpServer.Builder.addEndpoint(URI)
instead.Since 0.99.0. UseHttpServer.Builder.setAppDir(String)
instead.Since 0.99.0. UseHttpServer.Builder.addEndpoint(URI)
instead.Since 0.99.0UseInfoServer.addUnprivilegedServlet(String, String, Class)
orInfoServer.addPrivilegedServlet(String, String, Class)
instead of this method which does not state outwardly what kind of authz rules will be applied to this servlet.Since 0.99.0Since hbase-2.0.0. Will be removed in hbase-3.0.0.Since hbase-2.0.0Since hbase-2.0.0since 0.98.5. UseImmutableBytesWritable.getLength()
insteadWritables are going away. Use the pb serialization methods instead. Remove in a release after 0.96 goes out. This is here only to migrate old Reference files written with Writables before 0.96.This is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0. UseTimeRange.withinTimeRange(long)
insteadAs of release 1.3, this will be removed in HBase 3.0As of release 2.0, this will be removed in HBase 3.0Since 0.99.2;As of release 2.0.0, this will be removed in HBase 3.0.0. Instead useKeyValue.write(OutputStream, boolean)
without any replacement.since 0.98.9since 2.0.0 and will be removed in 3.0.0. UseHFileOutputFormat2.TableInfo.getTableDescriptor()
instead.as of release 2.3.0. Will be removed on 4.0.0. Please use main method instead.since 1.3.0 and will be removed in 3.0.0. UseTableMapReduceUtil.addDependencyJars(Job)
instead.Since 1.2.0 and will be removed in 3.0.0. UseTableMapReduceUtil.initCredentialsForCluster(Job, Configuration)
instead.since 2.4.0 and 2.3.2, will be removed in 4.0.0since 2.4.0 and 2.3.2, will be removed in 4.0.0 UseTableRecordReaderImpl.updateCounters(ScanMetrics, long, TaskAttemptContext, long)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseTableSnapshotInputFormat.TableSnapshotRegionSplit.getRegion()
since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.since 2.4.0, will be removed in 3.0.0.With proc-v2, we can record the crash server with procedure store, so do not need to scan the wal directory to find out the splitting wal directory any more. Leave it here only becauseRecoverMetaProcedure
(which is also deprecated) uses it.only used forRecoverMetaProcedure
. Should be removed along withRecoverMetaProcedure
.only used forRecoverMetaProcedure
. Should be removed along withRecoverMetaProcedure
.only used forRecoverMetaProcedure
. Should be removed along withRecoverMetaProcedure
.Since 2.0.0. To be removed in hbase-3.0.0.Since 2.0.0. Remove in hbase-3.0.0.UseAddress.getHostName()
insteadsince 2.3.0, will be removed in 4.0.0 along withWALProcedureStore
. As now we will store the procedure data in a master local region, and master itself will deal with the lease recovery of the region.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getCompletedSequenceId()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getCompactedCellCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getFilteredReadRequestCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getLastMajorCompactionTimestamp()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getMemStoreSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getRegionName()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getReadRequestCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionMetrics.getRequestCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreFileRootLevelIndexSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreSequenceId()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreFileRootLevelIndexSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 ((HBASE-3935)). UseRegionLoad.getStoreFileRootLevelIndexSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreFileCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreFileSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getUncompressedStoreFileSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getCompactingCellCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getBloomFilterSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getStoreFileUncompressedDataIndexSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseRegionLoad.getWriteRequestCount()
instead.org.apache.hadoop.hbase.regionserver.FifoRpcSchedulerFactory.create(Configuration, PriorityFunction) For tests only; to be removed.use HRegion.createHRegion() or HRegion.openHRegion()since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.since 2.4.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. For customization, use Coprocessors instead.As of release 2.0.0, this will be removed in HBase 3.0.0. For customization, use Coprocessors instead.As of release 2.0.0, this will be removed in HBase 3.0.0. For customization, use Coprocessors instead.Since 2.0 with out any replacement and will be removed in 3.0Since hbase-2.0.0. No replacement. To be removed in hbase-3.0.0 and replaced with something that doesn't expose IntefaceAudience.Private classes.In hbase-2.0.0. Will be removed in hbase-3.0.0. Added explicitly for a single Coprocessor for its needs only. Will be removed.Since hbase-2.0.0. No replacement. To be removed in hbase-3.0.0 and replaced with something that doesn't expose IntefaceAudience.Private classes.since 1.0.0.will be removed in 3.0will be removed in 3.0will be removed in 3.0will be removed in 3.0since 1.0.0.Since 2.0.0. Will be removed in 3.0.0.since 2.0.0 and will be removed in 3.0.0. Do not write further code which depends on this call. Instead use getStoreFileScanner() which uses the StoreFileScanner class/interface which is the preferred way to scan a store with higher level concepts.since 2.0.0 and will be removed in 3.0.0. Do not write further code which depends on this call. Instead use getStoreFileScanner() which uses the StoreFileScanner class/interface which is the preferred way to scan a store with higher level concepts. should we cache the blocks? use pread (for concurrent small readers) is scanner being used for compaction?Since 2.0.0. Will be removed in 3.0.0.Since 2.0.0. Removed in 3.0.0.Since hbase-2.0.0. Will be removed in 3.0.0.Since 2.0.0. Will be removed in 3.0.0.since 2.1.0 and will be removed in 4.0.0. UseReplicationPeer.registerPeerConfigListener(ReplicationPeerConfigListener)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setBandwidth(long)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setClusterKey(String)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setExcludeNamespaces(Set)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setExcludeTableCFsMap(Map)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setNamespaces(Set)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setReplicateAllUserTables(boolean)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setReplicationEndpointImpl(String)
instead.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder.setTableCFsMap(Map)
instead.Will be removed in HBase 3. UseReplicationPeerConfig.needToReplicate(TableName)
instead.since 2.2.0 and will be removed 4.0.0. UseAdmin.hasUserPermissions(List)
instead.since 2.2.0 and will be removed in 4.0.0. UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.since 2.2.0 and will be removed in 4.0.0. UseAdmin.grant(UserPermission, boolean)
instead.since 2.2.0 and will be removed in 4.0.0. UseAdmin.hasUserPermissions(String, List)
instead.since 2.2.0 and will be removed in 4.0.0. UseAdmin.revoke(UserPermission)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.getUserPermissions(GetUserPermissionsRequest)
instead.UseAdmin.grant(UserPermission, boolean)
instead.UseAdmin.grant(UserPermission, boolean)
instead.UseAdmin.grant(UserPermission, boolean)
instead.UseAdmin.hasUserPermissions(String, List)
instead.UseAdmin.revoke(UserPermission)
instead.UseAdmin.revoke(UserPermission)
instead.UseAdmin.revoke(UserPermission)
instead.Since 2.6.0. In our own code will not call this method any more, customized authentication method should implementSaslClientAuthenticationProvider.createClient(Configuration, InetAddress, String, Token, boolean, Map)
instead. Will be removed in 4.0.0.Since 2.6.0, will be removed in 4.0.0. UseSecurityInfo.getServerPrincipals()
instead.Since 2.0.0.External users should not use this method. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtil
instead.External users should not use this method. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtil
instead.External users should not use this method. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtil
instead.External users should not use this method. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtil
instead.UseVisibilityClient.addLabel(Connection,String)
instead.UseVisibilityClient.addLabels(Connection,String[])
instead.UseVisibilityClient.getAuths(Connection,String)
instead.UseVisibilityClient.listLabels(Connection,String)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getNumberOfRegions()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getMaxHeapSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseServerLoad.getRequestCountPerSecond()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getCoprocessorNames()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getReportTimestamp()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRequestCountPerSecond()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getCoprocessorNames()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseServerLoad.getRequestCount()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0. UseServerLoad.getUsedHeapSize()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 UseServerLoad.getRegionMetrics()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 No flag in 2.0As of release 2.0.0, this will be removed in HBase 3.0.0 No flag in 2.0As of release 2.0.0, this will be removed in HBase 3.0.0 No flag in 2.0As of release 2.0.0, this will be removed in HBase 3.0.0 No flag in 2.0DONT use this pb object since the byte array backed may be modified in rpc layerSince 2.0. UseServerName.getAddress()
instead.Since 2.0. This is for internal use only.Since 2.0. UseServerName.valueOf(String, int, long)
instead.Since 2.0. UseServerName.valueOf(String, long)
instead.Since 2.0. UseServerName.getAddress()
Since 2.0. Use instance of ServerName to pull out start code.Since 2.5.0, will be removed in 4.0.0. UseServerName.getStartCode()
instead.Since 2.0. UseServerName.valueOf(String)
Since 2.0. UseServerName.valueOf(String)
Since 2.0. UseServerName.valueOf(String)
as of release 2.3.0. UseBulkLoadHFiles
instead.as of release 2.3.0. UseBulkLoadHFiles
instead.since 2.0.0 and will be removed in 3.0.0. UseBytes.binarySearch(byte[][], byte[], int, int)
instead.since 2.0.0 and will be removed in 3.0.0. UseBytes.binarySearch(Cell[], Cell, CellComparator)
instead.since 2.0.0 and will be removed in 3.0.0. UseBytes.getLength()
instead.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.since 0.98.12. UseBytes.readAsVLong(byte[],int)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.As of release 2.0.0, this will be removed in HBase 3.0.0.For compatibility, will be removed in 4.0.0.Since 2.3.0. For removal in hbase4. Use ProgressReporter override instead.Since 2.3.0. Will be removed in hbase4. UsedFSUtils.getTableStoreFilePathMap(FileSystem, Path, PathFilter, ExecutorService, ProgressReporter)
Since 2.0.0. To be removed in hbase-3.0.0.Since 2.0.0. To be removed in hbase-3.0.0.deparcated since hbase 2.1.0Since version 1.2.0. Removing because not used and exposes subtle internal workings. UseWAL.getEarliestMemStoreSeqNum(byte[], byte[])
Since 2.3.0. Do not expose. Make protected.deparcated since hbase 2.1.0Only for compatibility, will be removed in 4.0.0.since 2.4.0, will be removed in 3.0.0.UnusedUnusedUnused
-
ConstructorDescriptionsince 2.0.0 and will be removed in 3.0.0. Use
new Scan().withStartRow(startRow)
instead.since 2.0.0 and will be removed in 3.0.0. Usenew Scan().withStartRow(startRow).withStopRow(stopRow)
instead.since 2.0.0 and will be removed in 3.0.0. Usenew Scan().withStartRow(startRow).setFilter(filter)
instead.since 2.0.0 and will be removed in 3.0.0. Use the version with the TableName instance instead.since 2.0.0 and will be removed in 3.0.0. Use the version with the TableName instance instead.since 2.0.0 and will be removed in 3.0.0. Use the version with the TableName instance instead.since 2.0.0 and will be removed in 3.0.0. Use the version with the TableName instance instead.since 2.3.0 and will be removed in 4.0.0. UseSnapshotDescription(String, TableName, SnapshotType, String, long, int, Map)
As of release 2.0.0, this will be removed in HBase 3.0.0Since 2.0.0. Will be removed in 3.0.0. Use other constructor.Since 2.0.0. Will be removed in 3.0.0. UseDependentColumnFilter(byte[], byte[], boolean, CompareOperator, ByteArrayComparable)
instead.Since 2.0.0. Will be removed in 3.0.0. UseFamilyFilter(CompareOperator, ByteArrayComparable)
Since 2.0.0. Will be removed in 3.0.0. UseQualifierFilter(CompareOperator, ByteArrayComparable)
instead.Since 2.0.0. Will remove in 3.0.0. UseRowFilter(CompareOperator, ByteArrayComparable)
} instead.Since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueExcludeFilter(byte[], byte[], CompareOperator, ByteArrayComparable)
Since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueExcludeFilter(byte[], byte[], CompareOperator, ByteArrayComparable, boolean, boolean)
Since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueFilter(byte[], byte[], CompareOperator, byte[])
instead.Since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueFilter(byte[], byte[], CompareOperator, ByteArrayComparable)
instead.Since 2.0.0. Will be removed in 3.0.0. UseSingleColumnValueFilter(byte[], byte[], CompareOperator, ByteArrayComparable, boolean, boolean)
instead.Since 2.0.0. Will be removed in 3.0.0. UseValueFilter(CompareOperator, ByteArrayComparable)
since 0.90.0. Please useHBaseConfiguration.create()
instead.since 0.90.0. Please useHBaseConfiguration.create(Configuration)
instead.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-18433). UseColumnFamilyDescriptorBuilder.of(byte[])
.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-18433). UseColumnFamilyDescriptorBuilder.of(String)
.As of release 2.0.0, this will be removed in HBase 3.0.0 (HBASE-18433). UseColumnFamilyDescriptorBuilder.copy(ColumnFamilyDescriptor)
.Since 0.99.0Since 0.99.0Since 0.99.0Since 0.99.0Since 0.99.0need by pb serializationThis is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0.This is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0.This is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0.This is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0.This is made @InterfaceAudience.Private in the 2.0 line and above and may be changed to private or removed in 3.0.since 2.0.0 and will be removed in 3.0.0. Please use#TableRecordWriter(JobConf)
instead. This version does not clean up connections and will leak connections (removed in 2.0).Use other constructors.as release of 2.0.0, and it will be removed in 3.0.0. UseReplicationPeerConfigBuilder
to create new ReplicationPeerConfig.Since 3.0.0, will be removed in 4.0.0. The rsgroup information for a table will be stored in the configuration of a table so this will be removed.As of release 2.0.0, this will be removed in HBase 3.0.0.since 2.0.1 and will be removed in 4.0.0. UseWALEdit(int, boolean)
instead.since 2.0.1 and will be removed in 4.0.0. UseWALEdit(int, boolean)
instead.