[FEATURE]Loading a ready-made mapping file during the template creation

[YANG-DB]

Is your feature request related to a problem? During the creation of an index template I need to import an existing mapping file to use as the schema for this template.

What solution would you like?

The purpose of this additional functionality is to allow the creation of a schema based (mapping) index (data-stream) using existing mapping files that are present in the plugin as part of the catalog deployment of pre-build schema used in the opensearch - Observability / Security Plugins.

What we need: Adding a load file option button for loading a ready made mapping file from the file system.

if the file contains composed templates (which do not already exist in the cluster) - the prompt will ask the user if he would like to load the components templates

For example the Logs mapping file that has inner composition of component templates

• Http component template
• Cloud component template
• Communication component template

All these inner compositions relationships are explained and detailed in the catalog config for in the Observability schema

Functionality:

• Loading mapping template from file
• if contains inner component templates
  • verify if they already exist
  • allow selecting them from file location so they can be created

Do you have any additional context?

• https://github.com/opensearch-project/opensearch-catalog/tree/main/docs/schema
• https://github.com/opensearch-project/opensearch-catalog/tree/main/schema/observability
• https://github.com/opensearch-project/opensearch-catalog/blob/main/schema/observability/logs/logs.mapping

[kamingleung]

@YANG-DB Can't we achieve this by associating the pre-canned component templates to a template? We can associate component templates to a template on the UI since 2.7.

[YANG-DB]

Actually the use case is that we want to generate the entire scope of both the index mapping including the component mapping that are referenced in that index mapping. We want this to be automated and not manually adding each component template

See the next logs.mapping example:

 },
  "composed_of": [
    "http_template",
    "communication_template"
  ],

This would prompt the dialog to load the component templates from the file system (folder?) And once the user select the folder all the depended component templates would be generated and the whole index template would also be generated without the user manually creating each components by himself

The main point here is to automate the entire index mapping hierarchy without the user having to manually create each part (component / index)

Another think to take into consideration is that index mapping may be subject for changes (versioning) so this also has to come into account in the template table UX

[kamingleung]

@YANG-DB I would like to clarify some of the points in this proposal, which may differ from the current create template workflow.

When you mentioned importing a mapping file to a template, does it: a) attach/associate component templates (containing mappings) to the template the user is creating or b) import the mapping structures into the template the user is creating without attaching/associating component templates?

[dblock]

[Triage -- attendees 1, 2, 3, 4, 5, 6, 7]

Looks like a reasonable proposal.