opensearch-project / opensearch-project/OpenSearch
Lightweight Elasticsearch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
Our team is developing and supporting a desktop application that can be installed on a wide range of systems from weak to strong and works offline (without internet or any network) in these systems.
The application requires a search engine with all the features of Lucene with an independent language API such as elasticsearch. The search engine should be installed offline with the application in the end-user's system.
Due to the fact that our team has experience in using elasticsearch, the best option to choose is elasticsearch, but elasticsearch is so heavy that it raises many challenges for publishing, installation and use on clients, from its large size for publishing, to the large resources it will occupy in the user's system.
Our suggestion to the OpenSearch development team is that the OpenSearch be published and installed as a core with minimal features and minimum size using minimal system resources, especially RAM. That is, without features such as scalability and resilience (clusters, nodes, and shards) and security, with the smallest size of the bundled JVM (located within the jdk directory of the Elasticsearch home directory), with the ability for user to add the rest of the features to the core if needed.
This will extend the use of OpenSearch to all applications across all operating systems, from desktop to mobile.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points to begin with; first review the OpenSearch packaging and runtime architecture for its bundled JVM and cluster, security, and resilience features. Done would require a defined minimal offline distribution, resource targets, and a validated way to add omitted features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop-dev, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100