[Derived Fields] Derived fields integration with Dashboards

[rishabhmaurya]

Is your feature request related to a problem? Please describe.

Derived Fields is a new feature to be introduced in OpenSearch 2.15. RFC: https://github.com/opensearch-project/OpenSearch/issues/1133 Meta Task: https://github.com/opensearch-project/OpenSearch/issues/12281 We would like to add its suport in OpenSearch Dashboards so that they can be defined and accessed for search, fetch and highlight features.

Describe the solution you'd like Just like we have support for "Script Fields", we would also like to add support for "Derived Fields", so that they are available for search, fetch and highlight from dashboard.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

[BionIT]

Hi @rishabhmaurya , are we targeting to make change for this issue in 2.15 or 2.16?

[rishabhmaurya]

@BionIT this is for 2.16

[rishabhmaurya]

@BionIT could we assign it to someone and prioritize it for 2.16. Here is the documentation of the feature, let me know if you need any clarification.

[seraphjiang]

@rishabhmaurya would you elaborate a little bit more what what is the feature and what are the functionality. the RFC looks more like backend feature requirement. it is unclear what feature or enhancement need at opensearch dashboards side. Once we have more clear understand what we need for opensearch dashboards, we may ask ux team's help to create a few mock up to understand the user experience and scope of work without write any code.

[smacrakis]

@rishabhmaurya -- you say "We would like to add its suport in OpenSearch Dashboards so that they can be defined and accessed for search, fetch and highlight features." Could you please list the touchpoints that need to be updated? Do we have a list of places where Fields in general or Script Fields in particular can be used?

[rishabhmaurya]

1. When defining index pattern, just like "scripted field", there should a tab for derived fields to define/list/edit derived fields against an index/index pattern. Internally, it should create derived fields mappings against index and it should support all parameters defined against the API here. I have created following "script field" for illustration:
   

2. Support on discover page: just like "script fields" are shown in available/popular fields section, derived fields should be shown here as well.

3. Similarly on dashboard page, derived fields should be made available to select them as part of dashboard.