Skip to content

ESQL: support for mapping-unavailable fields#140146

Closed
bpintea wants to merge 38 commits intoelastic:mainfrom
bpintea:feat/set_unmapped_nullify_load
Closed

ESQL: support for mapping-unavailable fields#140146
bpintea wants to merge 38 commits intoelastic:mainfrom
bpintea:feat/set_unmapped_nullify_load

Conversation

@bpintea
Copy link
Contributor

@bpintea bpintea commented Jan 4, 2026

WIP

bpintea and others added 30 commits December 12, 2025 01:05
This will allow re-evaluating the output past a RENAME/DROP/KEEP, once
an unmapping field is injected.
elasticsearchmachine and others added 7 commits January 2, 2026 06:29
@github-actions
Copy link
Contributor

github-actions bot commented Jan 4, 2026

ℹ️ 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?

@bpintea
Copy link
Contributor Author

bpintea commented Jan 19, 2026

Superseded by #139417 (and eventually #140463).

@bpintea bpintea closed this Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants