Data import plugin

[ruchidh]

Description

The Data Importer plugin for OpenSearch Dashboards provides a user-friendly interface for uploading and indexing data files into OpenSearch. This plugin supports various file formats, including CSV, JSON, and NDJSON, and offers several key features:

File Upload and Parsing:
Users can upload data files in CSV, JSON, or NDJSON formats.
The plugin parses the uploaded files and displays a preview of the data.

Index Management:
Users can specify the index name where the data should be stored.
The plugin fetches and displays existing indices, allowing users to select or create a new index.

Field Mapping:
The plugin automatically detects the schema of the uploaded data and maps the fields accordingly.

Cluster Selection:
Users can select the cluster where the data should be indexed (if applicable).

Notifications:
The plugin provides success and error notifications to inform users about the status of their data upload and indexing operations.

Preview and Load More:

Users can preview the uploaded data and load more rows as needed.
Overall, the Data Importer plugin simplifies the process of uploading and indexing data into OpenSearch, making it accessible to users with varying levels of technical expertise

Screenshot

Testing the changes

• yarn start

Descriptions following the prefixes must be 100 characters long or less
-->

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Changelog Entry Missing Hyphen

Changelog entries must begin with a hyphen (-).

[github-actions]

❌ Invalid Changelog Heading

The '## Changelog' heading in your PR description is either missing or malformed. Please make sure that your PR description includes a '## Changelog' heading with proper spelling, capitalization, spacing, and Markdown syntax.

[Flyingliuhub]

Do you have an RFC for this change? It seems similar to @huyaboo's proposal and implementation week ago: #9199

[zhongnansu]

@ruchidh A new plugin in OSD core definitely needs a feature request RFC. If you take a look at all big features, they all come with RFC first, and we include lots of them into the codebase as well. The transparent process is important, because it's an opportunity that developers can discuss, gather feedback, and build a solution that can really benefit the open source community

I suggest reaching out to the RFC owner to get involved in the discussion first, to come up with fundamental requirements and then collaborate with him #9199