[BUG]Covering index not present inside query

[YANG-DB]

What is the bug?

Query on S3 based data after defining a covering index doesn’t use the covering index during the execution ...

How to Reproduce
Created the next query based on the next table:

Table

"CREATE EXTERNAL TABLE mys3.default.http_logs (
   `@timestamp` TIMESTAMP,
    clientip STRING,
    request STRING, 
    status INT, 
    size INT, 
    year INT, 
    month INT, 
    day INT) 
USING json PARTITIONED BY(year, month, day) OPTIONS (path 's3://flint-data-dp-eu-west-1-beta/data/http_log/http_logs_partitioned_json_bz2/', compression 'bzip2')"

Covering Index

CREATE INDEX status_and_day
ON mys3.default.http_logs ( status, day )
WITH (
  auto_refresh = true,
  refresh_interval = '1 minute',
  checkpoint_location = 's3://flint-data-dp-eu-west-1-beta/data/http_log/checkpoint_status_and_day'
)

Query

SELECT
    day,
    status
FROM mys3.default.http_logs
WHERE status >= 400
GROUP BY day, status
LIMIT 100;

Explain Query

-- Explain:
== Physical Plan ==
AdaptiveSparkPlan isFinalPlan=false
+- CollectLimit 100
 +- HashAggregate(keys=[day#107, status#103], functions=[])
 +- Exchange hashpartitioning(day#107, status#103, 1000), ENSURE_REQUIREMENTS, [plan_id=75]
 +- HashAggregate(keys=[day#107, status#103], functions=[])
 +- Project [status#103, day#107]
 +- Filter (isnotnull(status#103) AND (status#103 >= 400))
 +- FileScan json default.http_logs[status#103,year#105,month#106,day#107] Batched: false, DataFilters: [isnotnull(status#103), (status#103 >= 400)], Format: JSON, Location: CatalogFileIndex(1 paths)[s3://flint-data-dp-eu-west-1-beta/data/http_log/http_logs_partitioned_j..., PartitionFilters: [], PushedFilters: [IsNotNull(status), GreaterThanOrEqual(status,400)], ReadSchema: struct<status:int>

What is the expected behavior?
I'm expecting the covering index rule to kick in and be part of the physical execution plan

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.

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

[dai-chen]

@YANG-DB Thanks for reporting the issue! Same as #103, covering index/MV is only available in OpenSearch and thus no query rewrite support for now.