This will be the main project roadmap where I'm going to summarize the main functionality we are going to implement and referencing the topics by issues:
1. Elasticsearch connector vagrant box.
2. Travis CI integration.
3. Re-architecting the Elasticsearch Connector so we can easily handle different version of Elasticsearch library and server.
Cleaning up all the deprecated functions from 8.x-1.x branch and drop the support of 8.x-1.x.
Mainly focusing on building easy for porting code from 8.x to 7.x
4. Refactor the 8.x Search API integration with more testable code and port it to 7.x
Comments
Comment #2
skek commentedComment #3
Bojhan commentedI am very curious how well along this is. I am tempted to update to Drupal 8, but I am not sure the elastic search part is ready.
5. Looks far off. I am interested in doing a "live" region where the results of a search would immediately be shown. How realistic is that with the dev branch?
Comment #4
skek commented@Bojhan,
This is the next one in my list because it is a very important feature of the module.
However I'm currently building the Aggregation (facets) abstraction so we can have easily the facets when using the remote reading.
I don't see it very far, but it will requires some work and it will be at least 2-4 weeks.
I will spend some time this weekend on this and will see how fast we can go with the implementation there.
Keep you posted.
Comment #5
skek commentedComment #6
skek commentedComment #7
simon georges commentedI suppose #2754915: Add support for autocompletion of fulltext search terms and #2755295: Add support for attachments could fit in the roadmap as well ;-)
Comment #8
heddnIs this roadmap still being maintained?
Comment #9
xan.ps commentedIt's been some time since this module's active development. I don't think the roadmap is still being maintained.
Comment #10
mparker17As of September 30, 2026...
1. We don't have a Vagrant box specifically, but we do have a very reliable way to set up a test environment with a working Elasticsearch instance.
2. We don't use Travis CI specifically, but we have a good automated testing suite (and lints) in all supported versions of the module that are passing: 8.x-7.x, 8.0.x, and 9.0.x
3. The 8.0.x and 9.0.x branches are architected in such a way that they're running mostly the same code but using different versions of the library to connect to different versions of Elasticsearch
4. The 8.0.x and 9.0.x branches have deep Search API integration
5. The 8.x-7.x, 8.0.x, and 9.0.x have deep integration with Views through their Search API integration
... so for the sake of moving forward, I'm going to close this issue, and recommend that if we want to improve any of these things, we open a smaller, more-actionable ticket for that, which should help keep work scoped and focused.