[Website]: Context question mark in ingest pipeline example

Open Beginner friendly
#7,906 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
elasticsearch
Domain
documentation

Research direction

Open the linked ingest pipelines documentation page and locate the “Access source fields in a processor” section. Update the example’s condition to remove safe navigation from ctx, then verify that it reads ctx.network.name == 'Guest' and renders correctly.

Written by the indexing model from the issue text.

Description

documentation Team:Developer triaged
Before you submit
  • This issue is about a documentation page, flow, or piece of content.
Type of issue

Inaccurate

What documentation page or section is affected

https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines

What happened?

The example in Access source fields in a processor uses ctx?.network?.name in the if condition.

Expected behavior

Because ctx is always available in an ingest pipeline, the example should not use the safe navigation operator on ctx.

Suggested correction

Update the example to use ctx.network.name == 'Guest'.

Additional info

No response

🤖 Refined by RefineBot on 2026-08-11. Original intent preserved.

RefineBot changes

What changed:

  • Clarified the affected section and the incorrect example behavior.
  • Added an expected-behavior section and a concrete suggested correction.
  • Kept the original page link and issue intent intact.

What was preserved:

  • The issue remains classified as an inaccurate documentation report for the ingest pipelines page.
  • The original report’s focus on the ctx?.network?.name example and its explanation that ctx is always available were retained.

Source: The target docs page was inspected to confirm the example location and wording.

Previous version
Before you submit
  • This issue is about a documentation page, flow, or piece of content.
Type of issue

Inaccurate

What documentation page or section is affected

https://www.elastic.co/docs/manage-data/ingest/transform-enrich/ingest-pipelines

What happened?

Examples show Question Mark on ctx (Context) that value don't need to have a question mark (Safe Navigation Operator) because Context must be always available.

PUT _ingest/pipeline/my-pipeline { "processors": [ { "drop": { "description": "Drop documents with 'network.name' of 'Guest'", "if": "ctx?.network?.name == 'Guest'" } } ] }

Please correct this typo on documentation because it is wrong.

Additional info

No response

TriageBot — Needs refinement
2026-08-11

Type: documentation

Section check:

  • [✅] type of issue
  • [✅] affected page
  • [❌] expected behavior: missing explicit expected wording for the correction

Ambiguity / scope notes:

  • The report says the example is wrong, but the needed correction is implied rather than stated directly.

Cross-references:

  • All referenced links are valid in the accessible repo context.

Next step: Rewritten above

> Generated by [Gh Aw Issue Triage](https://github.com/elastic/docs-content/actions/runs/31513296583) for #7906 · gpt50mini · 5.56 AIC · ⌖ 1.9 AIC · ⊞ 28.6K · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-call-id%3A+elastic%2Fdocs-content%2Fgh-aw-issue-triage%22&type=issues)
Dominant language
No language data
Stars
47
Forks
262
Avg merge
3d 8h
Merged PRs (30d)
127

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/docs-content

All issues in elastic/docs-content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.