Skip to content

Commit 63ad0be

Browse files
authored
preview & not eligible for support
1 parent d1a376f commit 63ad0be

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/event-hubs/log-compaction.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,12 @@ ms.custom: ignite-2022
1111
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 *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.
1212

1313
> [!NOTE]
14+
> This feature is currently in Preview.
1415
> Log compaction feature is available only in **premium** and **dedicated** tiers.
1516
17+
> [!WARNING]
18+
> Use of the Log Compaction feature is **not eligible for product support through Microsoft Azure**.
19+
1620
As shown below, an event log (of an event hub partition) may have multiple events with the same key. If you're using a compacted event hub, then Event Hubs service will take care of purging old events and only keeping the latest events of a given event key.
1721

1822
:::image type="content" source="./media/event-hubs-log-compaction/log-compaction.png" alt-text="Diagram showing how a topic gets compacted." lightbox="./media/event-hubs-resource-governance-overview/app-groups.png":::

0 commit comments

Comments
 (0)