Skip to content

IngestDocument cannot find fields that contain "." in the field name #127349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
desean1625 opened this issue Apr 24, 2025 · 2 comments
Closed

IngestDocument cannot find fields that contain "." in the field name #127349

desean1625 opened this issue Apr 24, 2025 · 2 comments
Labels
>bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP needs:triage Requires assignment of a team area label

Comments

@desean1625
Copy link

Elasticsearch Version

8.15.2

Installed Plugins

No response

Java Version

bundled

OS Version

lunix

Problem Description

IngestDocument doesn't resolve field paths the same way as the rest of the system causing ingest pipelines to fail.

Steps to Reproduce

PUT /users/_doc/1?refresh=wait_for
{
  "email": "[email protected]",
  "first_name": "Mardy",
  "last_name": "Brown",
  "city": "New Orleans",
  "county": "Orleans",
  "state": "LA",
  "zip": 70116,
  "web": "mardy.asciidocsmith.com"
}
PUT /_enrich/policy/users-policy
{
  "match": {
    "indices": "users",
    "match_field": "email",
    "enrich_fields": ["first_name", "last_name", "city", "zip", "state"]
  }
}

POST /_enrich/policy/users-policy/_execute

PUT /_ingest/pipeline/user_lookup
{
  "description" : "Enriching user details to messages",
  "processors" : [
    {
      "enrich" : {
        "policy_name": "users-policy",
        "field" : "system1.email",
        "target_field": "user",
        "max_matches": "1"
      }
    }
  ]
}
PUT /my-index-00001/_doc/my_id?pipeline=user_lookup
{
  "system1.email": "[email protected]"
}

Logs (if relevant)

No response

@desean1625 desean1625 added >bug needs:triage Requires assignment of a team area label labels Apr 24, 2025
@gbanasiak
Copy link
Contributor

Thank you for your interest in Elasticsearch. Please try using dot expander processor. We mention the correct way to access flattened objects in here. I'll close this issue. If you run into problems please ask for help in a Discuss post.

@desean1625
Copy link
Author

desean1625 commented Apr 28, 2025

@gbanasiak This doesn't seem to be the best solution, because doing this causes visualizations, anomaly detection, es|ql and many other features to not work. Previous guidance from Elastic has been to flatten all fields.

elastic/kibana#1084

@gbanasiak gbanasiak added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Apr 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP needs:triage Requires assignment of a team area label
Projects
None yet
Development

No branches or pull requests

2 participants