-
Deprecated InterfacesInterfaceDescriptionSince 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 3.0.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 4.0.0. The hope was that by 3.0.0 we will not need this facility as CoreCoprocessors are integated into core but we failed, so delay the removal to 4.0.0.Since 2.0.0 to be removed in 4.0.0. The hope was that by 3.0.0 we will not need this facility as CoreCoprocessors are integated into core but we failed, so delay the removal to 4.0.0.Please stop using this class again, as it is too low level, which is part of the rpc framework for HBase. Will be deleted in 4.0.0.only used for
RecoverMetaProcedure. Should be removed along withRecoverMetaProcedure.Since 2.3.0. To be removed in hbase4. Use HBCK2 instead. Remove whenHBaseFsckis removed.
-
Deprecated ClassesClassDescriptionsince 2.2.0, to be marked as
InterfaceAudience.Privatein 4.0.0.as of 2.4.0. Will be removed in 4.0.0.Since 2.5.0, will be removed in 4.0.0. UseRpcConnectionRegistryinstead.Please stop using this class again, as it is too low level, which is part of the rpc framework for HBase. Will be deleted in 4.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.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.since 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.since 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.since 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.since 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.Do 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.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 inServerCrashProceduredirectly, and the initial work for meta table will be done byInitMetaProcedure.UseAssignReplicationQueuesProcedureinstead, kept only for keeping compatibility.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 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.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.since 3.0.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 3.0.0, will be removed in 4.0.0. Now we will not use this operation to apply edits at secondary replica side.since 3.0.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 SplitWALRemoteProcedureKeep it here only for tests, usingAdmininstead.Keep it here only for compatibility with old client, all the logics have been moved into core of HBase.Keep it here only for compatibility withRSGroupAdminClient, usingMasterRpcServicesinstead.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 3.0.0, will be removed in 4.0.0. UseTestingHBaseClusterinstead.For removal in hbase-4.0.0. Use HBCK2 instead.Not usedsince 2.4.0 and 3.0.0 replaced by procedure-based WAL splitting; see SplitWALManager.Unused
-
Deprecated ExceptionsExceptionsDescriptionsince 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.since 0.99.0. Use
RowTooBigExceptioninstead.
-
Deprecated FieldsFieldDescriptionSince 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.namespace table has been folded into the ns family in meta table, do not use this any more.namespace table has been folded into the ns family in meta table, do not use this any more.namespace table has been folded into the ns family in meta table, do not use this any more.since 3.0.0 and will be removed in 4.0.0. We have folded the data in namespace table into meta table, so do not use it any more.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.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.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)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 the
HConstants.MERGE_QUALIFIER_PREFIX_STRprefix.Since 2.3.0 and 2.2.1. Not used anymore. Instead we look for theHConstants.MERGE_QUALIFIER_PREFIX_STRprefix.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.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.since 3.0.0. Will be removed in 4.0.0. Moved it into HBaseInterClusterReplicationEndpoint.Since 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_KEYinstead.since 2.3.0 and will be removed in 4.0.0. UseByteBuffAllocator.BUFFER_SIZE_KEYinstead.since 2.3.0 and will be removed in 4.0.0. UseByteBuffAllocator.MAX_BUFFER_COUNT_KEYinstead.useBlockCacheFactory.BLOCKCACHE_BLOCKSIZE_KEYinstead.Since 3.0.0, will be removed in 4.0.0. UseCopyTable.peerUriinstead.since 0.90.0since 0.90.0Since 3.0.0, will be removed in 4.0.0 UseSyncTable.SOURCE_URI_CONF_KEYinstead.Since 3.0.0, will be removed in 4.0.0 UseSyncTable.sourceUriinstead.Since 3.0.0, will be removed in 4.0.0 UseSyncTable.TARGET_URI_CONF_KEYinstead.Since 3.0.0, will be removed in 4.0.0 UseSyncTable.targetUriinstead.Since 3.0.0, will be removed in 4.0.0. You do not need to use this way for specifying configurations any more, you can specify any configuration with the connection uri's queries specified by theTableOutputFormat.OUTPUT_CLUSTERparameter.Since 3.0.0, will be removed in 4.0.0. UseTableOutputFormat.OUTPUT_CLUSTERto specify the peer cluster instead.Since 3.0.0, will be removed in 4.0.0. You do not need to use this way for specifying configurations any more, you can specify any configuration with the connection uri's queries specified by theTableOutputFormat.OUTPUT_CLUSTERparameter.Since 2.5.9, 2.6.1 and 2.7.0, will be removed in 4.0.0. Does not take effect from long ago, see HBASE-6044.Since 2.5.9, 2.6.1 and 2.7.0, will be removed in 4.0.0. Does not take effect from long ago, see HBASE-6044.since 3.0.0, will be removed in 4.0.0. In the new implementation, as the base load balancer will always be the rs group based one, you should just useHConstants.HBASE_MASTER_LOADBALANCER_CLASSto config the per group load balancer.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_KEYinstead.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 existingBaseSourceimplementations, please use the field named "registry" which is aMetricRegistryinstance together with theHBaseMetrics2HadoopMetricsAdapter.Useless after switching to OpenTelemetrysince 2.4.0 and will be removed in 4.0.0. UseHRegionServer.UNSAFE_RS_HOSTNAME_DISABLE_MASTER_REVERSEDNS_KEYinstead.Since 2.4.18/2.5.9/2.6.0, will be removed in 4.0.0. Please useConstants.FILTERinstead.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.since 3.0.0 and will be removed in 4.0.0. We have folded the data in namespace table into meta table, so do not use it any more.since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will b removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 2.4.0 and will be removed in 4.0.0. UseDNS.UNSAFE_RS_HOSTNAME_KEYinstead.Since 3.0.0, leave here only for implementing compatibility code.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.
-
Deprecated MethodsMethodDescriptionDeprecated since 2.2.0, this method will be
InterfaceAudience.Privateuse only after 4.0.0.Since 3.0.0, will be removed in 4.0.0. Tags are now internal only, you should not try to check it through theCellinterface.since 2.1.1 and will be removed in 4.0.0.since 2.1.1 and will be removed in 4.0.0.Since 2.5.0. Will be removed in 4.0.0. UseAdmin.balance(BalanceRequest)instead.since 3.0.0, will removed in 4.0.0. This is too low level, please stop using it any more. Use the coprocessorService methods inAsyncAdmininstead.since 3.0.0, will removed in 4.0.0. This is too low level, please stop using it any more. Use the coprocessorService methods inAsyncAdmininstead.since 2.4.0 and will be removed in 4.0.0. UseAdmin.getLogEntries(Set, String, ServerType, int, Map)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.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.4.0 and will be removed in 4.0.0. UseAdmin.unassign(byte[])instead.since 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.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 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 3.0.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 3.0.0, will be removed in 4.0.0. Please set this through theBufferedMutatorParams.Since 3.0.0, will be removed in 4.0.0. Please set this through theBufferedMutatorParams.Since 3.0.0, will be removed in 4.0.0. You can not set it any more as the implementation has to use too many internal stuffs in HBase.Since 3.0.0-alpha-2, will be removed in 4.0.0. You can not set it anymore. BufferedMutator will use Connection's ExecutorService.Since 3.0.0, will be removed in 4.0.0. We use a common timer in the whole client implementation so you can not set it any more.Since 3.0.0, will be removed in 4.0.0. You can not set it any more as the implementation has to use too many internal stuffs in HBase.Since 2.3.0, will be removed in 4.0.0. UseBufferedMutatorParams.operationTimeout(int)Since 3.0.0-alpha-2, will be removed in 4.0.0. You can not set it anymore. BufferedMutator will use Connection's ExecutorService.Since 3.0.0, will be removed in 4.0.0. We use a common timer in the whole client implementation so you can not set it any more.since 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.since 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.Since 3.0.0, will be removed in 4.0.0. After building sync client upon async client, the implementation is always 'async prefetch', so this flag is useless now.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 aFilterbut uses setting the startRow and stopRow instead. UseScan.setStartStopRowForPrefixScan(byte[])instead.org.apache.hadoop.hbase.client.Table.batchCallback(List<? extends Row>, Object[], Batch.Callback<R>) since 3.0.0, will removed in 4.0.0. Please use the batch related methods inAsyncTabledirectly if you want to use callback. We reuse the callback for coprocessor here, and the problem is that for batch operation, theAsyncTabledoes not tell us the region, so in this method we need an extra locating after we get the result, which is not good.since 3.0.0, will removed in 4.0.0. The batch call here references the blocking interface for of a protobuf stub, so it is not possible to do it in an asynchronous way, even if now we are building theTableimplementation based on theAsyncTable, which is not good. Use the coprocessorService methods inAsyncTabledirectly instead.since 3.0.0, will removed in 4.0.0. The batch call here references the blocking interface for of a protobuf stub, so it is not possible to do it in an asynchronous way, even if now we are building theTableimplementation based on theAsyncTable, which is not good. Use the coprocessorService methods inAsyncTabledirectly instead.Since 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.Since 3.0.0, will be removed in 4.0.0. For internal test use only, do not use it any more.since 3.0.0, will removed in 4.0.0. This is too low level, please stop using it any more. Use the coprocessorService methods inAsyncTableinstead.since 3.0.0, will removed in 4.0.0. The batch call here references the blocking interface for of a protobuf stub, so it is not possible to do it in an asynchronous way, even if now we are building theTableimplementation based on theAsyncTable, which is not good. Use the coprocessorService methods inAsyncTabledirectly instead.since 3.0.0, will removed in 4.0.0. The batch call here references the blocking interface for of a protobuf stub, so it is not possible to do it in an asynchronous way, even if now we are building theTableimplementation based on theAsyncTable, which is not good. Use the coprocessorService methods inAsyncTabledirectly instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postAppend(ObserverContext, Append, Result, WALEdit)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postDelete(ObserverContext, Delete, WALEdit)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.postIncrement(ObserverContext, Increment, Result, WALEdit)instead.Since 2.0.0, will be removed in 4.0.0. Visibility label feature still use this method, so it can not be removed in 3.0.0since 2.2.0 and will be removedin 4.0.0. UseRegionObserver.postIncrementBeforeWAL(ObserverContext, Mutation, List)orRegionObserver.postAppendBeforeWAL(ObserverContext, Mutation, List)instead.since 3.0.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 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preAppend(ObserverContext, Append, WALEdit)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preBatchMutate(ObserverContext, MiniBatchOperationInProgress)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutate(ObserverContext, CheckAndMutate, CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preCheckAndMutateAfterRowLock(ObserverContext, CheckAndMutate,CheckAndMutateResult)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preDelete(ObserverContext, Delete, WALEdit)instead.since 3.0.0 and will be removed in 4.0.0. UseRegionObserver.preIncrement(ObserverContext, Increment, WALEdit)instead.since 3.0.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-4.0.0 and replaced with something that doesn't expose IntefaceAudience.Private classes. VisibilityController still needs this, need to change the logic there first.since 3.0.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, plan to remove in 4.0.0. 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, plan to remove in 4.0.0. This is maintained for internal usage by AccessController. Do not use these hooks in custom co-processors.In 2.3.0, will be removed in 4.0.0. Only support changing log level on log4j now as HBase only uses log4j. You should do this by your own as it you know which log framework you are using then set the log level to debug is very easy.since 2.7.0, will be removed in 4.0.0. Now we use connection uri to specify the connection info of a cluster. Keep here only for compatibility.since 3.0.0 and will be removed in 4.0.0. Just useAdmin.modifyTable(TableDescriptor)directly as it is synchronous now.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniHBaseCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniHBaseCluster(StartMiniClusterOption)instead.since 2.2.0 and will be removed in 4.0.0. UseHBaseTestingUtility.startMiniHBaseCluster(StartMiniClusterOption)instead.Since 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.0Writables 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.without any replacement.since 0.98.9as of release 2.3.0. Will be removed on 4.0.0. Please use main method instead.Since 3.0.0, will be removed in 4.0.0. UseTableMapReduceUtil.initTableReducerJob(String, Class, Job, Class, URI)instead, where we use the connection uri to specify the target cluster.Since 3.0.0, will be removed in 4.0.0. UseTableMapReduceUtil.initTableReducerJob(String, Class, Job, Class, URI, boolean)instead, where we use the connection uri to specify the target cluster.Since 2.5.9, 2.6.1, 2.7.0, will be removed in 4.0.0. TheserverClassandserverImpldo not take effect any more, just useTableMapReduceUtil.initTableReducerJob(String, Class, Job, Class, String)instead.Since 2.5.9, 2.6.1, 2.7.0, will be removed in 4.0.0. TheserverClassandserverImpldo not take effect any more, just useTableMapReduceUtil.initTableReducerJob(String, Class, Job, Class, String, boolean)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.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.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.Since 3.0.0, will be removed in 4.0.0. UseQuotaRetriever(Configuration, Scan)instead.Since 3.0.0, will be removed in 4.0.0. UseQuotaRetriever(Configuration, Scan)instead.Since 3.0.0, will be removed in 4.0.0. Now we useHRegion.replayWALEntry(WALEntry, CellScanner)for replaying edits at secondary replica side.For tests only; to be removed.use HRegion.createHRegion() or HRegion.openHRegion()Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.Since 3.0.0, will be removed in 4.0.0. Only for keep compatibility for old region replica implementation.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.since 3.0.0 and will be removed in 4.0.0. UseRegion.checkAndMutate(CheckAndMutate)instead.Since 3.0.0, will be removed in 4.0.0. We do not use this method for replaying edits for secondary replicas any more, seeRSRpcServices.replicateToReplica(RpcController, ReplicateWALEntryRequest).Since 3.0.0, will be removed in 4.0.0. Not used any more, put here only for compatibility with old region replica implementation. Now we will usereplicateToReplicamethod instead.since 2.1.0 and will be removed in 4.0.0. UseReplicationPeer.registerPeerConfigListener(ReplicationPeerConfigListener)instead.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.Since 3.0.0, will be removed in 4.0.0. The rsgroup information will be stored in the configuration of a table so this will be removed.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 and will be removed in 4.0.0.External users should not use this method, will be removed in 4.0.0. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtilinstead.External users should not use this method, will be removed in 4.0.0. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtilinstead.External users should not use this method, will be removed in 4.0.0. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtilinstead.External users should not use this method, will be removed in 4.0.0. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtilinstead.External users should not use this method, will be removed in 4.0.0. Please post on the HBase dev mailing list if you need this method. Internal HBase code should useClientTokenUtilinstead.Since 2.5.0, will be removed in 4.0.0. UseServerName.getStartCode()instead.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.3.0. Do not expose. Make protected.Only for compatibility, will be removed in 4.0.0.Since 3.0.0, will be removed in 4.0.0.UnusedUnusedUnused
-
Deprecated ConstructorsConstructorDescriptionsince 2.3.0 and will be removed in 4.0.0. Use
SnapshotDescription(String, TableName, SnapshotType, String, long, int, Map)Since 0.99.0Since 0.99.0Since 0.99.0Since 0.99.0Since 0.99.0need by pb serializationUse other constructors.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.since 3.0.0 and will be removed in 4.0.0since 3.0.0 and will be removed in 4.0.0since 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.