Forum Discussion
Issues related to Policy implementation in KQL
I am also facing the same issue, for my implementation.
Community SupportHi ALOK_YADAV
Thanks for reaching out to Fabric community forum.
The execution time varies based on factors such as the dataset size, cluster load, and ingestion frequency.
Generally, policies like the Merge Extent Policy can take anywhere from a few minutes to several hours, depending on the above datasets. For large datasets, it may take longer.
For additional information you can refer the docs :
1. Merge Policy : Extents merge policy - Kusto | Microsoft Learn
2. Partician Policy : Partitioning policy - Kusto | Microsoft Learn
3. Policies : Policies overview - Kusto | Microsoft Learn
If this post was helpful, please consider marking Accept as solution to assist other members in finding it more easily.
If you continue to face issues, feel free to reach out to us for further assistance!
The execution time varies based on factors such as the dataset size, cluster load, and ingestion frequency.
lets take one example if i have 5TB datast size then how much time it takes to execute the policies. I want in general way because its so confusion to check the policies are exceuted or not.
- v-aatheeque
Hi ALOK_YADAV
The execution time varies based on factors like dataset size, cluster load, and ingestion frequency.
For example, if you have 5TB of data, the time it takes to execute policies depends on several factors, such as the complexity of the policies, the system's capacity, and network conditions. While it's difficult to provide an exact time without specific details about the environment and the policies being executed.
Thanks for using Microsoft Fabric Community.
