Forum Discussion

pmscorca's avatar
pmscorca
Icon for Post Prodigy rankPost Prodigy
1 year ago
Solved

Issue creating a KQL materialized view

Hi, I'm testing an eventstream that reads source events from an Azure Event Hubs and write them into a KQL table. I've created successfully a KQL materialized view (using summarize and arg_max clau...
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi pmscorca ,

     

    It might have seemed like the `async` keyword wasn't required, but for backfill operations, it is mandatory to ensure the process runs in the background without blocking other operations.

    When you use the `.create async materialized-view` command, an `OperationId` is generated. You can monitor the progress of this operation using the `.show operations` command. If the materialized view doesn't appear immediately, it might still be processing, especially if the dataset is large.

     

    Here's a step-by-step approach to troubleshoot and resolve your issues:

    1. Verify Async Creation:

    ```kql
    .create async materialized-view with (backfill=true) mymaterview on table mytable {
    mytable
    | summarize arg_max(Timestamp, *) by KeyColumn
    }
    ```

    2. Monitor the Operation:

    ```kql
    .show operations
    ```

    3. Make sure the new materialized view name is unique and doesn't conflict with other database objects.

    Create materialized view - Kusto | Microsoft Learn

     

    Best Regards,

    Neeko Tang

    If this post  helps, then please consider Accept it as the solution  to help the other members find it more quickly.