Deprecated API
Contents
-
ElementDescriptionsince 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" featurePortable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.since 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" featurePortable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.since 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" feature
-
InterfaceDescriptionsince 5.0 because of renaming purposes. Please use
PersistenceService
instead.since 5.0 UseICacheManager
instead.After 5.0 Jet was merged into core Hazelcast product. Jet became a service of Hazelcast instead of being an instance of its own that encapsulatesHazelcastInstance
. Please useJetService
instead.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.
-
ClassDescriptionsince 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" featuresince 5.0 use
DataPersistenceConfig
since 5.0 usePersistenceConfig
since 4.2since 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" featuresince 5.0, useJetConfig
instead.After 5.0 Jet was merged into core Hazelcast product. Use theHazelcast
class as the entry point.Since 5.1,Capacity
should be used instead.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.since 5.4, "User Code Deployment" is replaced by the "User Code Namespaces" feature
-
FieldDescriptionsince 4.0. Use
ClientProperty.METRICS_ENABLED
("hazelcast.client.metrics.enabled"
) instead.since 4.0. UseClientProperty.METRICS_COLLECTION_FREQUENCY
("hazelcast.client.metrics.collection.frequency"
) instead.
-
MethodDescriptionSince 5.0, the method is unusedSince 5.0, the method is unusedsince 5.0 Use
Cluster.getPersistenceService()
instead.Supported only for members of the cluster, clients will throw a
UnsupportedOperationException
.since 5.0 useConfig.setPersistenceConfig(PersistenceConfig)
since 4.2since 4.2useMerkleTreeConfig.getEnabled()
instead.Since 4.1 multiple persistent memory directories are supported. Please usePersistentMemoryConfig.getDirectoryConfigs()
instead.Since 5.2, useNativeMemoryConfig.getCapacity()
instead.Since 4.1 multiple persistent memory directories are supported. Please useNativeMemoryConfig.setPersistentMemoryConfig(PersistentMemoryConfig)
orPersistentMemoryConfig.addDirectoryConfig(PersistentMemoryDirectoryConfig)
instead.Since 5.2, useNativeMemoryConfig.setCapacity(Capacity)
instead.since 4.2since 4.2Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.since 5.0 UsePersistenceService.isBackupEnabled()
instead.The fields fromInstanceConfig
class were moved toJetConfig
class. Get the fields directly fromJetConfig
.The fields fromInstanceConfig
class were moved toJetConfig
class. Set the fields directly onJetConfig
.UsehazelcastInstance().getJet()
instead.since 5.0 Please useHazelcast.bootstrappedInstance()
and then getJetService
from the createdHazelcastInstance
by usingHazelcastInstance.getJet()
}.since 5.0 UseHazelcastClient.newHazelcastClient()
and then getJetService
from the createdHazelcastInstance
client by usingHazelcastInstance.getJet()
}.since 5.0 UseHazelcastClient.newHazelcastClient(ClientConfig)
and then getJetService
from the createdHazelcastInstance
client by usingHazelcastInstance.getJet()
}.since 5.0 UseHazelcastClient.newHazelcastFailoverClient()
and then getJetService
from the createdHazelcastInstance
client by usingHazelcastInstance.getJet()
}.since 5.0 UseHazelcastClient.newHazelcastFailoverClient(ClientFailoverConfig)
and then getJetService
from the createdHazelcastInstance
client by usingHazelcastInstance.getJet()
}.since 5.0 Please useHazelcast.newHazelcastInstance()
and then getJetService
from the createdHazelcastInstance
by usingHazelcastInstance.getJet()
}.since 5.0 UseHazelcast.newHazelcastInstance(Config)
and then getJetService
from the createdHazelcastInstance
by usingHazelcastInstance.getJet()
}.since 5.0 UseICacheManager.getCache(String)
instead.since 5.0 UseHazelcastInstance.getCacheManager()
instead.since 5.0 UseHazelcastInstance.getCluster()
instead.since 5.0 Because we first access toHazelcastInstance
and thenJetService
from the product's entry point -Hazelcast
-, we don't need to this back reference anymore. This class made sense when the entry point wasJet
.since 5.0 UseHazelcastInstance.getList(String)
instead.since 5.0 UseHazelcastInstance.getMap(String)
instead.since 5.0 UseHazelcastInstance.getName()
instead.since 5.0 UseHazelcastInstance.getReliableTopic(String)
instead.since 5.0 UseHazelcastInstance.getReplicatedMap(String)
instead.since 5.0 UseHazelcastInstance.getSql()
instead.since 5.0 UseHazelcastInstance.shutdown()
instead.UseFileSources.files(java.lang.String)
. Will be removed in Jet 5.0.UseFileSources.files(java.lang.String)
. Will be removed in Jet 5.0.UseFileSources.files(java.lang.String)
. Will be removed in Jet 5.0.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.This is a leftover from an earlier development cycle of the Pipeline API. UseGroupAggregateBuilder1.build(AggregateOperation)
instead and add a separate mapping stage withmapToOutputFn
.since Jet 4.3, Jet performs this transformation on the server-side.Jet now has first-class support for data rebalancing, seeGeneralStage.rebalance()
andGeneralStage.rebalance(FunctionEx)
.Since 5.1, the method is unusedsince 5.1, useCapacity.parse(String)
instead.since 5.1, useCapacity.parse(String, MemoryUnit)
insteadfor the sake of better naming. UseObjectDataInput.readString()
insteadfor the sake of better naming. UseObjectDataInput.readStringArray()
insteadfor the sake of better naming. UseObjectDataOutput.writeString(String)
insteadfor the sake of better naming. UseObjectDataOutput.writeStringArray(String[])
insteadfor the sake of better naming. UseClassDefinitionBuilder.addStringArrayField(String)
instead.for the sake of better naming. UseClassDefinitionBuilder.addStringField(String)
instead.for the sake of better naming. UsePortableReader.readString(String)
insteadfor the sake of better naming. UsePortableReader.readStringArray(String)
insteadfor the sake of better naming. UsePortableWriter.writeString(String, String)
instead.for the sake of better naming. UsePortableWriter.writeStringArray(String, String[])
instead.- use the above method that takes allMember arguments Returns a custom implementation of aPartitionGroupStrategy
to override default behavior of zone aware backup strategiesPartitionGroupMetaData
or to provide a specific behavior in case the discovery environment does not provide information about the infrastructure to be used for automatic configuration.since 5.4 - this method name is too ambiguous and does not convey its functionality well (it deserializes the value) - so it is being replaced byMergingValue.getDeserializedValue()
.
-
Enum ConstantDescriptionsince 5.0 Please use
RestEndpointGroup.PERSISTENCE
instead. If this deprecated endpoint group is tried to be activated, we apply this change as it's made to RestEndpointGroup#PERSISTENCE.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.Portable Serialization has been deprecated. We recommend you use Compact Serialization as Portable Serialization will be removed as of version 7.0.