You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by pe...@apache.org on 2021/01/11 07:42:26 UTC
[pulsar] branch asf-site updated: Updated site at revision ab8802b
This is an automated email from the ASF dual-hosted git repository.
penghui pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/pulsar.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 333cdcd Updated site at revision ab8802b
333cdcd is described below
commit 333cdcde5a638e202a7213a91fca0d931ea5e824
Author: Pulsar Site Updater <de...@pulsar.incubator.apache.org>
AuthorDate: Mon Jan 11 07:41:46 2021 +0000
Updated site at revision ab8802b
---
.../client/2.8.0-SNAPSHOT/allclasses-frame.html | 2 +-
.../client/2.8.0-SNAPSHOT/allclasses-noframe.html | 2 +-
.../api/client/2.8.0-SNAPSHOT/constant-values.html | 2 +-
.../api/client/2.8.0-SNAPSHOT/deprecated-list.html | 2 +-
content/api/client/2.8.0-SNAPSHOT/help-doc.html | 2 +-
content/api/client/2.8.0-SNAPSHOT/index-all.html | 2 +-
content/api/client/2.8.0-SNAPSHOT/index.html | 2 +-
.../apache/pulsar/client/api/Authentication.html | 2 +-
.../client/api/AuthenticationDataProvider.html | 2 +-
.../pulsar/client/api/AuthenticationFactory.html | 2 +-
.../pulsar/client/api/BatchMessageContainer.html | 2 +-
.../client/api/BatchReceivePolicy.Builder.html | 2 +-
.../pulsar/client/api/BatchReceivePolicy.html | 2 +-
.../apache/pulsar/client/api/BatcherBuilder.html | 2 +-
.../apache/pulsar/client/api/ClientBuilder.html | 2 +-
.../apache/pulsar/client/api/CompressionType.html | 2 +-
.../org/apache/pulsar/client/api/Consumer.html | 2 +-
.../apache/pulsar/client/api/ConsumerBuilder.html | 2 +-
.../client/api/ConsumerCryptoFailureAction.html | 2 +-
.../pulsar/client/api/ConsumerEventListener.html | 2 +-
.../pulsar/client/api/ConsumerInterceptor.html | 2 +-
.../apache/pulsar/client/api/ConsumerStats.html | 2 +-
.../apache/pulsar/client/api/CryptoKeyReader.html | 2 +-
.../apache/pulsar/client/api/DeadLetterPolicy.html | 2 +-
.../api/EncodedAuthenticationParameterSupport.html | 2 +-
.../pulsar/client/api/EncryptionKeyInfo.html | 2 +-
.../apache/pulsar/client/api/HashingScheme.html | 2 +-
.../apache/pulsar/client/api/KeySharedMode.html | 2 +-
.../KeySharedPolicy.KeySharedPolicyAutoSplit.html | 2 +-
.../api/KeySharedPolicy.KeySharedPolicySticky.html | 2 +-
.../apache/pulsar/client/api/KeySharedPolicy.html | 2 +-
.../apache/pulsar/client/api/KeyStoreParams.html | 2 +-
.../org/apache/pulsar/client/api/Message.html | 2 +-
.../apache/pulsar/client/api/MessageCrypto.html | 2 +-
.../org/apache/pulsar/client/api/MessageId.html | 2 +-
.../apache/pulsar/client/api/MessageListener.html | 2 +-
.../apache/pulsar/client/api/MessageRouter.html | 2 +-
.../pulsar/client/api/MessageRoutingMode.html | 2 +-
.../org/apache/pulsar/client/api/Messages.html | 2 +-
.../org/apache/pulsar/client/api/Producer.html | 2 +-
.../pulsar/client/api/ProducerAccessMode.html | 2 +-
.../apache/pulsar/client/api/ProducerBuilder.html | 2 +-
.../client/api/ProducerCryptoFailureAction.html | 2 +-
.../pulsar/client/api/ProducerInterceptor.html | 2 +-
.../apache/pulsar/client/api/ProducerStats.html | 2 +-
.../apache/pulsar/client/api/ProxyProtocol.html | 2 +-
.../org/apache/pulsar/client/api/PulsarClient.html | 2 +-
...lsarClientException.AlreadyClosedException.html | 2 +-
...sarClientException.AuthenticationException.html | 2 +-
...lsarClientException.AuthorizationException.html | 2 +-
...sarClientException.BrokerMetadataException.html | 2 +-
...ClientException.BrokerPersistenceException.html | 2 +-
.../PulsarClientException.ChecksumException.html | 2 +-
.../PulsarClientException.ConnectException.html | 2 +-
...sarClientException.ConsumerAssignException.html | 2 +-
...ulsarClientException.ConsumerBusyException.html | 2 +-
.../api/PulsarClientException.CryptoException.html | 2 +-
...ception.GettingAuthenticationDataException.html | 2 +-
...lientException.IncompatibleSchemaException.html | 2 +-
...entException.InvalidConfigurationException.html | 2 +-
...sarClientException.InvalidMessageException.html | 2 +-
.../PulsarClientException.InvalidServiceURL.html | 2 +-
...rClientException.InvalidTopicNameException.html | 2 +-
.../api/PulsarClientException.LookupException.html | 2 +-
...sarClientException.MemoryBufferIsFullError.html | 2 +-
...lientException.MessageAcknowledgeException.html | 2 +-
.../PulsarClientException.NotAllowedException.html | 2 +-
...ulsarClientException.NotConnectedException.html | 2 +-
.../PulsarClientException.NotFoundException.html | 2 +-
...ulsarClientException.NotSupportedException.html | 2 +-
...xception.ProducerBlockedQuotaExceededError.html | 2 +-
...tion.ProducerBlockedQuotaExceededException.html | 2 +-
...ulsarClientException.ProducerBusyException.html | 2 +-
...sarClientException.ProducerFencedException.html | 2 +-
...arClientException.ProducerQueueIsFullError.html | 2 +-
.../PulsarClientException.TimeoutException.html | 2 +-
...arClientException.TooManyRequestsException.html | 2 +-
...ClientException.TopicDoesNotExistException.html | 2 +-
...arClientException.TopicTerminatedException.html | 2 +-
...ientException.TransactionConflictException.html | 2 +-
...ception.UnsupportedAuthenticationException.html | 2 +-
.../pulsar/client/api/PulsarClientException.html | 2 +-
.../org/apache/pulsar/client/api/Range.html | 2 +-
.../org/apache/pulsar/client/api/Reader.html | 2 +-
.../apache/pulsar/client/api/ReaderBuilder.html | 2 +-
.../apache/pulsar/client/api/ReaderListener.html | 2 +-
.../pulsar/client/api/RegexSubscriptionMode.html | 2 +-
.../org/apache/pulsar/client/api/Schema.html | 2 +-
.../client/api/SchemaSerializationException.html | 2 +-
.../pulsar/client/api/ServiceUrlProvider.html | 2 +-
.../org/apache/pulsar/client/api/SizeUnit.html | 2 +-
.../client/api/SubscriptionInitialPosition.html | 2 +-
.../apache/pulsar/client/api/SubscriptionMode.html | 2 +-
.../apache/pulsar/client/api/SubscriptionType.html | 2 +-
.../apache/pulsar/client/api/TopicMetadata.html | 2 +-
.../pulsar/client/api/TypedMessageBuilder.html | 2 +-
.../client/api/class-use/Authentication.html | 2 +-
.../api/class-use/AuthenticationDataProvider.html | 2 +-
.../api/class-use/AuthenticationFactory.html | 2 +-
.../api/class-use/BatchMessageContainer.html | 2 +-
.../api/class-use/BatchReceivePolicy.Builder.html | 2 +-
.../client/api/class-use/BatchReceivePolicy.html | 2 +-
.../client/api/class-use/BatcherBuilder.html | 2 +-
.../pulsar/client/api/class-use/ClientBuilder.html | 2 +-
.../client/api/class-use/CompressionType.html | 2 +-
.../pulsar/client/api/class-use/Consumer.html | 2 +-
.../client/api/class-use/ConsumerBuilder.html | 2 +-
.../api/class-use/ConsumerCryptoFailureAction.html | 2 +-
.../api/class-use/ConsumerEventListener.html | 2 +-
.../client/api/class-use/ConsumerInterceptor.html | 2 +-
.../pulsar/client/api/class-use/ConsumerStats.html | 2 +-
.../client/api/class-use/CryptoKeyReader.html | 2 +-
.../client/api/class-use/DeadLetterPolicy.html | 2 +-
.../EncodedAuthenticationParameterSupport.html | 2 +-
.../client/api/class-use/EncryptionKeyInfo.html | 2 +-
.../pulsar/client/api/class-use/HashingScheme.html | 2 +-
.../pulsar/client/api/class-use/KeySharedMode.html | 2 +-
.../KeySharedPolicy.KeySharedPolicyAutoSplit.html | 2 +-
.../KeySharedPolicy.KeySharedPolicySticky.html | 2 +-
.../client/api/class-use/KeySharedPolicy.html | 2 +-
.../client/api/class-use/KeyStoreParams.html | 2 +-
.../pulsar/client/api/class-use/Message.html | 2 +-
.../pulsar/client/api/class-use/MessageCrypto.html | 2 +-
.../pulsar/client/api/class-use/MessageId.html | 2 +-
.../client/api/class-use/MessageListener.html | 2 +-
.../pulsar/client/api/class-use/MessageRouter.html | 2 +-
.../client/api/class-use/MessageRoutingMode.html | 2 +-
.../pulsar/client/api/class-use/Messages.html | 2 +-
.../pulsar/client/api/class-use/Producer.html | 2 +-
.../client/api/class-use/ProducerAccessMode.html | 2 +-
.../client/api/class-use/ProducerBuilder.html | 2 +-
.../api/class-use/ProducerCryptoFailureAction.html | 2 +-
.../client/api/class-use/ProducerInterceptor.html | 2 +-
.../pulsar/client/api/class-use/ProducerStats.html | 2 +-
.../pulsar/client/api/class-use/ProxyProtocol.html | 2 +-
.../pulsar/client/api/class-use/PulsarClient.html | 2 +-
...lsarClientException.AlreadyClosedException.html | 2 +-
...sarClientException.AuthenticationException.html | 2 +-
...lsarClientException.AuthorizationException.html | 2 +-
...sarClientException.BrokerMetadataException.html | 2 +-
...ClientException.BrokerPersistenceException.html | 2 +-
.../PulsarClientException.ChecksumException.html | 2 +-
.../PulsarClientException.ConnectException.html | 2 +-
...sarClientException.ConsumerAssignException.html | 2 +-
...ulsarClientException.ConsumerBusyException.html | 2 +-
.../PulsarClientException.CryptoException.html | 2 +-
...ception.GettingAuthenticationDataException.html | 2 +-
...lientException.IncompatibleSchemaException.html | 2 +-
...entException.InvalidConfigurationException.html | 2 +-
...sarClientException.InvalidMessageException.html | 2 +-
.../PulsarClientException.InvalidServiceURL.html | 2 +-
...rClientException.InvalidTopicNameException.html | 2 +-
.../PulsarClientException.LookupException.html | 2 +-
...sarClientException.MemoryBufferIsFullError.html | 2 +-
...lientException.MessageAcknowledgeException.html | 2 +-
.../PulsarClientException.NotAllowedException.html | 2 +-
...ulsarClientException.NotConnectedException.html | 2 +-
.../PulsarClientException.NotFoundException.html | 2 +-
...ulsarClientException.NotSupportedException.html | 2 +-
...xception.ProducerBlockedQuotaExceededError.html | 2 +-
...tion.ProducerBlockedQuotaExceededException.html | 2 +-
...ulsarClientException.ProducerBusyException.html | 2 +-
...sarClientException.ProducerFencedException.html | 2 +-
...arClientException.ProducerQueueIsFullError.html | 2 +-
.../PulsarClientException.TimeoutException.html | 2 +-
...arClientException.TooManyRequestsException.html | 2 +-
...ClientException.TopicDoesNotExistException.html | 2 +-
...arClientException.TopicTerminatedException.html | 2 +-
...ientException.TransactionConflictException.html | 2 +-
...ception.UnsupportedAuthenticationException.html | 2 +-
.../api/class-use/PulsarClientException.html | 2 +-
.../apache/pulsar/client/api/class-use/Range.html | 2 +-
.../apache/pulsar/client/api/class-use/Reader.html | 2 +-
.../pulsar/client/api/class-use/ReaderBuilder.html | 2 +-
.../client/api/class-use/ReaderListener.html | 2 +-
.../api/class-use/RegexSubscriptionMode.html | 2 +-
.../apache/pulsar/client/api/class-use/Schema.html | 2 +-
.../class-use/SchemaSerializationException.html | 2 +-
.../client/api/class-use/ServiceUrlProvider.html | 2 +-
.../pulsar/client/api/class-use/SizeUnit.html | 2 +-
.../api/class-use/SubscriptionInitialPosition.html | 2 +-
.../client/api/class-use/SubscriptionMode.html | 2 +-
.../client/api/class-use/SubscriptionType.html | 2 +-
.../pulsar/client/api/class-use/TopicMetadata.html | 2 +-
.../client/api/class-use/TypedMessageBuilder.html | 2 +-
.../api/interceptor/ProducerInterceptor.html | 2 +-
.../interceptor/ProducerInterceptorWrapper.html | 2 +-
.../interceptor/class-use/ProducerInterceptor.html | 2 +-
.../class-use/ProducerInterceptorWrapper.html | 2 +-
.../client/api/interceptor/package-frame.html | 2 +-
.../client/api/interceptor/package-summary.html | 2 +-
.../client/api/interceptor/package-tree.html | 2 +-
.../pulsar/client/api/interceptor/package-use.html | 2 +-
.../apache/pulsar/client/api/package-frame.html | 2 +-
.../apache/pulsar/client/api/package-summary.html | 2 +-
.../org/apache/pulsar/client/api/package-tree.html | 2 +-
.../org/apache/pulsar/client/api/package-use.html | 2 +-
.../org/apache/pulsar/client/api/schema/Field.html | 2 +-
.../client/api/schema/FieldSchemaBuilder.html | 2 +-
.../pulsar/client/api/schema/GenericRecord.html | 2 +-
.../client/api/schema/GenericRecordBuilder.html | 2 +-
.../pulsar/client/api/schema/GenericSchema.html | 2 +-
.../client/api/schema/RecordSchemaBuilder.html | 2 +-
.../pulsar/client/api/schema/SchemaBuilder.html | 2 +-
.../pulsar/client/api/schema/SchemaDefinition.html | 2 +-
.../client/api/schema/SchemaDefinitionBuilder.html | 2 +-
.../client/api/schema/SchemaInfoProvider.html | 2 +-
.../pulsar/client/api/schema/SchemaReader.html | 2 +-
.../pulsar/client/api/schema/SchemaWriter.html | 2 +-
.../pulsar/client/api/schema/class-use/Field.html | 2 +-
.../api/schema/class-use/FieldSchemaBuilder.html | 2 +-
.../client/api/schema/class-use/GenericRecord.html | 2 +-
.../api/schema/class-use/GenericRecordBuilder.html | 2 +-
.../client/api/schema/class-use/GenericSchema.html | 2 +-
.../api/schema/class-use/RecordSchemaBuilder.html | 2 +-
.../client/api/schema/class-use/SchemaBuilder.html | 2 +-
.../api/schema/class-use/SchemaDefinition.html | 2 +-
.../schema/class-use/SchemaDefinitionBuilder.html | 2 +-
.../api/schema/class-use/SchemaInfoProvider.html | 2 +-
.../client/api/schema/class-use/SchemaReader.html | 2 +-
.../client/api/schema/class-use/SchemaWriter.html | 2 +-
.../pulsar/client/api/schema/package-frame.html | 2 +-
.../pulsar/client/api/schema/package-summary.html | 2 +-
.../pulsar/client/api/schema/package-tree.html | 2 +-
.../pulsar/client/api/schema/package-use.html | 2 +-
.../pulsar/client/api/transaction/Transaction.html | 2 +-
.../api/transaction/TransactionBufferClient.html | 2 +-
...ferClientException.RequestTimeoutException.html | 2 +-
.../TransactionBufferClientException.html | 2 +-
.../client/api/transaction/TransactionBuilder.html | 2 +-
.../TransactionCoordinatorClient.State.html | 2 +-
.../transaction/TransactionCoordinatorClient.html | 2 +-
...tException.CoordinatorClientStateException.html | 2 +-
...ientException.CoordinatorNotFoundException.html | 2 +-
...rClientException.InvalidTxnStatusException.html | 2 +-
...ception.MetaStoreHandlerNotExistsException.html | 2 +-
...xception.MetaStoreHandlerNotReadyException.html | 2 +-
...ientException.TransactionNotFoundException.html | 2 +-
.../TransactionCoordinatorClientException.html | 2 +-
.../pulsar/client/api/transaction/TxnID.html | 2 +-
.../api/transaction/class-use/Transaction.html | 2 +-
.../class-use/TransactionBufferClient.html | 2 +-
...ferClientException.RequestTimeoutException.html | 2 +-
.../TransactionBufferClientException.html | 2 +-
.../transaction/class-use/TransactionBuilder.html | 2 +-
.../TransactionCoordinatorClient.State.html | 2 +-
.../class-use/TransactionCoordinatorClient.html | 2 +-
...tException.CoordinatorClientStateException.html | 2 +-
...ientException.CoordinatorNotFoundException.html | 2 +-
...rClientException.InvalidTxnStatusException.html | 2 +-
...ception.MetaStoreHandlerNotExistsException.html | 2 +-
...xception.MetaStoreHandlerNotReadyException.html | 2 +-
...ientException.TransactionNotFoundException.html | 2 +-
.../TransactionCoordinatorClientException.html | 2 +-
.../client/api/transaction/class-use/TxnID.html | 2 +-
.../client/api/transaction/package-frame.html | 2 +-
.../client/api/transaction/package-summary.html | 2 +-
.../client/api/transaction/package-tree.html | 2 +-
.../pulsar/client/api/transaction/package-use.html | 2 +-
.../client/internal/DefaultImplementation.html | 2 +-
.../internal/class-use/DefaultImplementation.html | 2 +-
.../pulsar/client/internal/package-frame.html | 2 +-
.../pulsar/client/internal/package-summary.html | 2 +-
.../pulsar/client/internal/package-tree.html | 2 +-
.../apache/pulsar/client/internal/package-use.html | 2 +-
.../org/apache/pulsar/common/api/AuthData.html | 2 +-
.../api/EncryptionContext.EncryptionKey.html | 2 +-
.../pulsar/common/api/EncryptionContext.html | 2 +-
.../pulsar/common/api/class-use/AuthData.html | 2 +-
.../class-use/EncryptionContext.EncryptionKey.html | 2 +-
.../common/api/class-use/EncryptionContext.html | 2 +-
.../apache/pulsar/common/api/package-frame.html | 2 +-
.../apache/pulsar/common/api/package-summary.html | 2 +-
.../org/apache/pulsar/common/api/package-tree.html | 2 +-
.../org/apache/pulsar/common/api/package-use.html | 2 +-
.../InterfaceAudience.LimitedPrivate.html | 2 +-
.../classification/InterfaceAudience.Private.html | 2 +-
.../classification/InterfaceAudience.Public.html | 2 +-
.../common/classification/InterfaceAudience.html | 2 +-
.../InterfaceStability.Evolving.html | 2 +-
.../classification/InterfaceStability.Stable.html | 2 +-
.../InterfaceStability.Unstable.html | 2 +-
.../common/classification/InterfaceStability.html | 2 +-
.../InterfaceAudience.LimitedPrivate.html | 2 +-
.../class-use/InterfaceAudience.Private.html | 2 +-
.../class-use/InterfaceAudience.Public.html | 2 +-
.../class-use/InterfaceAudience.html | 2 +-
.../class-use/InterfaceStability.Evolving.html | 2 +-
.../class-use/InterfaceStability.Stable.html | 2 +-
.../class-use/InterfaceStability.Unstable.html | 2 +-
.../class-use/InterfaceStability.html | 2 +-
.../common/classification/package-frame.html | 2 +-
.../common/classification/package-summary.html | 2 +-
.../pulsar/common/classification/package-tree.html | 2 +-
.../pulsar/common/classification/package-use.html | 2 +-
.../common/schema/KeyValue.KeyValueDecoder.html | 2 +-
.../org/apache/pulsar/common/schema/KeyValue.html | 2 +-
.../pulsar/common/schema/KeyValueEncodingType.html | 2 +-
.../apache/pulsar/common/schema/SchemaInfo.html | 2 +-
.../common/schema/SchemaInfoWithVersion.html | 2 +-
.../apache/pulsar/common/schema/SchemaType.html | 2 +-
.../schema/class-use/KeyValue.KeyValueDecoder.html | 2 +-
.../pulsar/common/schema/class-use/KeyValue.html | 2 +-
.../schema/class-use/KeyValueEncodingType.html | 2 +-
.../pulsar/common/schema/class-use/SchemaInfo.html | 2 +-
.../schema/class-use/SchemaInfoWithVersion.html | 2 +-
.../pulsar/common/schema/class-use/SchemaType.html | 2 +-
.../apache/pulsar/common/schema/package-frame.html | 2 +-
.../pulsar/common/schema/package-summary.html | 2 +-
.../apache/pulsar/common/schema/package-tree.html | 2 +-
.../apache/pulsar/common/schema/package-use.html | 2 +-
.../api/client/2.8.0-SNAPSHOT/overview-frame.html | 2 +-
.../client/2.8.0-SNAPSHOT/overview-summary.html | 2 +-
.../api/client/2.8.0-SNAPSHOT/overview-tree.html | 2 +-
.../api/client/2.8.0-SNAPSHOT/serialized-form.html | 2 +-
content/api/python/2.8.0-SNAPSHOT/index.html | 6 +-
content/api/python/index.html | 6 +-
content/docs/en/2.6.0/concepts-messaging.html | 35 +-
.../docs/en/2.6.0/concepts-messaging/index.html | 35 +-
content/docs/en/2.6.1/concepts-messaging.html | 37 +-
.../docs/en/2.6.1/concepts-messaging/index.html | 37 +-
content/docs/en/2.6.2/concepts-messaging.html | 37 +-
.../docs/en/2.6.2/concepts-messaging/index.html | 37 +-
content/docs/en/concepts-messaging.html | 37 +-
content/docs/en/concepts-messaging/index.html | 37 +-
content/docs/en/next/concepts-messaging.html | 34 +-
content/docs/en/next/concepts-messaging/index.html | 34 +-
content/docs/fr/2.6.0/concepts-messaging.html | 26 +-
.../docs/fr/2.6.0/concepts-messaging/index.html | 26 +-
content/docs/fr/2.6.1/concepts-messaging.html | 28 +-
.../docs/fr/2.6.1/concepts-messaging/index.html | 28 +-
content/docs/fr/2.6.2/concepts-messaging.html | 28 +-
.../docs/fr/2.6.2/concepts-messaging/index.html | 28 +-
content/docs/fr/concepts-messaging.html | 28 +-
content/docs/fr/concepts-messaging/index.html | 28 +-
content/docs/fr/next/concepts-messaging.html | 28 +-
content/docs/fr/next/concepts-messaging/index.html | 28 +-
content/docs/ja/2.6.0/concepts-messaging.html | 26 +-
.../docs/ja/2.6.0/concepts-messaging/index.html | 26 +-
content/docs/ja/2.6.1/concepts-messaging.html | 28 +-
.../docs/ja/2.6.1/concepts-messaging/index.html | 28 +-
content/docs/ja/2.6.2/concepts-messaging.html | 28 +-
.../docs/ja/2.6.2/concepts-messaging/index.html | 28 +-
content/docs/ja/concepts-messaging.html | 28 +-
content/docs/ja/concepts-messaging/index.html | 28 +-
content/docs/ja/next/concepts-messaging.html | 28 +-
content/docs/ja/next/concepts-messaging/index.html | 28 +-
content/docs/ko/2.6.0/concepts-messaging.html | 26 +-
.../docs/ko/2.6.0/concepts-messaging/index.html | 26 +-
content/docs/ko/2.6.1/concepts-messaging.html | 28 +-
.../docs/ko/2.6.1/concepts-messaging/index.html | 28 +-
content/docs/ko/2.6.2/concepts-messaging.html | 28 +-
.../docs/ko/2.6.2/concepts-messaging/index.html | 28 +-
content/docs/ko/concepts-messaging.html | 28 +-
content/docs/ko/concepts-messaging/index.html | 28 +-
content/docs/ko/next/concepts-messaging.html | 28 +-
content/docs/ko/next/concepts-messaging/index.html | 28 +-
content/docs/zh-CN/2.6.0/concepts-messaging.html | 26 +-
.../docs/zh-CN/2.6.0/concepts-messaging/index.html | 26 +-
content/docs/zh-CN/2.6.1/concepts-messaging.html | 28 +-
.../docs/zh-CN/2.6.1/concepts-messaging/index.html | 28 +-
content/docs/zh-CN/2.6.2/concepts-messaging.html | 28 +-
.../docs/zh-CN/2.6.2/concepts-messaging/index.html | 28 +-
content/docs/zh-CN/concepts-messaging.html | 28 +-
content/docs/zh-CN/concepts-messaging/index.html | 28 +-
content/docs/zh-CN/next/concepts-messaging.html | 30 +-
.../docs/zh-CN/next/concepts-messaging/index.html | 30 +-
content/docs/zh-TW/2.6.0/concepts-messaging.html | 26 +-
.../docs/zh-TW/2.6.0/concepts-messaging/index.html | 26 +-
content/docs/zh-TW/2.6.1/concepts-messaging.html | 28 +-
.../docs/zh-TW/2.6.1/concepts-messaging/index.html | 28 +-
content/docs/zh-TW/2.6.2/concepts-messaging.html | 28 +-
.../docs/zh-TW/2.6.2/concepts-messaging/index.html | 28 +-
content/docs/zh-TW/concepts-messaging.html | 28 +-
content/docs/zh-TW/concepts-messaging/index.html | 28 +-
content/docs/zh-TW/next/concepts-messaging.html | 28 +-
.../docs/zh-TW/next/concepts-messaging/index.html | 28 +-
content/swagger/2.8.0-SNAPSHOT/swagger.json | 588 ++++++++++---------
.../swagger/2.8.0-SNAPSHOT/swaggerfunctions.json | 546 +++++++++---------
.../swagger/2.8.0-SNAPSHOT/swaggerpackages.json | 516 ++++++++---------
content/swagger/2.8.0-SNAPSHOT/swaggersink.json | 516 ++++++++---------
content/swagger/2.8.0-SNAPSHOT/swaggersource.json | 516 ++++++++---------
content/swagger/2.8.0-SNAPSHOT/v2/swagger.json | 639 +++++++++++----------
.../2.8.0-SNAPSHOT/v3/swaggerfunctions.json | 582 +++++++++----------
.../swagger/2.8.0-SNAPSHOT/v3/swaggerpackages.json | 558 +++++++++---------
content/swagger/2.8.0-SNAPSHOT/v3/swaggersink.json | 558 +++++++++---------
.../swagger/2.8.0-SNAPSHOT/v3/swaggersource.json | 558 +++++++++---------
content/swagger/master/swagger.json | 588 ++++++++++---------
content/swagger/master/swaggerfunctions.json | 546 +++++++++---------
content/swagger/master/swaggerpackages.json | 516 ++++++++---------
content/swagger/master/swaggersink.json | 516 ++++++++---------
content/swagger/master/swaggersource.json | 516 ++++++++---------
content/swagger/master/v2/swagger.json | 639 +++++++++++----------
content/swagger/master/v3/swaggerfunctions.json | 582 +++++++++----------
content/swagger/master/v3/swaggerpackages.json | 558 +++++++++---------
content/swagger/master/v3/swaggersink.json | 558 +++++++++---------
content/swagger/master/v3/swaggersource.json | 558 +++++++++---------
content/swagger/restApiVersions.json | 16 +-
.../tools/pulsar-admin/2.8.0-SNAPSHOT/index.html | 9 +-
.../tools/pulsar-admin/2.8.0-SNAPSHOT/navData.js | 2 +-
400 files changed, 6710 insertions(+), 6857 deletions(-)
diff --git a/content/api/client/2.8.0-SNAPSHOT/allclasses-frame.html b/content/api/client/2.8.0-SNAPSHOT/allclasses-frame.html
index 47540db..a16906a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/allclasses-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/allclasses-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>All Classes (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/allclasses-noframe.html b/content/api/client/2.8.0-SNAPSHOT/allclasses-noframe.html
index a4fc492..b3ed165 100644
--- a/content/api/client/2.8.0-SNAPSHOT/allclasses-noframe.html
+++ b/content/api/client/2.8.0-SNAPSHOT/allclasses-noframe.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>All Classes (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/constant-values.html b/content/api/client/2.8.0-SNAPSHOT/constant-values.html
index efea23d..6270026 100644
--- a/content/api/client/2.8.0-SNAPSHOT/constant-values.html
+++ b/content/api/client/2.8.0-SNAPSHOT/constant-values.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Constant Field Values (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/deprecated-list.html b/content/api/client/2.8.0-SNAPSHOT/deprecated-list.html
index 17fdadc..2372264 100644
--- a/content/api/client/2.8.0-SNAPSHOT/deprecated-list.html
+++ b/content/api/client/2.8.0-SNAPSHOT/deprecated-list.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Deprecated List (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/help-doc.html b/content/api/client/2.8.0-SNAPSHOT/help-doc.html
index e29ad09..15ddb42 100644
--- a/content/api/client/2.8.0-SNAPSHOT/help-doc.html
+++ b/content/api/client/2.8.0-SNAPSHOT/help-doc.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>API Help (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/index-all.html b/content/api/client/2.8.0-SNAPSHOT/index-all.html
index b5c0fcf..ebdf153 100644
--- a/content/api/client/2.8.0-SNAPSHOT/index-all.html
+++ b/content/api/client/2.8.0-SNAPSHOT/index-all.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Index (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/index.html b/content/api/client/2.8.0-SNAPSHOT/index.html
index 4a9233f..b08bbd2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/index.html
+++ b/content/api/client/2.8.0-SNAPSHOT/index.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Pulsar Client :: API 2.8.0-SNAPSHOT API</title>
<script type="text/javascript">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Authentication.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Authentication.html
index 0c2c0fb..36bfa25 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Authentication.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Authentication.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Authentication (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationDataProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationDataProvider.html
index 7d462a1..fb271d8 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationDataProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationDataProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>AuthenticationDataProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationFactory.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationFactory.html
index 5b7fdec..8e9a0ac 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationFactory.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/AuthenticationFactory.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>AuthenticationFactory (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchMessageContainer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchMessageContainer.html
index f3138a0..a228d69 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchMessageContainer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchMessageContainer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>BatchMessageContainer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.Builder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.Builder.html
index e2a4a3d..386647e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.Builder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.Builder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>BatchReceivePolicy.Builder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.html
index a4b56f2..6eca82b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatchReceivePolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>BatchReceivePolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatcherBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatcherBuilder.html
index 067170a..a0d65ec 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatcherBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/BatcherBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>BatcherBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ClientBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ClientBuilder.html
index 0c04ec5..e000a59 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ClientBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ClientBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ClientBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CompressionType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CompressionType.html
index 6cceed4..68d6580 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CompressionType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CompressionType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>CompressionType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Consumer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Consumer.html
index 1a9fd50..a5222ce 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Consumer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Consumer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Consumer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerBuilder.html
index beaf3cb..dad42cc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ConsumerBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerCryptoFailureAction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerCryptoFailureAction.html
index b1fefcf..359fb50 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerCryptoFailureAction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerCryptoFailureAction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ConsumerCryptoFailureAction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerEventListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerEventListener.html
index d800388..125396a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerEventListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerEventListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ConsumerEventListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerInterceptor.html
index 2f52d49..06f5cbf 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ConsumerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerStats.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerStats.html
index ea343b5..d35a630 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerStats.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ConsumerStats.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ConsumerStats (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CryptoKeyReader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CryptoKeyReader.html
index 6eb6d0e..600fd7f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CryptoKeyReader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/CryptoKeyReader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>CryptoKeyReader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/DeadLetterPolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/DeadLetterPolicy.html
index 5611843..9e01970 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/DeadLetterPolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/DeadLetterPolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>DeadLetterPolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncodedAuthenticationParameterSupport.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncodedAuthenticationParameterSupport.html
index 1206ef5..b8f669c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncodedAuthenticationParameterSupport.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncodedAuthenticationParameterSupport.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>EncodedAuthenticationParameterSupport (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncryptionKeyInfo.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncryptionKeyInfo.html
index e57c36e..7ba2c83 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncryptionKeyInfo.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/EncryptionKeyInfo.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>EncryptionKeyInfo (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/HashingScheme.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/HashingScheme.html
index a2003e5..1fccaa1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/HashingScheme.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/HashingScheme.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>HashingScheme (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedMode.html
index eda59fd..5cd25dc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeySharedMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicyAutoSplit.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicyAutoSplit.html
index a29e9c7..10242d7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicyAutoSplit.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicyAutoSplit.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeySharedPolicy.KeySharedPolicyAutoSplit (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicySticky.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicySticky.html
index ece98fb..3c0863a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicySticky.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.KeySharedPolicySticky.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeySharedPolicy.KeySharedPolicySticky (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.html
index a35496b..2a7aae2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeySharedPolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeySharedPolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeyStoreParams.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeyStoreParams.html
index 4263340..436a308 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeyStoreParams.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/KeyStoreParams.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeyStoreParams (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Message.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Message.html
index 43cacba..1474f6f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Message.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Message.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Message (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageCrypto.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageCrypto.html
index fa87738..ba5b2df 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageCrypto.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageCrypto.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>MessageCrypto (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageId.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageId.html
index 193eb0b..d6bf723 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageId.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageId.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>MessageId (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageListener.html
index de3be36..54091db 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>MessageListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRouter.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRouter.html
index aaf744f..5706449 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRouter.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRouter.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>MessageRouter (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRoutingMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRoutingMode.html
index ea1b175..c7feb08 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRoutingMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/MessageRoutingMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>MessageRoutingMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Messages.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Messages.html
index 97601a3..ddb9258 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Messages.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Messages.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Messages (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Producer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Producer.html
index 7bf4f7d..881e2e0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Producer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Producer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Producer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerAccessMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerAccessMode.html
index 616f2c9..85bc6a0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerAccessMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerAccessMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerAccessMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerBuilder.html
index abf7e91..661e2df 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerCryptoFailureAction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerCryptoFailureAction.html
index f5872b1..a3b4b26 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerCryptoFailureAction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerCryptoFailureAction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerCryptoFailureAction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerInterceptor.html
index 293615b..3902f05 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerStats.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerStats.html
index 74cbe6e..ab62893 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerStats.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProducerStats.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerStats (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProxyProtocol.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProxyProtocol.html
index 0c5afb3..7b43668 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProxyProtocol.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ProxyProtocol.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProxyProtocol (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClient.html
index a2eb736..e1591f7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AlreadyClosedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AlreadyClosedException.html
index 66c78ae..c146387 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AlreadyClosedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AlreadyClosedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.AlreadyClosedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthenticationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthenticationException.html
index aa83efd..c58485c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthenticationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthenticationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.AuthenticationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthorizationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthorizationException.html
index 1f9868a..d426d05 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthorizationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.AuthorizationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.AuthorizationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerMetadataException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerMetadataException.html
index 9d664ab..14b3697 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerMetadataException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerMetadataException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.BrokerMetadataException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerPersistenceException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerPersistenceException.html
index 54ba2e6..7338bc7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerPersistenceException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.BrokerPersistenceException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.BrokerPersistenceException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ChecksumException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ChecksumException.html
index 93a6b7d2..a2ec433 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ChecksumException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ChecksumException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ChecksumException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConnectException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConnectException.html
index a8b163b..a21b3f2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConnectException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConnectException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ConnectException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerAssignException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerAssignException.html
index 0e78bdf..cbc3c6c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerAssignException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerAssignException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ConsumerAssignException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerBusyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerBusyException.html
index 7aed126..2e8d31e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerBusyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ConsumerBusyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ConsumerBusyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.CryptoException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.CryptoException.html
index c1781a1..1326867 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.CryptoException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.CryptoException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.CryptoException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.GettingAuthenticationDataException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.GettingAuthenticationDataException.html
index e4c9527..770296b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.GettingAuthenticationDataException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.GettingAuthenticationDataException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.GettingAuthenticationDataException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.IncompatibleSchemaException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.IncompatibleSchemaException.html
index 09b957d..2ea8e24 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.IncompatibleSchemaException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.IncompatibleSchemaException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.IncompatibleSchemaException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidConfigurationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidConfigurationException.html
index 0f782b4..57e29ac 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidConfigurationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidConfigurationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.InvalidConfigurationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidMessageException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidMessageException.html
index df0717e..b18aebd 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidMessageException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidMessageException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.InvalidMessageException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidServiceURL.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidServiceURL.html
index 02a4928..1bd3dd5 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidServiceURL.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidServiceURL.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.InvalidServiceURL (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidTopicNameException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidTopicNameException.html
index ccbe971..91376c6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidTopicNameException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.InvalidTopicNameException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.InvalidTopicNameException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.LookupException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.LookupException.html
index 601aa81..92eb3d2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.LookupException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.LookupException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.LookupException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MemoryBufferIsFullError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MemoryBufferIsFullError.html
index 28856dc..bdc554d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MemoryBufferIsFullError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MemoryBufferIsFullError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.MemoryBufferIsFullError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MessageAcknowledgeException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MessageAcknowledgeException.html
index ce3351c..7a39fc9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MessageAcknowledgeException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.MessageAcknowledgeException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.MessageAcknowledgeException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotAllowedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotAllowedException.html
index 57f9378..d6e3f63 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotAllowedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotAllowedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.NotAllowedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotConnectedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotConnectedException.html
index f5367cf..087bf40 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotConnectedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotConnectedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.NotConnectedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotFoundException.html
index ba884e3..834d155 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.NotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotSupportedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotSupportedException.html
index cf5a24a..e5c833a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotSupportedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.NotSupportedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.NotSupportedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededError.html
index 18dfd8b..9a272fa 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ProducerBlockedQuotaExceededError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededException.html
index 63388bf..95c4944 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBlockedQuotaExceededException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ProducerBlockedQuotaExceededException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBusyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBusyException.html
index f0936b0..7b7e6eb 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBusyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerBusyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ProducerBusyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerFencedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerFencedException.html
index 452301f..17409ea 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerFencedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerFencedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ProducerFencedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerQueueIsFullError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerQueueIsFullError.html
index 4ad1682..05e7383 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerQueueIsFullError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.ProducerQueueIsFullError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.ProducerQueueIsFullError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TimeoutException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TimeoutException.html
index 51cb961..781552d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TimeoutException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TimeoutException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.TimeoutException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TooManyRequestsException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TooManyRequestsException.html
index 4d65e1e..b1b6175 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TooManyRequestsException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TooManyRequestsException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.TooManyRequestsException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicDoesNotExistException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicDoesNotExistException.html
index 24199ee..8c7b266 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicDoesNotExistException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicDoesNotExistException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.TopicDoesNotExistException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicTerminatedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicTerminatedException.html
index f67d92e..08a0026 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicTerminatedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TopicTerminatedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.TopicTerminatedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TransactionConflictException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TransactionConflictException.html
index 01a91ec..50bcdef 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TransactionConflictException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.TransactionConflictException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.TransactionConflictException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.UnsupportedAuthenticationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.UnsupportedAuthenticationException.html
index 1cc877d..34dc946 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.UnsupportedAuthenticationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.UnsupportedAuthenticationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException.UnsupportedAuthenticationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.html
index df62c0b..0255a98 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/PulsarClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>PulsarClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Range.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Range.html
index 44bf0d5..ae7d88f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Range.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Range.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Range (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Reader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Reader.html
index c166a8c..b1be76c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Reader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Reader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Reader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderBuilder.html
index d035d4e..ebf9c6e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ReaderBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderListener.html
index 34ffc99..e5f8b2a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ReaderListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ReaderListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/RegexSubscriptionMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/RegexSubscriptionMode.html
index a94ab0e..b60036f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/RegexSubscriptionMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/RegexSubscriptionMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>RegexSubscriptionMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Schema.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Schema.html
index 7d30bae..0535a27 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Schema.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/Schema.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SchemaSerializationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SchemaSerializationException.html
index 42f7100..48282c6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SchemaSerializationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SchemaSerializationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaSerializationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ServiceUrlProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ServiceUrlProvider.html
index 46f2e68..a3a37b1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ServiceUrlProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/ServiceUrlProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ServiceUrlProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SizeUnit.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SizeUnit.html
index 926b652..1e3d544 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SizeUnit.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SizeUnit.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SizeUnit (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionInitialPosition.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionInitialPosition.html
index 52d5cef..43dc8fe 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionInitialPosition.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionInitialPosition.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SubscriptionInitialPosition (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionMode.html
index b165457..3371e94 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SubscriptionMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionType.html
index c6f4ac4..dae51bb 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/SubscriptionType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SubscriptionType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TopicMetadata.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TopicMetadata.html
index 71e5b87..68fdc22c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TopicMetadata.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TopicMetadata.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TopicMetadata (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TypedMessageBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TypedMessageBuilder.html
index 2755ce7..4b0f7ef 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TypedMessageBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/TypedMessageBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TypedMessageBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Authentication.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Authentication.html
index 7d42cb7..15130f0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Authentication.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Authentication.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Authentication (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationDataProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationDataProvider.html
index 6049ea6..3b663e1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationDataProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationDataProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.AuthenticationDataProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationFactory.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationFactory.html
index 1fa2a1d..073738e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationFactory.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/AuthenticationFactory.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.AuthenticationFactory (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchMessageContainer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchMessageContainer.html
index 5e1e7dd..e21abad 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchMessageContainer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchMessageContainer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.BatchMessageContainer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.Builder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.Builder.html
index 224d684..6ed4318 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.Builder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.Builder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.BatchReceivePolicy.Builder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.html
index 3f55c8f..71fcf54 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatchReceivePolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.BatchReceivePolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatcherBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatcherBuilder.html
index 018c703..9633c83 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatcherBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/BatcherBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.BatcherBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ClientBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ClientBuilder.html
index 9c27678..9782cfc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ClientBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ClientBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ClientBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CompressionType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CompressionType.html
index aadce26..202d996 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CompressionType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CompressionType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.CompressionType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Consumer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Consumer.html
index 21adacc..15a4b2b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Consumer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Consumer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Consumer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerBuilder.html
index 76948d5..5932473 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ConsumerBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerCryptoFailureAction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerCryptoFailureAction.html
index b8147bc..5740bd3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerCryptoFailureAction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerCryptoFailureAction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.ConsumerCryptoFailureAction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerEventListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerEventListener.html
index 0ed2f07..7e46918 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerEventListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerEventListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ConsumerEventListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerInterceptor.html
index e7b3b9b..15544ea 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ConsumerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerStats.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerStats.html
index 9133798..a2bf850 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerStats.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ConsumerStats.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ConsumerStats (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CryptoKeyReader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CryptoKeyReader.html
index e6488fa..43bd66f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CryptoKeyReader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/CryptoKeyReader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.CryptoKeyReader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/DeadLetterPolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/DeadLetterPolicy.html
index c5e7d91..00be187 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/DeadLetterPolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/DeadLetterPolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.DeadLetterPolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncodedAuthenticationParameterSupport.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncodedAuthenticationParameterSupport.html
index a0f563c..922b258 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncodedAuthenticationParameterSupport.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncodedAuthenticationParameterSupport.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.EncodedAuthenticationParameterSupport (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncryptionKeyInfo.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncryptionKeyInfo.html
index 9ae0ff0..bed858c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncryptionKeyInfo.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/EncryptionKeyInfo.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.EncryptionKeyInfo (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/HashingScheme.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/HashingScheme.html
index 0b83686..18b0ddb 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/HashingScheme.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/HashingScheme.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.HashingScheme (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedMode.html
index bf3c601..2f5209e8 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.KeySharedMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicyAutoSplit.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicyAutoSplit.html
index 4c027b3..87b08a0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicyAutoSplit.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicyAutoSplit.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.KeySharedPolicy.KeySharedPolicyAutoSplit (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicySticky.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicySticky.html
index c3f0dcb..56e5fc3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicySticky.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.KeySharedPolicySticky.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.KeySharedPolicy.KeySharedPolicySticky (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.html
index 2ed6892..e0fc3fd 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeySharedPolicy.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.KeySharedPolicy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeyStoreParams.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeyStoreParams.html
index ef6ee10..03e9b26 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeyStoreParams.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/KeyStoreParams.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.KeyStoreParams (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Message.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Message.html
index d89322f..de0902a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Message.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Message.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Message (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageCrypto.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageCrypto.html
index 3dd81b0..bdaf923 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageCrypto.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageCrypto.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.MessageCrypto (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageId.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageId.html
index ea44794..78965a9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageId.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageId.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.MessageId (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageListener.html
index 2b2ec27..115e192 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.MessageListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRouter.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRouter.html
index ec23430..4d035be 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRouter.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRouter.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.MessageRouter (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRoutingMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRoutingMode.html
index 334dccb..ce3b387 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRoutingMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/MessageRoutingMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.MessageRoutingMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Messages.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Messages.html
index 9d76542..188c009 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Messages.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Messages.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Messages (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Producer.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Producer.html
index e27d50e..0cfee7f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Producer.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Producer.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Producer (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerAccessMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerAccessMode.html
index 5499594..239530f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerAccessMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerAccessMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.ProducerAccessMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerBuilder.html
index 4f0f11c..3e41ec9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ProducerBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerCryptoFailureAction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerCryptoFailureAction.html
index 7ee7261..9a96942 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerCryptoFailureAction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerCryptoFailureAction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.ProducerCryptoFailureAction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerInterceptor.html
index 06cd083..7332d14 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ProducerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerStats.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerStats.html
index 0ece467..5b3b92b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerStats.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProducerStats.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ProducerStats (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProxyProtocol.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProxyProtocol.html
index 67877dc..0785eab 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProxyProtocol.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ProxyProtocol.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.ProxyProtocol (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClient.html
index a00a304..4347992 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.PulsarClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AlreadyClosedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AlreadyClosedException.html
index 6ede07b..e4e17b3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AlreadyClosedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AlreadyClosedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.AlreadyClosedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthenticationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthenticationException.html
index 9ff4a63..b02602a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthenticationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthenticationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.AuthenticationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthorizationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthorizationException.html
index 34aa81d..4108ad6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthorizationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.AuthorizationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.AuthorizationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerMetadataException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerMetadataException.html
index 53019fc..061d3f2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerMetadataException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerMetadataException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.BrokerMetadataException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerPersistenceException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerPersistenceException.html
index b47dc67..5c28a0d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerPersistenceException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.BrokerPersistenceException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.BrokerPersistenceException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ChecksumException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ChecksumException.html
index c68facb..4242321 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ChecksumException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ChecksumException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ChecksumException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConnectException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConnectException.html
index 8463851..580fa03 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConnectException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConnectException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ConnectException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerAssignException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerAssignException.html
index 63d26d9..1f094e5 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerAssignException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerAssignException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ConsumerAssignException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerBusyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerBusyException.html
index a7d67e8..96cdf86 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerBusyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ConsumerBusyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ConsumerBusyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.CryptoException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.CryptoException.html
index 1d8cdac..7846584 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.CryptoException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.CryptoException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.CryptoException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.GettingAuthenticationDataException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.GettingAuthenticationDataException.html
index d2a9345..007d756 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.GettingAuthenticationDataException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.GettingAuthenticationDataException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.GettingAuthenticationDataException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.IncompatibleSchemaException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.IncompatibleSchemaException.html
index 04b97b3..e7b34fa 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.IncompatibleSchemaException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.IncompatibleSchemaException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.IncompatibleSchemaException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidConfigurationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidConfigurationException.html
index c6b269b..da332aa 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidConfigurationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidConfigurationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.InvalidConfigurationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidMessageException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidMessageException.html
index 205c3d4..e0d3744 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidMessageException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidMessageException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.InvalidMessageException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidServiceURL.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidServiceURL.html
index 7bc2fe5..67eeabf 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidServiceURL.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidServiceURL.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.InvalidServiceURL (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidTopicNameException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidTopicNameException.html
index ef86382..13daf0e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidTopicNameException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.InvalidTopicNameException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.InvalidTopicNameException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.LookupException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.LookupException.html
index fe8507d..9cc2d6b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.LookupException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.LookupException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.LookupException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MemoryBufferIsFullError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MemoryBufferIsFullError.html
index d3e4554..a30d53c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MemoryBufferIsFullError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MemoryBufferIsFullError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.MemoryBufferIsFullError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MessageAcknowledgeException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MessageAcknowledgeException.html
index 0908dbf..09cc168 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MessageAcknowledgeException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.MessageAcknowledgeException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.MessageAcknowledgeException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotAllowedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotAllowedException.html
index 7c15014..5643535 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotAllowedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotAllowedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.NotAllowedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotConnectedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotConnectedException.html
index 7ae56d2..26c2192 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotConnectedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotConnectedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.NotConnectedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotFoundException.html
index ba46f48..65a4d96 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.NotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotSupportedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotSupportedException.html
index 43b8425..a9f5aa1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotSupportedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.NotSupportedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.NotSupportedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededError.html
index 8a0dff5..e4a0976 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ProducerBlockedQuotaExceededError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededException.html
index 1f6a5ce..9a05d15 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBlockedQuotaExceededException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ProducerBlockedQuotaExceededException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBusyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBusyException.html
index c8afccc..861f237 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBusyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerBusyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ProducerBusyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerFencedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerFencedException.html
index 13f19be..af186c6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerFencedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerFencedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ProducerFencedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerQueueIsFullError.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerQueueIsFullError.html
index c24d23f..d62a3ad 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerQueueIsFullError.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.ProducerQueueIsFullError.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.ProducerQueueIsFullError (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TimeoutException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TimeoutException.html
index 4acc5ba..85e70c3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TimeoutException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TimeoutException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.TimeoutException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TooManyRequestsException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TooManyRequestsException.html
index 0e60700..6896023 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TooManyRequestsException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TooManyRequestsException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.TooManyRequestsException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicDoesNotExistException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicDoesNotExistException.html
index 4e3e6d0..0e45e74 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicDoesNotExistException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicDoesNotExistException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.TopicDoesNotExistException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicTerminatedException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicTerminatedException.html
index b5bc20e..45e2315 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicTerminatedException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TopicTerminatedException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.TopicTerminatedException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TransactionConflictException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TransactionConflictException.html
index d6ff383..c09c0ec 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TransactionConflictException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.TransactionConflictException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.TransactionConflictException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.UnsupportedAuthenticationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.UnsupportedAuthenticationException.html
index d12466b..23bce45 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.UnsupportedAuthenticationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.UnsupportedAuthenticationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException.UnsupportedAuthenticationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.html
index 5f73a94..0d0f484 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/PulsarClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.PulsarClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Range.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Range.html
index e4db04a..aa76dc3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Range.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Range.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.Range (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Reader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Reader.html
index 794fb7a..c58be6c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Reader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Reader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Reader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderBuilder.html
index dfedc2d..d1077d0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ReaderBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderListener.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderListener.html
index 5c5d14e..4941d5b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderListener.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ReaderListener.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ReaderListener (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/RegexSubscriptionMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/RegexSubscriptionMode.html
index e7f1fa4..1eb3262 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/RegexSubscriptionMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/RegexSubscriptionMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.RegexSubscriptionMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Schema.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Schema.html
index 341c268..7cd4916 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Schema.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/Schema.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.Schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SchemaSerializationException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SchemaSerializationException.html
index a2bf8dc..73eee2e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SchemaSerializationException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SchemaSerializationException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.SchemaSerializationException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ServiceUrlProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ServiceUrlProvider.html
index c236f5d..a5d3929 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ServiceUrlProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/ServiceUrlProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.ServiceUrlProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SizeUnit.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SizeUnit.html
index fafa161..45d5cc8 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SizeUnit.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SizeUnit.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.SizeUnit (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionInitialPosition.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionInitialPosition.html
index 78c2b31..7558331 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionInitialPosition.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionInitialPosition.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.SubscriptionInitialPosition (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionMode.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionMode.html
index 79dca74..63768f9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionMode.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionMode.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.SubscriptionMode (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionType.html
index 04a6890..e02fa68 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/SubscriptionType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.SubscriptionType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TopicMetadata.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TopicMetadata.html
index d0438bd..1daa326 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TopicMetadata.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TopicMetadata.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.TopicMetadata (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TypedMessageBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TypedMessageBuilder.html
index f878e95..1ac3236 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TypedMessageBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/class-use/TypedMessageBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.TypedMessageBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptor.html
index 05fbc0c..69445d9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptorWrapper.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptorWrapper.html
index c4aab57..ece797f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptorWrapper.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/ProducerInterceptorWrapper.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>ProducerInterceptorWrapper (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptor.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptor.html
index d24f6d1..64b4e48 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptor.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptor.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.interceptor.ProducerInterceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptorWrapper.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptorWrapper.html
index 3075c04..f569aea 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptorWrapper.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/class-use/ProducerInterceptorWrapper.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.interceptor.ProducerInterceptorWrapper (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-frame.html
index a14285d..98344be 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.interceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-summary.html
index f338c8f..7e2d3de 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.interceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-tree.html
index 3a3180d..ef1d6e3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.interceptor Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-use.html
index 3a189c1..b320dcc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/interceptor/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.client.api.interceptor (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-frame.html
index a28f8e2..c34b813 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-summary.html
index ebb27e2..43e146e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-tree.html
index d596763..44930d6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-use.html
index 87e4ff6..a189843 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.client.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/Field.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/Field.html
index 17c9ac5..9da9c03 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/Field.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/Field.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Field (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/FieldSchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/FieldSchemaBuilder.html
index 14cc344..3ec8a4c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/FieldSchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/FieldSchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>FieldSchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecord.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecord.html
index 7eeeaf5..53775dd 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecord.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecord.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GenericRecord (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecordBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecordBuilder.html
index c2736a9..86b54a4 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecordBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericRecordBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GenericRecordBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericSchema.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericSchema.html
index f08e2c3..05dfcc1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericSchema.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/GenericSchema.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>GenericSchema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/RecordSchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/RecordSchemaBuilder.html
index 6bc8f12..4866996 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/RecordSchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/RecordSchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>RecordSchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaBuilder.html
index afd4b9c..f47fcfe 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinition.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinition.html
index f772e11..6c49978 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinition.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinition.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaDefinition (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinitionBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinitionBuilder.html
index af0e5da..8452a37 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinitionBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaDefinitionBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaDefinitionBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaInfoProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaInfoProvider.html
index 75fd850..8f93588 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaInfoProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaInfoProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaInfoProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaReader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaReader.html
index 9723791..3c9c8ad 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaReader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaReader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaReader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaWriter.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaWriter.html
index fb12b8b..a48b252 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaWriter.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/SchemaWriter.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaWriter (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/Field.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/Field.html
index d5565aa..13b35a0 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/Field.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/Field.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.schema.Field (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/FieldSchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/FieldSchemaBuilder.html
index 250ab8b..864028c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/FieldSchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/FieldSchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.FieldSchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecord.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecord.html
index 5a229de..544557e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecord.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecord.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.GenericRecord (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecordBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecordBuilder.html
index 905b10b..4c10401 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecordBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericRecordBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.GenericRecordBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericSchema.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericSchema.html
index 5858501..c681b4e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericSchema.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/GenericSchema.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.GenericSchema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/RecordSchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/RecordSchemaBuilder.html
index 66f7e34..c941b48 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/RecordSchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/RecordSchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.RecordSchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaBuilder.html
index c7c6bb3..3cdcf67 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinition.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinition.html
index fb55cf6..5ae41af 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinition.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinition.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaDefinition (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinitionBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinitionBuilder.html
index 6c915ca..f51c098 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinitionBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaDefinitionBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaDefinitionBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaInfoProvider.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaInfoProvider.html
index fc0c5d5..7336f25 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaInfoProvider.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaInfoProvider.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaInfoProvider (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaReader.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaReader.html
index f6afc02..79ad1f6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaReader.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaReader.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaReader (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaWriter.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaWriter.html
index 69b54b8..111296c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaWriter.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/class-use/SchemaWriter.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.schema.SchemaWriter (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-frame.html
index 5f53342..b133985 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-summary.html
index 7353e69..b2d131e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-tree.html
index 3baa010..b8b084b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.schema Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-use.html
index 80f9962..2ae3eca 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/schema/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.client.api.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/Transaction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/Transaction.html
index 5113a02..b333a5f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/Transaction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/Transaction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Transaction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClient.html
index 5fa2b15..9907083 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionBufferClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.RequestTimeoutException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.RequestTimeoutException.html
index eab2823..59379a2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.RequestTimeoutException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.RequestTimeoutException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionBufferClientException.RequestTimeoutException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.html
index 2f1bab7..94d670e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBufferClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionBufferClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBuilder.html
index 518b210..02c4f98 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.State.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.State.html
index 101fa7a..ee3f853 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.State.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.State.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClient.State (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.html
index 46fb264..f1d2a7b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorClientStateException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorClientStateException.html
index be34deb..06e372a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorClientStateException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorClientStateException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.CoordinatorClientStateException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorNotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
index b528431..961b736 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.CoordinatorNotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.InvalidTxnStatusException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.InvalidTxnStatusException.html
index 2f5bce4..354d9fc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.InvalidTxnStatusException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.InvalidTxnStatusException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.InvalidTxnStatusException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
index 554e37e..5b7d621 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
index afa424c..3c2c79e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.TransactionNotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.TransactionNotFoundException.html
index 49c523a..044df3b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.TransactionNotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.TransactionNotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException.TransactionNotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.html
index eaee473..01700f4 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TransactionCoordinatorClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TransactionCoordinatorClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TxnID.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TxnID.html
index be0ca89..6a200d2 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TxnID.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/TxnID.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>TxnID (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/Transaction.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/Transaction.html
index 08cfe3a..c89ff50 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/Transaction.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/Transaction.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.transaction.Transaction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClient.html
index ae12154..1906700 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.transaction.TransactionBufferClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.RequestTimeoutException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.RequestTimeoutException.html
index 1087fb9..124f913 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.RequestTimeoutException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.RequestTimeoutException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionBufferClientException.RequestTimeoutException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.html
index ea6d3b4..d9a1706 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBufferClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionBufferClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBuilder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBuilder.html
index a76925f..b7d198b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBuilder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionBuilder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.transaction.TransactionBuilder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.State.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.State.html
index 92598b1..76e33fc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.State.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.State.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClient.State (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.html
index af39661..d030dd5 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClient.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.client.api.transaction.TransactionCoordinatorClient (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorClientStateException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorClientStateException.html
index 10069ea..acc0758 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorClientStateException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorClientStateException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.CoordinatorClientStateException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorNotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
index 56a116c..3c939df 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.CoordinatorNotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.CoordinatorNotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.InvalidTxnStatusException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.InvalidTxnStatusException.html
index c783f95..0adb064 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.InvalidTxnStatusException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.InvalidTxnStatusException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.InvalidTxnStatusException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
index 9261589..2e885b7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.MetaStoreHandlerNotExistsException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
index 86c3599..448d07c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.MetaStoreHandlerNotReadyException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.TransactionNotFoundException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.TransactionNotFoundException.html
index 3aa0cb4..04e3e28 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.TransactionNotFoundException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.TransactionNotFoundException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException.TransactionNotFoundException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.html
index 79f2f1e..757ff15 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TransactionCoordinatorClientException.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TransactionCoordinatorClientException (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TxnID.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TxnID.html
index 89675c1..2f7ef54 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TxnID.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/class-use/TxnID.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.api.transaction.TxnID (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-frame.html
index b4de9c5..bdfc89b 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.transaction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-summary.html
index 96c22c3..578d601 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.transaction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-tree.html
index c834c25..fa073f4 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.api.transaction Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-use.html
index 49149b7..570c522 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/api/transaction/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.client.api.transaction (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/DefaultImplementation.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/DefaultImplementation.html
index 9bca255..3687923 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/DefaultImplementation.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/DefaultImplementation.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>DefaultImplementation (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/class-use/DefaultImplementation.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/class-use/DefaultImplementation.html
index aadc534..977445c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/class-use/DefaultImplementation.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/class-use/DefaultImplementation.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.client.internal.DefaultImplementation (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-frame.html
index bbcf81d..625dfd7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.internal (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-summary.html
index 8a18d2d..ad8d24e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.internal (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-tree.html
index 8055b89..743c73a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.client.internal Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-use.html
index 6f15221..5e98f45 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/client/internal/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.client.internal (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/AuthData.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/AuthData.html
index d62877c..15586c4 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/AuthData.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/AuthData.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>AuthData (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.EncryptionKey.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.EncryptionKey.html
index 3282a60..44ed70c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.EncryptionKey.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.EncryptionKey.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>EncryptionContext.EncryptionKey (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.html
index 0617af1..83cd402 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/EncryptionContext.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>EncryptionContext (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/AuthData.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/AuthData.html
index 69cc9e6..def6abb 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/AuthData.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/AuthData.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.api.AuthData (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.EncryptionKey.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.EncryptionKey.html
index 087356c..51dd2f7 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.EncryptionKey.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.EncryptionKey.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.api.EncryptionContext.EncryptionKey (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.html
index 82e3858..e64a7c6 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/class-use/EncryptionContext.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.api.EncryptionContext (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-frame.html
index 1e8fd15..0d516c9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-summary.html
index cb0bdf8..c741c5f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-tree.html
index 879a994..52c6c28 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.api Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-use.html
index 2e718bd..6733753 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/api/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.common.api (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.LimitedPrivate.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.LimitedPrivate.html
index a41f33b..d549c2e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.LimitedPrivate.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.LimitedPrivate.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceAudience.LimitedPrivate (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Private.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Private.html
index 8071344..e4c45d8 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Private.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Private.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceAudience.Private (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Public.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Public.html
index 84985ac..d98c751 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Public.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.Public.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceAudience.Public (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.html
index 2e7c478..fd31801 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceAudience.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceAudience (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Evolving.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Evolving.html
index bf12fc5..10e2193 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Evolving.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Evolving.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceStability.Evolving (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Stable.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Stable.html
index 54caa7b..7345c67 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Stable.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Stable.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceStability.Stable (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Unstable.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Unstable.html
index 56b536c..8ea1437 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Unstable.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.Unstable.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceStability.Unstable (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.html
index 656d2d2..013ae2d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/InterfaceStability.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>InterfaceStability (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.LimitedPrivate.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.LimitedPrivate.html
index 6af803a..bbb06ac 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.LimitedPrivate.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.LimitedPrivate.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceAudience.LimitedPrivate (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Private.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Private.html
index 90b62f9..1f7095f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Private.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Private.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceAudience.Private (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Public.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Public.html
index 97ca72f..21cd89ac 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Public.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.Public.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceAudience.Public (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.html
index a7e53c4..9a7fb05 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceAudience.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceAudience (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Evolving.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Evolving.html
index 6fb036c..ec0fa83 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Evolving.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Evolving.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceStability.Evolving (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Stable.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Stable.html
index b31c772..11f1e47 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Stable.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Stable.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceStability.Stable (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Unstable.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Unstable.html
index 67674f5..63d66a1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Unstable.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.Unstable.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceStability.Unstable (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.html
index a0f9831..0067af8 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/class-use/InterfaceStability.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.classification.InterfaceStability (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-frame.html
index 5119082..aa3e51f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.classification (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-summary.html
index 6267bad..ab2555d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.classification (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-tree.html
index 9e1d91d..bf1b003 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.classification Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-use.html
index c767aa9..af3d431 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/classification/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.common.classification (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.KeyValueDecoder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.KeyValueDecoder.html
index 6569a22..09a448c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.KeyValueDecoder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.KeyValueDecoder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeyValue.KeyValueDecoder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.html
index a2568a9..ddb473a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValue.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeyValue (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValueEncodingType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValueEncodingType.html
index 8e81e41..0d9517f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValueEncodingType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/KeyValueEncodingType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>KeyValueEncodingType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfo.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfo.html
index 983c076..69a102a 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfo.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfo.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaInfo (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfoWithVersion.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfoWithVersion.html
index 549f3f0..c290ab9 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfoWithVersion.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaInfoWithVersion.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaInfoWithVersion (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaType.html
index 3c40144..9aa08a3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/SchemaType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:27 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:19 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SchemaType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.KeyValueDecoder.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.KeyValueDecoder.html
index c61f5ea..cf2980e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.KeyValueDecoder.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.KeyValueDecoder.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Interface org.apache.pulsar.common.schema.KeyValue.KeyValueDecoder (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.html
index 37910b3..51026c3 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValue.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.schema.KeyValue (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValueEncodingType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValueEncodingType.html
index 6dc3993..70c2e78 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValueEncodingType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/KeyValueEncodingType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.schema.KeyValueEncodingType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfo.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfo.html
index 7c1a24e..354378d 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfo.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfo.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.schema.SchemaInfo (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfoWithVersion.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfoWithVersion.html
index c16f524..836e0dc 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfoWithVersion.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaInfoWithVersion.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.schema.SchemaInfoWithVersion (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaType.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaType.html
index 222caac..9a8c400 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaType.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/class-use/SchemaType.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Class org.apache.pulsar.common.schema.SchemaType (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-frame.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-frame.html
index 6403a0a..b653d3e 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-summary.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-summary.html
index 95e0f8c..3140249 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-tree.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-tree.html
index 7edaaf0..25c61c1 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>org.apache.pulsar.common.schema Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-use.html b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-use.html
index 5be8f60..549ee20 100644
--- a/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-use.html
+++ b/content/api/client/2.8.0-SNAPSHOT/org/apache/pulsar/common/schema/package-use.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Uses of Package org.apache.pulsar.common.schema (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/overview-frame.html b/content/api/client/2.8.0-SNAPSHOT/overview-frame.html
index 3f19c21..823ce30 100644
--- a/content/api/client/2.8.0-SNAPSHOT/overview-frame.html
+++ b/content/api/client/2.8.0-SNAPSHOT/overview-frame.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Overview List (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/overview-summary.html b/content/api/client/2.8.0-SNAPSHOT/overview-summary.html
index 81883fd..7f032bf 100644
--- a/content/api/client/2.8.0-SNAPSHOT/overview-summary.html
+++ b/content/api/client/2.8.0-SNAPSHOT/overview-summary.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Overview (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/overview-tree.html b/content/api/client/2.8.0-SNAPSHOT/overview-tree.html
index 7fd6d4b..b8f675f 100644
--- a/content/api/client/2.8.0-SNAPSHOT/overview-tree.html
+++ b/content/api/client/2.8.0-SNAPSHOT/overview-tree.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:29 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Class Hierarchy (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/client/2.8.0-SNAPSHOT/serialized-form.html b/content/api/client/2.8.0-SNAPSHOT/serialized-form.html
index d85348f..bd1350c 100644
--- a/content/api/client/2.8.0-SNAPSHOT/serialized-form.html
+++ b/content/api/client/2.8.0-SNAPSHOT/serialized-form.html
@@ -2,7 +2,7 @@
<!-- NewPage -->
<html lang="en">
<head>
-<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 00:38:28 UTC 2021 -->
+<!-- Generated by javadoc (1.8.0_232) on Mon Jan 11 06:33:20 UTC 2021 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Serialized Form (Pulsar Client :: API 2.8.0-SNAPSHOT API)</title>
<meta name="date" content="2021-01-11">
diff --git a/content/api/python/2.8.0-SNAPSHOT/index.html b/content/api/python/2.8.0-SNAPSHOT/index.html
index e483625..4e79265 100644
--- a/content/api/python/2.8.0-SNAPSHOT/index.html
+++ b/content/api/python/2.8.0-SNAPSHOT/index.html
@@ -3579,7 +3579,7 @@ producers and consumers.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.create_producer">
- <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe38b710>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
+ <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddca710>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
</div>
@@ -3789,7 +3789,7 @@ batched into single batch message:
<div class="item">
<div class="name def" id="pulsar.Client.create_reader">
- <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe396dd0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False)</p>
+ <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddd5dd0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False)</p>
</div>
@@ -3968,7 +3968,7 @@ instances directly on a particular partition.
<div class="item">
<div class="name def" id="pulsar.Client.subscribe">
- <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe396d50>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
+ <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddd5d50>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
</div>
diff --git a/content/api/python/index.html b/content/api/python/index.html
index e483625..4e79265 100644
--- a/content/api/python/index.html
+++ b/content/api/python/index.html
@@ -3579,7 +3579,7 @@ producers and consumers.</p></div>
<div class="item">
<div class="name def" id="pulsar.Client.create_producer">
- <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe38b710>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
+ <p>def <span class="ident">create_producer</span>(</p><p>self, topic, producer_name=None, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddca710>, initial_sequence_id=None, send_timeout_millis=30000, compression_type=_pulsar.CompressionType.NONE, max_pending_messages=1000, max_pending_messages_across_partitions=50000, block_if_queue_full=False, batching_enabled=False, batching_max_messages=1000, batching_max_allowed_size_in_bytes=131072, batching_max_publish_delay_ms [...]
</div>
@@ -3789,7 +3789,7 @@ batched into single batch message:
<div class="item">
<div class="name def" id="pulsar.Client.create_reader">
- <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe396dd0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False)</p>
+ <p>def <span class="ident">create_reader</span>(</p><p>self, topic, start_message_id, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddd5dd0>, reader_listener=None, receiver_queue_size=1000, reader_name=None, subscription_role_prefix=None, is_read_compacted=False)</p>
</div>
@@ -3968,7 +3968,7 @@ instances directly on a particular partition.
<div class="item">
<div class="name def" id="pulsar.Client.subscribe">
- <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7f45fe396d50>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
+ <p>def <span class="ident">subscribe</span>(</p><p>self, topic, subscription_name, consumer_type=_pulsar.ConsumerType.Exclusive, schema=<pulsar.schema.schema.BytesSchema object at 0x7fc89ddd5d50>, message_listener=None, receiver_queue_size=1000, max_total_receiver_queue_size_across_partitions=50000, consumer_name=None, unacked_messages_timeout_ms=None, broker_consumer_stats_cache_time_ms=30000, negative_ack_redelivery_delay_ms=60000, is_read_compacted=False, properties=None, pa [...]
</div>
diff --git a/content/docs/en/2.6.0/concepts-messaging.html b/content/docs/en/2.6.0/concepts-messaging.html
index 056b7f5..5edefaa 100644
--- a/content/docs/en/2.6.0/concepts-messaging.html
+++ b/content/docs/en/2.6.0/concepts-messaging.html
@@ -150,8 +150,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,17 +159,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -202,7 +202,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -238,8 +238,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>.
+<p><strong>No need to explicitly create new topics</strong>
+You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -248,8 +248,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions:</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong>
+There is a lot of flexibility in how to combine subscriptions:</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive)</li>
<li>If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared)</li>
@@ -273,8 +273,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -284,11 +284,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -304,8 +305,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/en/2.6.0/concepts-messaging/index.html b/content/docs/en/2.6.0/concepts-messaging/index.html
index 056b7f5..5edefaa 100644
--- a/content/docs/en/2.6.0/concepts-messaging/index.html
+++ b/content/docs/en/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,17 +159,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -202,7 +202,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -238,8 +238,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>.
+<p><strong>No need to explicitly create new topics</strong>
+You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -248,8 +248,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions:</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong>
+There is a lot of flexibility in how to combine subscriptions:</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive)</li>
<li>If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared)</li>
@@ -273,8 +273,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -284,11 +284,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -304,8 +305,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/en/2.6.1/concepts-messaging.html b/content/docs/en/2.6.1/concepts-messaging.html
index a0137ff..1e68700 100644
--- a/content/docs/en/2.6.1/concepts-messaging.html
+++ b/content/docs/en/2.6.1/concepts-messaging.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -289,8 +289,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -300,11 +300,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -320,8 +321,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -482,7 +483,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/2.6.1/concepts-messaging/index.html b/content/docs/en/2.6.1/concepts-messaging/index.html
index a0137ff..1e68700 100644
--- a/content/docs/en/2.6.1/concepts-messaging/index.html
+++ b/content/docs/en/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -289,8 +289,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -300,11 +300,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -320,8 +321,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -482,7 +483,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/2.6.2/concepts-messaging.html b/content/docs/en/2.6.2/concepts-messaging.html
index 9ed96b5..3f3c568 100644
--- a/content/docs/en/2.6.2/concepts-messaging.html
+++ b/content/docs/en/2.6.2/concepts-messaging.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -289,8 +289,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -300,11 +300,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -320,8 +321,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -482,7 +483,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/2.6.2/concepts-messaging/index.html b/content/docs/en/2.6.2/concepts-messaging/index.html
index 9ed96b5..3f3c568 100644
--- a/content/docs/en/2.6.2/concepts-messaging/index.html
+++ b/content/docs/en/2.6.2/concepts-messaging/index.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -289,8 +289,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -300,11 +300,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -320,8 +321,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -482,7 +483,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/concepts-messaging.html b/content/docs/en/concepts-messaging.html
index 161b0ed..8f39ff8 100644
--- a/content/docs/en/concepts-messaging.html
+++ b/content/docs/en/concepts-messaging.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -291,8 +291,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -302,11 +302,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -322,8 +323,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -484,7 +485,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/concepts-messaging/index.html b/content/docs/en/concepts-messaging/index.html
index 161b0ed..8f39ff8 100644
--- a/content/docs/en/concepts-messaging/index.html
+++ b/content/docs/en/concepts-messaging/index.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -291,8 +291,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -302,11 +302,12 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
-<li>You need to specify a key or orderingKey for messages</li>
+<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
+<li>Your producers should disable batching or use a key-based batch builder.</li>
</ul>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
@@ -322,8 +323,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -484,7 +485,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/next/concepts-messaging.html b/content/docs/en/next/concepts-messaging.html
index 233c4c7..dbcde69 100644
--- a/content/docs/en/next/concepts-messaging.html
+++ b/content/docs/en/next/concepts-messaging.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -291,8 +291,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -302,8 +302,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
@@ -323,8 +323,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -485,7 +485,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/en/next/concepts-messaging/index.html b/content/docs/en/next/concepts-messaging/index.html
index 233c4c7..dbcde69 100644
--- a/content/docs/en/next/concepts-messaging/index.html
+++ b/content/docs/en/next/concepts-messaging/index.html
@@ -166,8 +166,8 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong>
+Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,17 +175,17 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note
+<p><strong>Note</strong>
If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -218,7 +218,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -254,8 +254,8 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
+<p><strong>No need to explicitly create new topics</strong>
+You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically.
If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-namespace</code> namespace of the <code>my-tenant</code> tenant.</p>
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
@@ -264,8 +264,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly.</p>
+<p><strong>Pub-Sub or Queuing</strong>
+In Pulsar, you can use different subscriptions flexibly.</p>
<ul>
<li>If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode.</li>
<li>If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared).</li>
@@ -291,8 +291,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that:</p>
+<p><strong>Limitations of shared mode</strong>
+When using shared mode, be aware that:</p>
<ul>
<li>Message ordering is not guaranteed.</li>
<li>You cannot use cumulative acknowledgment with shared mode.</li>
@@ -302,8 +302,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that:</p>
+<p><strong>Limitations of Key_Shared mode</strong>
+When you use Key_Shared mode, be aware that:</p>
<ul>
<li>You need to specify a key or orderingKey for messages.</li>
<li>You cannot use cumulative acknowledgment with Key_Shared mode.</li>
@@ -323,8 +323,8 @@ If no tenant or namespace is specified when a client creates a topic, the topic
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong>
+When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -485,7 +485,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/en/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/en/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/2.6.0/concepts-messaging.html b/content/docs/fr/2.6.0/concepts-messaging.html
index 22f96b0..25e07fc 100644
--- a/content/docs/fr/2.6.0/concepts-messaging.html
+++ b/content/docs/fr/2.6.0/concepts-messaging.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/fr/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/fr/2.6.0/concepts-messaging/index.html b/content/docs/fr/2.6.0/concepts-messaging/index.html
index 22f96b0..25e07fc 100644
--- a/content/docs/fr/2.6.0/concepts-messaging/index.html
+++ b/content/docs/fr/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/fr/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/fr/2.6.1/concepts-messaging.html b/content/docs/fr/2.6.1/concepts-messaging.html
index 9285229..eaeeefc 100644
--- a/content/docs/fr/2.6.1/concepts-messaging.html
+++ b/content/docs/fr/2.6.1/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/2.6.1/concepts-messaging/index.html b/content/docs/fr/2.6.1/concepts-messaging/index.html
index 9285229..eaeeefc 100644
--- a/content/docs/fr/2.6.1/concepts-messaging/index.html
+++ b/content/docs/fr/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/2.6.2/concepts-messaging.html b/content/docs/fr/2.6.2/concepts-messaging.html
index 58a1ee5..6459e5a 100644
--- a/content/docs/fr/2.6.2/concepts-messaging.html
+++ b/content/docs/fr/2.6.2/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/2.6.2/concepts-messaging/index.html b/content/docs/fr/2.6.2/concepts-messaging/index.html
index 58a1ee5..6459e5a 100644
--- a/content/docs/fr/2.6.2/concepts-messaging/index.html
+++ b/content/docs/fr/2.6.2/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/concepts-messaging.html b/content/docs/fr/concepts-messaging.html
index 8a5bbdc..c9f25a5 100644
--- a/content/docs/fr/concepts-messaging.html
+++ b/content/docs/fr/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/concepts-messaging/index.html b/content/docs/fr/concepts-messaging/index.html
index 8a5bbdc..c9f25a5 100644
--- a/content/docs/fr/concepts-messaging/index.html
+++ b/content/docs/fr/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/next/concepts-messaging.html b/content/docs/fr/next/concepts-messaging.html
index ccb435a..d9f474d 100644
--- a/content/docs/fr/next/concepts-messaging.html
+++ b/content/docs/fr/next/concepts-messaging.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/fr/next/concepts-messaging/index.html b/content/docs/fr/next/concepts-messaging/index.html
index ccb435a..d9f474d 100644
--- a/content/docs/fr/next/concepts-messaging/index.html
+++ b/content/docs/fr/next/concepts-messaging/index.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="espaces-de-nommage"></a><a href="#espaces-de-nommage" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/fr/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/fr/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/fr/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/2.6.0/concepts-messaging.html b/content/docs/ja/2.6.0/concepts-messaging.html
index fc823e2..ecc9d09 100644
--- a/content/docs/ja/2.6.0/concepts-messaging.html
+++ b/content/docs/ja/2.6.0/concepts-messaging.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/ja/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/ja/2.6.0/concepts-messaging/index.html b/content/docs/ja/2.6.0/concepts-messaging/index.html
index fc823e2..ecc9d09 100644
--- a/content/docs/ja/2.6.0/concepts-messaging/index.html
+++ b/content/docs/ja/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/ja/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/ja/2.6.1/concepts-messaging.html b/content/docs/ja/2.6.1/concepts-messaging.html
index c5c58e2..8b25325 100644
--- a/content/docs/ja/2.6.1/concepts-messaging.html
+++ b/content/docs/ja/2.6.1/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/2.6.1/concepts-messaging/index.html b/content/docs/ja/2.6.1/concepts-messaging/index.html
index c5c58e2..8b25325 100644
--- a/content/docs/ja/2.6.1/concepts-messaging/index.html
+++ b/content/docs/ja/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/2.6.2/concepts-messaging.html b/content/docs/ja/2.6.2/concepts-messaging.html
index 2e040e7..28c5610 100644
--- a/content/docs/ja/2.6.2/concepts-messaging.html
+++ b/content/docs/ja/2.6.2/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/2.6.2/concepts-messaging/index.html b/content/docs/ja/2.6.2/concepts-messaging/index.html
index 2e040e7..28c5610 100644
--- a/content/docs/ja/2.6.2/concepts-messaging/index.html
+++ b/content/docs/ja/2.6.2/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings">< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/concepts-messaging.html b/content/docs/ja/concepts-messaging.html
index a91450b..f4fa2c8 100644
--- a/content/docs/ja/concepts-messaging.html
+++ b/content/docs/ja/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href=" [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href=" [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/concepts-messaging/index.html b/content/docs/ja/concepts-messaging/index.html
index a91450b..f4fa2c8 100644
--- a/content/docs/ja/concepts-messaging/index.html
+++ b/content/docs/ja/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href=" [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href=" [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/next/concepts-messaging.html b/content/docs/ja/next/concepts-messaging.html
index 0804d3e..a2014b2 100644
--- a/content/docs/ja/next/concepts-messaging.html
+++ b/content/docs/ja/next/concepts-messaging.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/next/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/next/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ja/next/concepts-messaging/index.html b/content/docs/ja/next/concepts-messaging/index.html
index 0804d3e..a2014b2 100644
--- a/content/docs/ja/next/concepts-messaging/index.html
+++ b/content/docs/ja/next/concepts-messaging/index.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="negative-acknowledgement"></a><a href="#negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="acknowledgement-timeout"></a><a href="#acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="dead-letter-topic"></a><a href="#dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2- [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ja/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/next/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ja/next/concepts-overview"><span class="arrow-prev">← </span><span>概要</span></a><a class="docs-next button" href="/docs/ja/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/2.6.0/concepts-messaging.html b/content/docs/ko/2.6.0/concepts-messaging.html
index 856383d..3281ae2 100644
--- a/content/docs/ko/2.6.0/concepts-messaging.html
+++ b/content/docs/ko/2.6.0/concepts-messaging.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>배치 작업이 활성화되면, 같은 배치 내의 다른 메시지들이 소비자에게 다시 재전달 될 수 있으며, 부정적인 알림 메시지도 전달될 수 있다.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>배치 작업이 활성화되면, 같은 배치 내의 다른 메시지들이 소비자에게 재전달될 뿐 아니라, 비승인된 메시지도 재전달 될 수 있다.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/ko/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. 펄사에는 네 가지 사용 가능한 구독 모드가 있다. <a href="#exclusive">배타적 모드</a>, <a href="#shared">공유 모드</a>, <a href="#failover">장애극복 모드</a> 그리고 <a href="#key_shared">키 공유 모드</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-큐잉-또는-pub-sub큐잉-동시허용-옵션"></a><a href="#pub-sub-큐잉-또는-pub-sub큐잉-동시허용-옵션" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
-<p>구독을 조합하여 사용하는 방법은 매우 다양하다. * 전형적인 소비자 간 "팬아웃 pub-sub 메시징"을 하고 싶다면, 각 소비자에게 고유한 구독 명칭(배타적 모드) 을 부여할 수 있다. * 소비자 간 "메시지 큐잉"을 하고 싶다면, 여러 소비자에게 동일한 구독 명칭(공유 모드, 장애극복 모드, 키 공유 모드) 을 부여할 수 있다. * 두 가지를 동시에 허용하고 싶다면, 일부 소비자는 배타적인 구독 모드로 설정하고 나머지 소비자는 다른 모드로 설정하면 된다.</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>키 공유 모드를 사용할 때 주의할 점은 다음과 같다: * 메시지를 사용하기 위해 키(key) 나 순서키(orderingKey) 를 설정할 필요가 있다. * 키 공유 모드에서 누적적인 알림을 사용할 수는 없다.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/ko/2.6.0/concepts-messaging/index.html b/content/docs/ko/2.6.0/concepts-messaging/index.html
index 856383d..3281ae2 100644
--- a/content/docs/ko/2.6.0/concepts-messaging/index.html
+++ b/content/docs/ko/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>배치 작업이 활성화되면, 같은 배치 내의 다른 메시지들이 소비자에게 다시 재전달 될 수 있으며, 부정적인 알림 메시지도 전달될 수 있다.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>배치 작업이 활성화되면, 같은 배치 내의 다른 메시지들이 소비자에게 재전달될 뿐 아니라, 비승인된 메시지도 재전달 될 수 있다.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/ko/2.6.0/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create [...]
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. 펄사에는 네 가지 사용 가능한 구독 모드가 있다. <a href="#exclusive">배타적 모드</a>, <a href="#shared">공유 모드</a>, <a href="#failover">장애극복 모드</a> 그리고 <a href="#key_shared">키 공유 모드</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-큐잉-또는-pub-sub큐잉-동시허용-옵션"></a><a href="#pub-sub-큐잉-또는-pub-sub큐잉-동시허용-옵션" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
-<p>구독을 조합하여 사용하는 방법은 매우 다양하다. * 전형적인 소비자 간 "팬아웃 pub-sub 메시징"을 하고 싶다면, 각 소비자에게 고유한 구독 명칭(배타적 모드) 을 부여할 수 있다. * 소비자 간 "메시지 큐잉"을 하고 싶다면, 여러 소비자에게 동일한 구독 명칭(공유 모드, 장애극복 모드, 키 공유 모드) 을 부여할 수 있다. * 두 가지를 동시에 허용하고 싶다면, 일부 소비자는 배타적인 구독 모드로 설정하고 나머지 소비자는 다른 모드로 설정하면 된다.</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>키 공유 모드를 사용할 때 주의할 점은 다음과 같다: * 메시지를 사용하기 위해 키(key) 나 순서키(orderingKey) 를 설정할 필요가 있다. * 키 공유 모드에서 누적적인 알림을 사용할 수는 없다.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/ko/2.6.1/concepts-messaging.html b/content/docs/ko/2.6.1/concepts-messaging.html
index fcfcfbe..53d0730 100644
--- a/content/docs/ko/2.6.1/concepts-messaging.html
+++ b/content/docs/ko/2.6.1/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/2.6.1/concepts-messaging/index.html b/content/docs/ko/2.6.1/concepts-messaging/index.html
index fcfcfbe..53d0730 100644
--- a/content/docs/ko/2.6.1/concepts-messaging/index.html
+++ b/content/docs/ko/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/2.6.1/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/2.6.2/concepts-messaging.html b/content/docs/ko/2.6.2/concepts-messaging.html
index 5f36738..b3ea96e 100644
--- a/content/docs/ko/2.6.2/concepts-messaging.html
+++ b/content/docs/ko/2.6.2/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/2.6.2/concepts-messaging/index.html b/content/docs/ko/2.6.2/concepts-messaging/index.html
index 5f36738..b3ea96e 100644
--- a/content/docs/ko/2.6.2/concepts-messaging/index.html
+++ b/content/docs/ko/2.6.2/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/2.6.2/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/2.6.2/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headi [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/concepts-messaging.html b/content/docs/ko/concepts-messaging.html
index c398214..ba303b2 100644
--- a/content/docs/ko/concepts-messaging.html
+++ b/content/docs/ko/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/concepts-messaging/index.html b/content/docs/ko/concepts-messaging/index.html
index c398214..ba303b2 100644
--- a/content/docs/ko/concepts-messaging/index.html
+++ b/content/docs/ko/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any numbe [...]
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ delayedDeliveryTickTimeMillis=<span class="hljs-number">1000</span>
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/next/concepts-messaging.html b/content/docs/ko/next/concepts-messaging.html
index b00a5f9..d7ddcac 100644
--- a/content/docs/ko/next/concepts-messaging.html
+++ b/content/docs/ko/next/concepts-messaging.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/ko/next/concepts-messaging/index.html b/content/docs/ko/next/concepts-messaging/index.html
index b00a5f9..d7ddcac 100644
--- a/content/docs/ko/next/concepts-messaging/index.html
+++ b/content/docs/ko/next/concepts-messaging/index.html
@@ -161,8 +161,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="부정적-알림"></a><a href="#부정적-알림" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -170,13 +169,13 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="알림-타임아웃"></a><a href="#알림-타임아웃" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
-<p>Note<br>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알림은 더 정확하게 각 독립 메시지의 재전송을 통제하며, 메시지의 처리 시간이 알림 타임아웃 시간을 초과하였을 때에 유효하지 않은 재전송을 사전에 피할 수 있다.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="데드-레터-토픽"></a><a href="#데드-레터-토픽" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 [...]
@@ -209,7 +208,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 부정적인 알
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -245,8 +244,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="네임스페이스"></a><a href="#네임스페이스" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2. [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/ko/next/admin-api-namespaces#create">admin API</a>. For instance, a tenant with different applications can create a separate namespace for each application. A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any [...]
@@ -254,8 +252,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="Subscription modes"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -276,15 +273,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="키-공유-모드"></a><a href="#키-공유-모드" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1- [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>키 공유 모드의 구독을 비활성화 하기 위해서는 <code>broker.config</code> 파일을 수정하면 된다.</strong></p>
@@ -299,8 +294,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -459,7 +453,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// 설정된 지연 간격 대로 전송될 메시지</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/ko/next/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/ko/next/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-heading [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.0/concepts-messaging.html b/content/docs/zh-CN/2.6.0/concepts-messaging.html
index 66f7e86..b0a6bb3 100644
--- a/content/docs/zh-CN/2.6.0/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.0/concepts-messaging.html
@@ -150,8 +150,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>注意：如果开启批处理，在确认取消后，同一批中的其他消息都会被重新发送给 Consumer。</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>注意: 如果启用批处理，同一批次中的其他消息就跟未确认消息一样可能会重新发送给消费者。</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>你并不需要显式的创建topic。 如果客户端尝试从一个还不存在的topic写或者接受消息，pulsar将会按在<a href="#topics">topic名称</a>提供的<a href="#namespaces">namespace</a>下自动创建topic。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. 如果客户端尝试从一个还不存在的topic写或者接受消息，pulsar将会按在<a href="#topics">topic名称</a>提供的<a href="#namespaces">namespace</a>下自动创建topic。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. < [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 一个租户可以通过<a href="/docs/zh-CN/2.6.0/admin-api-namespaces#create">admin API</a>创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有 4 种可用的订阅模式： <a href="#exclusive">独占（exclusive）</a>， <a href="#shared">共享（shared）</a>，<a href="#failover">灾备（failover）</a>和 <a href="#key_shared">键共享（key_shared）</a>。 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="订阅-发布，队列，亦或两者都是"></a><a href="#订阅-发布，队列，亦或两者都是" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 [...]
-<p>订阅可以灵活组合出很多可能性：<br/> - 如果你想实现传统的 “发布-订阅消息”形式 ，你可以让每个消费者都有一个唯一的订阅名称（独占）<br/> - 如果你想实现传统的“消息队列” 形式，可以使多个消费者使用同一个的订阅名称（共享、灾备、键共享）<br/> - 如果你想同时做到这两点，你可以让一些消费者使用独占方式，剩余消费者使用其他方式。</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>使用 Key_Shared 模式时需要注意两点：</br> * 需要为消息指定一个 key 或 orderingKey</br> * Key_Shared 模式不能使用累积确认</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.6.0/concepts-messaging/index.html b/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
index 66f7e86..b0a6bb3 100644
--- a/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>注意：如果开启批处理，在确认取消后，同一批中的其他消息都会被重新发送给 Consumer。</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>注意: 如果启用批处理，同一批次中的其他消息就跟未确认消息一样可能会重新发送给消费者。</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>你并不需要显式的创建topic。 如果客户端尝试从一个还不存在的topic写或者接受消息，pulsar将会按在<a href="#topics">topic名称</a>提供的<a href="#namespaces">namespace</a>下自动创建topic。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. 如果客户端尝试从一个还不存在的topic写或者接受消息，pulsar将会按在<a href="#topics">topic名称</a>提供的<a href="#namespaces">namespace</a>下自动创建topic。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. < [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 一个租户可以通过<a href="/docs/zh-CN/2.6.0/admin-api-namespaces#create">admin API</a>创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有 4 种可用的订阅模式： <a href="#exclusive">独占（exclusive）</a>， <a href="#shared">共享（shared）</a>，<a href="#failover">灾备（failover）</a>和 <a href="#key_shared">键共享（key_shared）</a>。 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="订阅-发布，队列，亦或两者都是"></a><a href="#订阅-发布，队列，亦或两者都是" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 [...]
-<p>订阅可以灵活组合出很多可能性：<br/> - 如果你想实现传统的 “发布-订阅消息”形式 ，你可以让每个消费者都有一个唯一的订阅名称（独占）<br/> - 如果你想实现传统的“消息队列” 形式，可以使多个消费者使用同一个的订阅名称（共享、灾备、键共享）<br/> - 如果你想同时做到这两点，你可以让一些消费者使用独占方式，剩余消费者使用其他方式。</p>
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. 如果多于一个消费者尝试以同样方式去订阅主题，消费者将会收到错误。</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>使用 Key_Shared 模式时需要注意两点：</br> * 需要为消息指定一个 key 或 orderingKey</br> * Key_Shared 模式不能使用累积确认</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多主题时，Pulsar客户端会自动调用Pulsar的API来发现匹配表达式或者列表的所有topic，然后全部订阅。 如果此时有暂不存在的topic，那么一旦这些topic被创建，conusmer会自动订阅。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>下面是多主题订阅在java中的例子：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-CN/2.6.1/concepts-messaging.html b/content/docs/zh-CN/2.6.1/concepts-messaging.html
index fec94f5..cbdd9d1 100644
--- a/content/docs/zh-CN/2.6.1/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.1/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/2.6.1/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.1/concepts-messaging/index.html b/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
index fec94f5..cbdd9d1 100644
--- a/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/2.6.1/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.1/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.2/concepts-messaging.html b/content/docs/zh-CN/2.6.2/concepts-messaging.html
index b227103..4879343 100644
--- a/content/docs/zh-CN/2.6.2/concepts-messaging.html
+++ b/content/docs/zh-CN/2.6.2/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/2.6.2/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/2.6.2/concepts-messaging/index.html b/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
index b227103..4879343 100644
--- a/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
+++ b/content/docs/zh-CN/2.6.2/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/2.6.2/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -464,7 +458,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/2.6.2/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/2.6.2/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li>< [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/concepts-messaging.html b/content/docs/zh-CN/concepts-messaging.html
index 6cec45a..339d15a 100644
--- a/content/docs/zh-CN/concepts-messaging.html
+++ b/content/docs/zh-CN/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href="#发送模 [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href="#发送模 [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/concepts-messaging/index.html b/content/docs/zh-CN/concepts-messaging/index.html
index 6cec45a..339d15a 100644
--- a/content/docs/zh-CN/concepts-messaging/index.html
+++ b/content/docs/zh-CN/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -175,15 +174,15 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. 确认取消是
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -283,15 +280,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>当你使用 key 共享模式时，需要知道如下两点： * 你需要为每条消息指定一个key或者orderingKey。 * 你不能在 key 共享模式里面使用累积确认。</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -306,8 +301,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -466,7 +460,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href="#发送模 [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc-headings"><li><a href="#发送模 [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/next/concepts-messaging.html b/content/docs/zh-CN/next/concepts-messaging.html
index db065ec..395f650 100644
--- a/content/docs/zh-CN/next/concepts-messaging.html
+++ b/content/docs/zh-CN/next/concepts-messaging.html
@@ -162,8 +162,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -171,14 +170,14 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
-<p>注意<br>
-尽量使用取消确认，而不要使用确认超时。 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
+Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>Dead letter topic enables you to consume new messages when some messages cannot be consumed successfully by a consumer. In this mechanism, messages that are failed to be consumed are stored in a separate topic, which is called dead letter topic. You can decide how to handle messages in the dead letter topic.</p>
@@ -210,7 +209,7 @@
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -246,8 +245,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/next/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -255,8 +253,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -277,15 +274,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p><em>shared</em>或者<em>round robin</em>模式中，多个消费者可以绑定到同一个订阅上。 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>当使用共享模式时，需要知道如下两点: * 消息是没办法保证有序的。 * 你不能在共享模式里面使用累积消费。</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -300,8 +295,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -460,7 +454,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/next/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#消息">消息</a></li><li><a href="#producer">Producer</a><ul class="toc-headings"><li><a href="#发送模式">发 [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/next/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#消息">消息</a></li><li><a href="#producer">Producer</a><ul class="toc-headings"><li><a href="#发送模式">发 [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-CN/next/concepts-messaging/index.html b/content/docs/zh-CN/next/concepts-messaging/index.html
index db065ec..395f650 100644
--- a/content/docs/zh-CN/next/concepts-messaging/index.html
+++ b/content/docs/zh-CN/next/concepts-messaging/index.html
@@ -162,8 +162,7 @@
<li>累积确认模式 累积确认时，消费者只需要确认最后一条他收到的消息。 所有之前（包含此条）的消息，都不会被再次发送给那个消费者。</li>
</ul>
<blockquote>
-<p>Note</p>
-<p><a href="#subscription-modes">共享消费模式</a>不能使用累积确认模式 。因为共享订阅模式会多个消费者共享一个订阅。 在共享订阅模式，消息都是单条确认模式。</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. 在共享订阅模式，消息都是单条确认模式。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="取消确认"></a><a href="#取消确认" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>当消费者在某个时间没有成功的消费某条消息，消费者想重新消费到这条消息，这个消费者可以发送一条取消确认消息到 broker，broker 会将这条消息重新发给消费者。</p>
@@ -171,14 +170,14 @@
<p>在独占消费模式和灾备订阅模式中，消费者仅仅只能对收到的最后一条消息进行取消确认。</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次里面收到取消确认的消息和其他消息。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="确认超时"></a><a href="#确认超时" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>如果消息没有被成功消费，你想去让 broker 自动重新交付这个消息， 你可以采用未确认消息自动重新交付机制。 客户端会跟踪 <code>超时</code> 时间范围内所有未确认的消息。 并且在指定超时时间后会发送一个 <code>重发未确认的消息</code> 请求到 broker。</p>
<blockquote>
-<p>备注 如果启用批处理，消费者会在同一批次收到未知消息和其他消息。</p>
-<p>注意<br>
-尽量使用取消确认，而不要使用确认超时。 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> <br>
+Prefer negative acknowledgements over acknowledgement timeout. 确认取消是以更高的精度在控制单条消息的重新传递。当消息处理时间超过确认超时时间时，要避免无效的消息重传。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主题"></a><a href="#死信主题" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>Dead letter topic enables you to consume new messages when some messages cannot be consumed successfully by a consumer. In this mechanism, messages that are failed to be consumed are stored in a separate topic, which is called dead letter topic. You can decide how to handle messages in the dead letter topic.</p>
@@ -210,7 +209,7 @@
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -246,8 +245,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="不需要显式的创建topic"></a><a href="#不需要显式的创建topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>在Pulsar中不需要主动去创建主题。 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-namespace/my-topic</code> means the <code>my-topic</code> topic is created in the <code>my-name [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. 如果客户端尝试从不存在的主题当中生产消息或消费消息，Pulsar 将会自动使用该<a href="#topics">主题名称</a>在该命名空间下创建同名的主题。 If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my-namespace/my-topic</code>. <code>persistent://my-tenant/my-nam [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="命名空间"></a><a href="#命名空间" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
<p>命名空间是租户内部逻辑上的命名术语。 可以通过<a href="/docs/zh-CN/next/admin-api-namespaces#create">admin API</a>在租户下创建多个命名空间。 例如，包含多个应用程序的租户可以为每个应用程序创建单独的命名空间。 Namespace使得程序可以以层级的方式创建和管理topic Topic<code>my-tenant/app1</code> ，它的namespace是<code>app1</code>这个应用，对应的租户是 <code>my-tenant</code>。 你可以在namespace下创建任意数量的<a href="#topics">topic</a>。</p>
@@ -255,8 +253,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>订阅是命名好的配置规则，指导消息如何投递给消费者。 Pulsar 中有四种订阅模式: <a href="#exclusive">独占</a>，<a href="#shared">共享</a>，<a href="#failover">灾备</a>和<a href="#key_shared">key共享</a> 下图展示了这三种模式：</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="订阅模型"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="发布-订阅-或者-队列"></a><a href="#发布-订阅-或者-队列" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>在Pulsar当中，你可以灵活的使用不同的订阅方式。 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. 如果你想在消费者当中使用传统的”发布-订阅消息“，你可以为每个消费者指定一个特定的订阅名称， 这就是独占模式。 如果你想在消费者当中实现”消息队列“的效果，则多个消费者会拥有相同的订阅名称(如共享模式，灾备模式，key共享模式)。 如果你想同时实现两种效果，则可以将订阅模式和其他的订阅模式结合起来使用。</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="consumerless-subscriptions-and-their-corresponding-modes"></a><a href="#consumerless-subscriptions-and-their-corresponding-modes" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.2 [...]
<p>When a subscription has no consumers, its subscription mode is undefined. A subscription's mode is defined when a consumer connects to the subscription, and the mode can be changed by restarting all consumers with a different configuration.</p>
@@ -277,15 +274,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p><em>shared</em>或者<em>round robin</em>模式中，多个消费者可以绑定到同一个订阅上。 消息通过round robin轮询机制分发给不同的消费者，并且每个消息仅会被分发给一个消费者。 当消费者断开连接，所有被发送给他，但没有被确认的消息将被重新安排，分发给其它存活的消费者。</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="shared模式的限制"></a><a href="#shared模式的限制" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42 [...]
-<p>当使用共享模式时，需要知道如下两点: * 消息是没办法保证有序的。 * 你不能在共享模式里面使用累积消费。</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="共享订阅"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>可以在 <code>broker.config</code> 中禁用 Key_Shared 模式。</strong></p>
@@ -300,8 +295,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>当订阅多个主题的时候，Pulsar 客户端将自动调用 Pulsar API 找到符合匹配规则的主题列表，然后订阅这些主题。 如果此时有暂不存在的主题，那么一旦这些主题被创建，消费者会自动订阅这些主题。</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>如下是 Java 订阅多个主题的代码示例：</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -460,7 +454,7 @@ delayedDeliveryTickTimeMillis=1000
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/next/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#消息">消息</a></li><li><a href="#producer">Producer</a><ul class="toc-headings"><li><a href="#发送模式">发 [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-CN/next/concepts-overview"><span class="arrow-prev">← </span><span>概述</span></a><a class="docs-next button" href="/docs/zh-CN/next/concepts-architecture-overview"><span>架构</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#消息">消息</a></li><li><a href="#producer">Producer</a><ul class="toc-headings"><li><a href="#发送模式">发 [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-TW/2.6.0/concepts-messaging.html b/content/docs/zh-TW/2.6.0/concepts-messaging.html
index f8742de..7009ea2 100644
--- a/content/docs/zh-TW/2.6.0/concepts-messaging.html
+++ b/content/docs/zh-TW/2.6.0/concepts-messaging.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="否定回覆-negative-acknowledgement"></a><a href="#否定回覆-negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="確認超時-acknowledgement-timeout"></a><a href="#確認超時-acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主題-dead-letter-topic"></a><a href="#死信主題-dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/zh-TW/2.6.0/admin-api-namespaces#create">admin API</a>. 例如，一個對接多個應用的租戶，可以為每個應用創建不同的namespace。 A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any number of <a href="#topics">topics</a> under the namespace.</p>
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="訂閱模式"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-TW/2.6.0/concepts-messaging/index.html b/content/docs/zh-TW/2.6.0/concepts-messaging/index.html
index f8742de..7009ea2 100644
--- a/content/docs/zh-TW/2.6.0/concepts-messaging/index.html
+++ b/content/docs/zh-TW/2.6.0/concepts-messaging/index.html
@@ -150,8 +150,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="note"></a><a href="#note" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6 [...]
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers having access to the same subscription. In the shared subscription mode, messages can be acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="否定回覆-negative-acknowledgement"></a><a href="#否定回覆-negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer can send a negative acknowledgement to the broker, and then the broker will redeliver the message.</p>
@@ -159,15 +158,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they have received.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the negatively acknowledged messages.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="確認超時-acknowledgement-timeout"></a><a href="#確認超時-acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
<p>When a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client will track the unacknowledged messages within the entire <code>acktimeout</code> time range, and send a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
+<p><strong>Note</strong> If batching is enabled, other messages in the same batch may be redelivered to the consumer as well as the unacknowledged messages.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主題-dead-letter-topic"></a><a href="#死信主題-dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -200,7 +199,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -236,8 +235,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <co [...]
+<p><strong>No need to explicitly create new topics</strong> You don't need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar will automatically create that topic under the <a href="#namespaces">namespace</a> provided in the <a href="#topics">topic name</a>. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant can create multiple namespaces via the <a href="/docs/zh-TW/2.6.0/admin-api-namespaces#create">admin API</a>. 例如，一個對接多個應用的租戶，可以為每個應用創建不同的namespace。 A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any number of <a href="#topics">topics</a> under the namespace.</p>
@@ -245,8 +243,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. There are four available subscription modes in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="訂閱模式"></p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="pub-sub-queuing-or-both"></a><a href="#pub-sub-queuing-or-both" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have some consumers with exclusive subscriptions [...]
+<p><strong>Pub-Sub, Queuing, or Both</strong> There is a lot of flexibility in how to combine subscriptions: * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, you can make each consumer have a unique subscription name (exclusive) * If you want to achieve "message queuing" among consumers, you can make multiple consumers have the same subscription name (shared, failover, key_shared) * If you want to do both simultaneously, you can have s [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If more than one consumer attempts to subscribe to a topic using the same subscription, the consumer receives an error.</p>
@@ -265,15 +262,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When using Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -288,8 +283,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client will automatically make a call to the Pulsar API to discover the topics that match the regex pattern/list and then subscribe to all of them. If any of the topics don't currently exist, the consumer will auto-subscribe to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>Here are some multi-topic subscription examples for Java:</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
diff --git a/content/docs/zh-TW/2.6.1/concepts-messaging.html b/content/docs/zh-TW/2.6.1/concepts-messaging.html
index ffd36cc..6fa5334 100644
--- a/content/docs/zh-TW/2.6.1/concepts-messaging.html
+++ b/content/docs/zh-TW/2.6.1/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="否定回覆-negative-acknowledgement"></a><a href="#否定回覆-negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="確認超時-acknowledgement-timeout"></a><a href="#確認超時-acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主題-dead-letter-topic"></a><a href="#死信主題-dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/zh-TW/2.6.1/admin-api-namespaces#create">admin API</a>. 例如，一個對接多個應用的租戶，可以為每個應用創建不同的namespace。 A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any number of <a href="#topics">topics</a> under the namespace.</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="訂閱模式"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -463,7 +457,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-TW/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/zh-TW/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-TW/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/zh-TW/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-TW/2.6.1/concepts-messaging/index.html b/content/docs/zh-TW/2.6.1/concepts-messaging/index.html
index ffd36cc..6fa5334 100644
--- a/content/docs/zh-TW/2.6.1/concepts-messaging/index.html
+++ b/content/docs/zh-TW/2.6.1/concepts-messaging/index.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="否定回覆-negative-acknowledgement"></a><a href="#否定回覆-negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="確認超時-acknowledgement-timeout"></a><a href="#確認超時-acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主題-dead-letter-topic"></a><a href="#死信主題-dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/zh-TW/2.6.1/admin-api-namespaces#create">admin API</a>. 例如，一個對接多個應用的租戶，可以為每個應用創建不同的namespace。 A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any number of <a href="#topics">topics</a> under the namespace.</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="訂閱模式"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-shared-mode"></a><a href="#limitations-of-shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
+<p><strong>Limitations of shared mode</strong> When using shared mode, be aware that: * Message ordering is not guaranteed. * You cannot use cumulative acknowledgment with shared mode.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-shared-subscriptions.png" alt="Shared subscriptions"></p>
<h3><a class="anchor" aria-hidden="true" id="key_shared"></a><a href="#key_shared" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>In <em>Key_Shared</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a distribution across consumers and message with same key or same ordering key are delivered to only one consumer. No matter how many times the message is re-delivered, it is delivered to the same consumer. When a consumer connected or disconnected will cause served consumer change for some key of message.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="limitations-of-key_shared-mode"></a><a href="#limitations-of-key_shared-mode" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<p>When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages * You cannot use cumulative acknowledgment with Key_Shared mode.</p>
+<p><strong>Limitations of Key_Shared mode</strong> When you use Key_Shared mode, be aware that: * You need to specify a key or orderingKey for messages. * You cannot use cumulative acknowledgment with Key_Shared mode. * Your producers should disable batching or use a key-based batch builder.</p>
</blockquote>
<p><img src="/docs/assets/pulsar-key-shared-subscriptions.png" alt="Key_Shared subscriptions"></p>
<p><strong>You can disable Key_Shared subscription in the <code>broker.config</code> file.</strong></p>
@@ -304,8 +299,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</blockquote>
<p>When subscribing to multiple topics, the Pulsar client automatically makes a call to the Pulsar API to discover the topics that match the regex pattern/list, and then subscribe to all of them. If any of the topics do not exist, the consumer auto-subscribes to them once the topics are created.</p>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-ordering-guarantees-across-multiple-topics"></a><a href="#no-ordering-guarantees-across-multiple-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h- [...]
-<p>When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
+<p><strong>No ordering guarantees across multiple topics</strong> When a producer sends messages to a single topic, all messages are guaranteed to be read from that topic in the same order. However, these guarantees do not hold across multiple topics. So when a producer sends message to multiple topics, the order in which messages are read from those topics is not guaranteed to be the same.</p>
</blockquote>
<p>The following are multi-topic subscription examples for Java.</p>
<pre><code class="hljs css language-java"><span class="hljs-keyword">import</span> java.util.regex.Pattern;
@@ -463,7 +457,7 @@ Consumer<<span class="hljs-keyword">byte</span>[]> consumer = client.newCo
<pre><code class="hljs css language-java"><span class="hljs-comment">// message to be delivered at the configured delay interval</span>
producer.newMessage().deliverAfter(<span class="hljs-number">3L</span>, TimeUnit.Minute).value(<span class="hljs-string">"Hello Pulsar!"</span>).send();
</code></pre>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-TW/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/zh-TW/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/zh-TW/2.6.1/concepts-overview"><span class="arrow-prev">← </span><span>Overview</span></a><a class="docs-next button" href="/docs/zh-TW/2.6.1/concepts-architecture-overview"><span>Architecture</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#messages">Messages</a></li><li><a href="#producers">Producers</a><ul class="toc [...]
const community = document.querySelector("a[href='#community']").parentNode;
const communityMenu =
'<li>' +
diff --git a/content/docs/zh-TW/2.6.2/concepts-messaging.html b/content/docs/zh-TW/2.6.2/concepts-messaging.html
index 8fbe7db..11a5308 100644
--- a/content/docs/zh-TW/2.6.2/concepts-messaging.html
+++ b/content/docs/zh-TW/2.6.2/concepts-messaging.html
@@ -166,8 +166,7 @@
<li>Messages are acknowledged cumulatively. With cumulative acknowledgement, the consumer only needs to acknowledge the last message it received. All messages in the stream up to (and including) the provided message are not re-delivered to that consumer.</li>
</ul>
<blockquote>
-<p>Note</p>
-<p>Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
+<p><strong>Note</strong> Cumulative acknowledgement cannot be used in the <a href="#subscription-modes">shared subscription mode</a>, because the shared subscription mode involves multiple consumers who have access to the same subscription. In the shared subscription mode, messages are acknowledged individually.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="否定回覆-negative-acknowledgement"></a><a href="#否定回覆-negative-acknowledgement" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 [...]
<p>When a consumer does not consume a message successfully at a time, and wants to consume the message again, the consumer sends a negative acknowledgement to the broker, and then the broker redelivers the message.</p>
@@ -175,15 +174,15 @@
<p>In the exclusive and failover subscription modes, consumers only negatively acknowledge the last message they receive.</p>
<p>In the shared and Key_Shared subscription modes, you can negatively acknowledge messages individually.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the negatively acknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="確認超時-acknowledgement-timeout"></a><a href="#確認超時-acknowledgement-timeout" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 [...]
<p>If a message is not consumed successfully, and you want to trigger the broker to redeliver the message automatically, you can adopt the unacknowledged message automatic re-delivery mechanism. Client tracks the unacknowledged messages within the entire <code>acktimeout</code> time range, and sends a <code>redeliver unacknowledged messages</code> request to the broker automatically when the acknowledgement timeout is specified.</p>
<blockquote>
-<p>Note If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
+<p><strong>Note</strong> If batching is enabled, other messages and the unacknowledged messages in the same batch are redelivered to the consumer.</p>
</blockquote>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Prefer negative acknowledgements over acknowledgement timeout. Negative acknowledgement controls the re-delivery of individual messages with more precision, and avoids invalid redeliveries when the message processing time exceeds the acknowledgement timeout.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="死信主題-dead-letter-topic"></a><a href="#死信主題-dead-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0 [...]
@@ -216,7 +215,7 @@ Prefer negative acknowledgements over acknowledgement timeout. Negative acknowle
</code></pre>
<p>Dead letter topic depends on message re-delivery. Messages are redelivered either due to <a href="#acknowledgement-timeout">acknowledgement timeout</a> or <a href="#negative-acknowledgement">negative acknowledgement</a>. If you are going to use negative acknowledgement on a message, make sure it is negatively acknowledged before the acknowledgement timeout.</p>
<blockquote>
-<p>Note<br>
+<p><strong>Note</strong> <br>
Currently, dead letter topic is enabled only in the shared subscription mode.</p>
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="retry-letter-topic"></a><a href="#retry-letter-topic" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
@@ -252,8 +251,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
</tbody>
</table>
<blockquote>
-<h4><a class="anchor" aria-hidden="true" id="no-need-to-explicitly-create-new-topics"></a><a href="#no-need-to-explicitly-create-new-topics" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 [...]
-<p>You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenant and namespace, such as <code>persistent://my-tenant/my- [...]
+<p><strong>No need to explicitly create new topics</strong> You do not need to explicitly create topics in Pulsar. If a client attempts to write or receive messages to/from a topic that does not yet exist, Pulsar creates that topic under the namespace provided in the <a href="#topics">topic name</a> automatically. If no tenant or namespace is specified when a client creates a topic, the topic is created in the default tenant and namespace. You can also create a topic in a specified tenan [...]
</blockquote>
<h2><a class="anchor" aria-hidden="true" id="namespaces"></a><a href="#namespaces" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1 [...]
<p>A namespace is a logical nomenclature within a tenant. A tenant creates multiple namespaces via the <a href="/docs/zh-TW/2.6.2/admin-api-namespaces#create">admin API</a>. 例如，一個對接多個應用的租戶，可以為每個應用創建不同的namespace。 A namespace allows the application to create and manage a hierarchy of topics. The topic <code>my-tenant/app1</code> is a namespace for the application <code>app1</code> for <code>my-tenant</code>. You can create any number of <a href="#topics">topics</a> under the namespace.</p>
@@ -261,8 +259,7 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>A subscription is a named configuration rule that determines how messages are delivered to consumers. Four subscription modes are available in Pulsar: <a href="#exclusive">exclusive</a>, <a href="#shared">shared</a>, <a href="#failover">failover</a>, and <a href="#key_shared">key_shared</a>. These modes are illustrated in the figure below.</p>
<p><img src="/docs/assets/pulsar-subscription-modes.png" alt="訂閱模式"></p>
<blockquote>
-<h3><a class="anchor" aria-hidden="true" id="pub-sub-or-queuing"></a><a href="#pub-sub-or-queuing" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22- [...]
-<p>In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, combine exclusive subscription mode wi [...]
+<p><strong>Pub-Sub or Queuing</strong> In Pulsar, you can use different subscriptions flexibly. * If you want to achieve traditional "fan-out pub-sub messaging" among consumers, specify a unique subscription name for each consumer. It is exclusive subscription mode. * If you want to achieve "message queuing" among consumers, share the same subscription name among multiple consumers(shared, failover, key_shared). * If you want to achieve both effects simultaneously, co [...]
</blockquote>
<h3><a class="anchor" aria-hidden="true" id="exclusive"></a><a href="#exclusive" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.6 [...]
<p>In <em>exclusive</em> mode, only a single consumer is allowed to attach to the subscription. If multiple consumers subscribe to a topic using the same subscription, an error occurs.</p>
@@ -281,15 +278,13 @@ Currently, dead letter topic is enabled only in the shared subscription mode.</p
<p>In <em>shared</em> or <em>round robin</em> mode, multiple consumers can attach to the same subscription. Messages are delivered in a round robin distribution across consumers, and any given message is delivered to only one consumer. When a consumer disconnects, all the messages that were sent to it and not acknowledged will be rescheduled for sending to the remaining consumers.</p>
<p>In the diagram below, <strong>Consumer-C-1</strong> and <strong>Consumer-C-2</strong> are able to subscribe to the topic, but <strong>Consumer-C-3</strong> and others could as well.</p>
... 19195 lines suppressed ...