Skip to content

[9.3] ESQL: Enable nullify and fail unmapped resolution in tech-preview (#140528)#140657

Merged
elasticsearchmachine merged 5 commits intoelastic:9.3from
GalLalouche:feat/set_unmapped_nullify_keyword_tp_93
Jan 15, 2026
Merged

[9.3] ESQL: Enable nullify and fail unmapped resolution in tech-preview (#140528)#140657
elasticsearchmachine merged 5 commits intoelastic:9.3from
GalLalouche:feat/set_unmapped_nullify_keyword_tp_93

Conversation

@GalLalouche
Copy link
Contributor

@GalLalouche GalLalouche commented Jan 14, 2026

Manual backport of #140528 to 9.3.

Also backports the test fix #140554.

…astic#140528)

This PR removes the snapshot protection of FAIL and NULLIFY options for unmapped fields (only LOAD remains protected under snapshot).

Follow up to elastic#140463.
Related: elastic#138888.
@GalLalouche GalLalouche added >feature backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) :Analytics/ES|QL AKA ESQL v9.3.0 labels Jan 14, 2026
@GalLalouche GalLalouche added the ES|QL-ui Impacts ES|QL UI label Jan 14, 2026
@GalLalouche GalLalouche removed the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Jan 14, 2026
@alex-spies alex-spies removed the v9.3.1 label Jan 14, 2026
@alex-spies alex-spies changed the title [9.3] ESQL: Enable nullify and fail unmapped resolution in tech-preview (#140463) [9.3] ESQL: Enable nullify and fail unmapped resolution in tech-preview (#140528) Jan 14, 2026
@alex-spies alex-spies added test-release Trigger CI checks against release build Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) and removed ES|QL-ui Impacts ES|QL UI labels Jan 14, 2026
@github-actions
Copy link
Contributor

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

@alex-spies alex-spies self-assigned this Jan 15, 2026
@GalLalouche GalLalouche enabled auto-merge (squash) January 15, 2026 09:50
@GalLalouche GalLalouche disabled auto-merge January 15, 2026 09:50
@GalLalouche GalLalouche enabled auto-merge (squash) January 15, 2026 09:50
@elasticsearchmachine elasticsearchmachine merged commit 1c0c250 into elastic:9.3 Jan 15, 2026
37 checks passed
@GalLalouche GalLalouche deleted the feat/set_unmapped_nullify_keyword_tp_93 branch January 15, 2026 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >feature Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) test-release Trigger CI checks against release build v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants