Replies: 1 comment 1 reply
-
Is https://github.com/meilisearch/MeiliSearch/issues/1436 also planned for Q3? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As you may know, we have been working on the new version 0.21 of the engine for quite some time. We have started to iterate on a release candidate that you can now test. We have made a blog post about it if you want to know more.
It's time to think about the future and move forward. That's why I'd like to give you more visibility on what we have planned for the third quarter of 2021.
We have set some clear goals for Q3 🎯.
Our first goal is to reduce what some of you have called deal-breakers when it comes to choosing MeiliSearch. We will therefore devote a maximum of our efforts to these two subjects in order to improve the search experience for you and your users by being able to manage more use-cases with MeiliSearch.
Our second goal is to start building a guide-line to facilitate future developments and upgrades of the API. This goal will also allow us to improve the developer experience to make it easier for you to use the API. We will tackle this problem block by block to move towards a 1.0 stable version.
Finally, we are aware that there are still things to improve to reduce indexing times. We have decided to take advantage of Q3 to iterate on this subject directly after the release of v0.21. In order to accomplish this objective, we will also provide two new formats to index your documents in MeiliSearch. We will add the support of CSV and NDJSON files for indexing.
If we summarize what we have just seen, here is a list of objectives and associated steps.
Reduce deal-breakers
Stabilize the API format block by block until v1.0.
Patch Indexing speed
You can visualize it on the dedicated Public Core Roadmap project page.
Thank you for your reading ✌️
Beta Was this translation helpful? Give feedback.
All reactions