Adds method to unset last response in Client

[acya-skulskaya]

I have a kafka consumer, which works as a demon. Manticore client is initialized one time at start. This consumer adds documents to manticore in bulk, say 100-200Mb at a time. I have noticed a memory leak, it increases every time the consumer adds documents to manticore. Turns out manticore client doesn't clean the lastResponse property after I execute $index->addDocuments($documents); - it is understandable that one may need this response later, but it also increases memory usage by ~200Mb for each running demon in my case, which is important when you have 20 of these demons running at the same time. So i have found that unsetting the lastResponse property each time after I add documents solves this memory leak problem

[sanikolaev]

Thanks for the PR @acya-skulskaya
Can you please improve it, so it passes the tests?

[acya-skulskaya]

Thanks for the PR @acya-skulskaya Can you please improve it, so it passes the tests?

Hi, sorry I didn't have time yesterday to finish fixing the tests.
But the issue with failing tests doesn't seem to be connected with my changes? First it was showing that InsertTest was failing because the response had key table instead of _index - my guess it is because tests were written for a different version of manticoresearch?
I have updated my fork with today's release, but the tests are still failing all the same.
Also have tried to specify a previous version of manticoresearch in CI, but it didn't help with the tests.
I just really don't understand how adding a small method to manually unset a property could cause all these tests to be failing? And they seem to be failing because they expect completely different data in responses?

[sanikolaev]

@Nick-S-2018 pls review the PR and help with the failing tests.