[v1.0-rc/bug] "No mapping found for [XXXLast30DaysFeature] in order to sort on" and "Sort criterion field XXXLast30DaysFeature was not found in any entity spec to be searched" errors with new UI

[Masterchen09]

Describe the bug

When opening the home page with the new UI multiple requests for the search query getSearchResultsForMultiple are performed for the dashboard and dataset entity types with different filters and sort criterions.

The requests in the UI are returning the typical DataFetchingException:

{
    "errors": [
        {
            "message": "An unknown error occurred.",
            "locations": [
                {
                    "line": 2,
                    "column": 3
                }
            ],
            "path": [
                "searchAcrossEntities"
            ],
            "extensions": {
                "code": 500,
                "type": "SERVER_ERROR",
                "classification": "DataFetchingException"
            }
        }
    ],
    "data": {
        "searchAcrossEntities": null
    },
    "extensions": {}
}

While the log of the GMS gives us the underlying issue: datahub-datahub-gms-64cf46d4c8-g6kcg_datahub-gms.log
(Note: I have removed everything from the log which is not directly related to the issue.)

No mapping found for [XXX] in order to sort on
Sort criterion field XXX was not found in any entity spec to be searched

It seems the corresponding fields are missing for the OSS GMS:

DASHBOARD -> viewCountLast30DaysFeature
DATASET -> usageCountLast30DaysFeature, uniqueUserCountLast30DaysFeature and writeCountLast30DaysFeature

While the corresponding time-series aspects contains the fields (viewCount, usageCount, uniqueUserCount and writeCount), I am not sure how these fields in the aspects are related to the "*Last30DaysFeature" - I was only able to find references to them in the UI: E.g. https://github.com/search?q=repo%3Adatahub-project%2Fdatahub%20writeCountLast30DaysFeature&type=code

To Reproduce
Steps to reproduce the behavior:

1. Open the home page.
2. Check the network monitor and logs of the GMS.

Expected behavior
Either the requests should not be performed in DataHub OSS or the corresponding fields must be implemented for the OSS GMS.

Screenshots and/or Screen Recordings
n/a

System details (please complete the following information):

• v1.0.0 -> We have updated the affected (sandbox) instance from 0.15.0.1, 1.0.0-rc1, 1.0.0-rc2, ... with all 1.0.-rc versions - not sure whether this is related to the issue (i.e. that a necessary system update step was not performed if you have used any specific 1.0.-rc versions before)
• We are using OpenSearch 2.11.0 instead of Elasticsearch - I don't think this is related to the issue, but as it affects the search this information could be useful...

Additional context
n/a

[jakobhanna]

Can see the same behaviour

[rafaelsmf]

I'm facing the same issue.

{"error":{"root_cause":[{"type":"query_shard_exception","reason":"No mapping found for [usageCountLast30DaysFeature] in order to sort on","index":"datasetindex_v2","index_uuid":"XXX"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"can_match","grouped":true,"failed_shards":[{"shard":0,"index":"datasetindex_v2","node":"XXX","reason":{"type":"query_shard_exception","reason":"No mapping found for [usageCountLast30DaysFeature] in order to sort on","index":"datasetindex_v2","index_uuid":"XXX"}}]},"status":400}