be able to customize es version

[sibelius]

instead of forking, why not enable customization esVersion

is there any block of this?

We are willing to contribute with the fix

[Blankll]

Hi @sibelius , I just refer to this project and created a similar lib as an alternative to it: jest-search, it enables customizable es version and also supports like OpenSearch, and ZincSearch, you can have a try if you want, feel free to raise issues if you get any block when using it, I'm seeking for any feedbacks!

[sibelius]

Can you export startEngine and stopEngine?

[Blankll]

Hi @sibelius , should not be a problem if you want, I am just bit curious your use case, would be great if you could provide me some context of the reason

[sibelius]

Our tests need both mongo and elasticsearch

[Blankll]

Hi @sibelius exported in v1.0.1

[sibelius]

I'm getting this error

ConnectionError: other side closed - Local: ::1:53051, Remote: ::1:9600

[Blankll]

Hi @sibelius thanks for reporting the issue, could you pls pass the env DEBUG=jest-search for instance

"test": "DEBUG='jest-search' jest --runInBand  .....

and send me the printed logs to me? that will help me to diagnose the issues thanks,

and feel free to raise issues in the repo

[sibelius]

we are using "@elastic/elasticsearch": "8.8.0",

[Blankll]

Hi @sibelius the library underline is not rely on any elastic/OpenSearch client , so the version of client should not related, could you provide me:

1. what's the version of elastic search you pass to startEngine
2. will be great if you provide me the logs as I mentioned above
3. the way the client connects to es that started by the library and it only supports HTTP,

and there is an example that you can refer: https://github.com/Blankll/event-search

[sibelius]

do we need runInBand ?

[Blankll]

yes @sibelius

[sibelius]

why ?

[Blankll]

if you use by global setup it is fine to not use runInBand, just make sure the data id u insert to es in different cases are not in conflict,
if you start the server by calling startEngine in *.test.ts, it is possible that the port and some file that elasticsearch relies on like data folder under es folder are getting conflicts since they are using same binary in parallel,

we didn't do sufficient tests on this case, I'd like to know more context for getting rid of runInBand, I can do further tests if it is a commonly requirement

[sibelius]

can you try something like this shelfio/jest-mongodb#209?

create 1 cluster or something per test file ?