opensearch-project / opensearch-project/data-prepper

Feature Request: View/Dump All Metadata Associated with OpenSearch Records

Open
#5,338 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Java
Stars
374
Forks
354
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Is your feature request related to a problem? Please describe.
In OpenSearch. Currently, users have to explicitly know or keep track of any metadata to use it when working with records in OpenSearch. This makes it difficult to access and utilize important information about how records were sourced, processed, and sinked to OpenSearch.

Describe the solution you'd like
Implement a feature that allows users to easily view or dump all metadata associated with a record in OpenSearch. This should include information about how the record was sourced, processed, and sinked to OpenSearch. The solution should provide a simple and intuitive way to access this metadata without requiring users to manually track or remember specific metadata fields.

Additional context

This feature would greatly improve the traceability and auditability of data in OpenSearch. It would be particularly useful for debugging, data lineage tracking, and ensuring compliance with data governance policies. The ability to easily access and view all metadata associated with a record would enhance the overall usability and value of the OpenSearch system for data management and analysis tasks.

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no files, tests, or entry points. Start by tracing how records are sourced, processed, and sent to OpenSearch, then define an approach for exposing all associated metadata; done means users can view or dump that metadata for a record.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
data-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.