Skip to content

Commit c5fe5d5

Browse files
(AzureCXP) fixes MicrosoftDocs/azure-docs#362540
Updated line number 10. From:Log compaction is a way of retaining data in Event Hubs using event key based retention. By default, each event hub/Kafka topic is created with time-based retention or the *delete* cleanup policy, where events are purged upon the expiration of the retention time. Rather using coarser-grained time based retention, you can use event key-based retention mechanism where Event Hubs retrains the last known value for each event key of an event hub or a Kafka topic. To: Log compaction is a way of retaining data in Event Hubs using event key based retention. By default, each event hub/Kafka topic is created with time-based retention or the *delete* cleanup policy, where events are purged upon the expiration of the retention time. Rather using coarser-grained time based retention, you can use event key-based retention mechanism where Event Hubs retains the last known value for each event key of an event hub or a Kafka topic.
1 parent 9034d3b commit c5fe5d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/event-hubs/log-compaction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.date: 05/18/2023
77

88
# Log compaction in Azure Event Hubs
99

10-
Log compaction is a way of retaining data in Event Hubs using event key based retention. By default, each event hub/Kafka topic is created with time-based retention or the *delete* cleanup policy, where events are purged upon the expiration of the retention time. Rather using coarser-grained time based retention, you can use event key-based retention mechanism where Event Hubs retrains the last known value for each event key of an event hub or a Kafka topic.
10+
Log compaction is a way of retaining data in Event Hubs using event key based retention. By default, each event hub/Kafka topic is created with time-based retention or the *delete* cleanup policy, where events are purged upon the expiration of the retention time. Rather using coarser-grained time based retention, you can use event key-based retention mechanism where Event Hubs retains the last known value for each event key of an event hub or a Kafka topic.
1111

1212
> [!NOTE]
1313
> Log compaction feature isn't supported in the * **basic** tier.

0 commit comments

Comments
 (0)