Data Modeling Search/Aggregates Not Refreshing

The fix has been applied and indexing has resumed. We are currently monitoring the state of the fix at this stage.

The fix for the Elasticsearch mapping bug has been deployed to staging and initial results look good. Pending successful staging validation, rollout to production is planned throughout next week. The workaround remains to avoid using JSON keys with shared prefixes and dotted variants.

A bug in the Elasticsearch mapping refresh is causing search and aggregate results to not update for projects using JSON properties where a plain key and a dotted key share a prefix (e.g. "min" and "min.A" in the same JSON object). A first fix was insufficient; a second fix (PR #1908) is now in pipeline and rollout to az-eastus-1 is expected within ~1 week, pending testing.

Example of triggering data pattern:

{
"min": "value",
"min.A": "nested_value"
}


Any JSON property where a plain key (min) and a dotted key (min.A) share the same prefix will trigger the naming collision.
Currently fixing is in progress.

We have identified the cause of an issue affecting Data Modeling search and aggregate results on the az-eastus-1 cluster. This issue is limited to a specific data pattern and does not affect all customers only projects ingesting JSON data where one key is used as a prefix before a dot (.) in another key within the same JSON object are impacted.

Workaround: To avoid triggering this issue, please ensure JSON objects do not contain keys where one key shares a prefix with another key before a dot (.) or end of string. For example, a structure where one key appears as a prefix of another dot-separated key should be avoided.

Our engineering team is actively working on a permanent fix. We will provide further updates as the situation develops.

We are currently investigating an issue where Data Modeling search and aggregate results are not refreshing as expected on the az-eastus-1 cluster. Users may experience incorrect or zero counts in search results, and newly ingested data may not appear in the CDF Search UI. Our engineering team has identified the root cause and a fix is currently in progress. We will provide further updates as the situation develops.