-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch files for nmslib and faiss creating enforcing compilation to happen during cmake #1552
Comments
@navneet1v yeah - I have noticed this. I have been building lib once locally then commenting out in gradle. |
+1 I am commenting the patch apply code in CMakeList.txt, as I got frustrated with build times. I cannot remove buildJni task as I needed changed in the C++ code. I tried added --cached in the
|
@navneet1v tried this and it was failing to pick up source in the file:
|
I think we might be able to do:
ref: https://stackoverflow.com/questions/48167884/check-if-git-apply-was-already-applied |
This worked for me: https://gist.github.com/jmazanec15/a4cab0b6944e8e4b403c43a2113a5a4b. Ill raise a PR at some point. It is a little messy as of now. |
will wait for the PR. I looked into that commands |
Problem
To enable features in Faiss and Nmslib there are 2 patch files which have been added in k-NN repo. The patches gets applied while running
cmake
or gradle taskcmakeJniLib
(nmslib, faiss).Due to this the cmake command assumes that files have changed and it leads recompile the files and dependent files leading to increase in running of all the gradle tasks like integTest, test, run etc.
This really adds significant time during development process as you might have to run the tests/integTest task multiple times. This is not a problem for CIs and actual opensearch build process because it builds the k-NN plugin only once.
Solution
The text was updated successfully, but these errors were encountered: