Anonymitaet commented on a change in pull request #13336:
URL: https://github.com/apache/pulsar/pull/13336#discussion_r770311619
##########
File path: site2/docs/reference-configuration.md
##########
@@ -354,6 +354,8 @@ brokerServiceCompactionThresholdInBytes|If the estimated
backlog size is greater
| managedLedgerInfoCompressionType | Compression type of managed ledger
information. <br><br>Available options are `NONE`, `LZ4`, `ZLIB`, `ZSTD`, and
`SNAPPY`). <br><br>If this value is `NONE` or invalid, the `managedLedgerInfo`
is not compressed. <br><br>**Note** that after enabling this configuration, if
you want to degrade a broker, you need to change the value to `NONE` and make
sure all ledger metadata is saved without compression. | None |
| additionalServlets | Additional servlet name. <br><br>If you have multiple
additional servlets, separate them by commas. <br><br>For example,
additionalServlet_1, additionalServlet_2 | N/A |
| additionalServletDirectory | Location of broker additional servlet NAR
directory | ./brokerAdditionalServlet |
+brokerEntryMetadataInterceptors | Set broker entry metadata interceptors.<br
/><br />Multiple interceptors should be separated by commas. <br /><br
/>Available
values:<li>org.apache.pulsar.common.intercept.AppendBrokerTimestampMetadataInterceptor</li><li>org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor</li>
<br /><br />Example<br
/>brokerEntryMetadataInterceptors=org.apache.pulsar.common.intercept.AppendBrokerTimestampMetadataInterceptor,
org.apache.pulsar.common.intercept.AppendIndexMetadataInterceptor|N/A
+enableExposingBrokerEntryMetadataToClient|Whether to expose broker entry
metadata to client or not.<br /><br />Available
values:<li>true</li><li>false</li><br />Example<br
/>enableExposingBrokerEntryMetadataToClient=true | false
Review comment:
OK, I've updated, PTAL
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
