-
Notifications
You must be signed in to change notification settings - Fork 56
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
Getting error when trying to delete: self.db.deleteByQuery is not a function #45
Comments
This is a valid bug, I verified by running tests against v2.x, thanks to @harshadyeola for setting up easy to use docker instructions Ah, dang! Its deprecated in 1.5.3 according to docs |
|
I added a conditional to the It should work as long the This works for me but I don't know if should go on a PR. |
BTW, it only seems appropriate that I thank both:
for their separate and novel approach ... without them my research into a possible resolution would not get as far. |
@juanpujol - I like what you have and I do think it would have made a valid PR, even if there may have been a little bit of back & forth. Right now I'm trying to use https://github.com/arielfr/elastic-deletebyquery to make it work, a bit stuck but let's hope I figure it out as it would be a more complete solution. Also am worried about blocking code but lets see. |
use https://github.com/arielfr/elastic-deletebyquery to bulk delete for destroyAll when working with v2.x of ES
@juanpujol - it is done and released in 1.0.7 of this connector, please take it for a spin and reopen this issue if it is not fixed. Out of the many approaches, I chose to use https://github.com/arielfr/elastic-deletebyquery to make it work which means that scam/scrol is used in tandem with bulk queries to ES v2.x |
@pulkitsinghal sorry it took me so long. I tested and it works, thank you! |
I'm using ElasticSarch 2.1.1 and loopback-connector-elastic-search 1.0.5 and every time I try to delete a record by id I get this error:
An important issue since I'm not able to remove anything.
Thank you.
The text was updated successfully, but these errors were encountered: