[BUG]Create MV fails setting up correctly

[YANG-DB]

What is the bug?
Creation of a MV fails:

CREATE MATERIALIZED VIEW mys3.default.http_countip_distinct_views
AS
  SELECT
    window.start AS `start.time`,
    COUNT(distinct clientip) AS count_hourly_failed_distinct_ip
  FROM mys3.default.http_logs_plain
  WHERE status != 200
  GROUP BY TUMBLE(`@timestamp`, '60 Minutes')
WITH (
  auto_refresh = true,
  refresh_interval = '10 Minutes',
  checkpoint_location = 's3://flint-data-dp-eu-west-1-beta/data/http_log/checkpoint_http_count_view',
  watermark_delay = '10 Minutes'
);

How can one reproduce the bug?
Steps to reproduce the behavior:

Running the next MV creation

CREATE MATERIALIZED VIEW mys3.default.http_countip_distinct_views
AS
  SELECT
    window.start AS `start.time`,
    COUNT(distinct clientip) AS count_hourly_failed_distinct_ip
  FROM mys3.default.http_logs_plain
  WHERE status != 200
  GROUP BY TUMBLE(`@timestamp`, '60 Minutes')
WITH (
  auto_refresh = true,
  refresh_interval = '10 Minutes',
  checkpoint_location = 's3://flint-data-dp-eu-west-1-beta/data/http_log/checkpoint_http_count_view',
  watermark_delay = '10 Minutes'
);

Result in the next error:

{
    "data": {
        "ok": true,
        "resp": {
            "status": "FAILED",
            "error": "Fail to write result, cause: Failed to create Flint index"
        }
    }
}

What is the expected behavior?
Successful create the index and the ETL proccess

Do you have any screenshots?

Do you have any additional context?
Add any other context about the problem.

[dai-chen]

@YANG-DB it would be helpful if you can share more info, such as any error stack in Spark log. Thanks!