handle too long response from elasticsearch

return 413 instead of 500 when elasticsearch response is too long and client throws exception

added Azure label

requested review from @nthakur and @ajoshi19

assigned to @msavchuk

Please update the documentation:https://community.opengroup.org/osdu/platform/system/search-service/-/blob/master/docs/tutorial/SearchService.md for this limitation. You can add Known limitations block at the end and mention this.

added 1 commit

• 88cb1d65 - enhance too long response from elasticsearch message

Compare with previous version

added 12 commits

• 88cb1d65...7237ccf0 - 9 commits from branch master
• 2bff5db6 - handle too long response from elasticsearch
• 300ddf27 - enhance too long response from elasticsearch message
• cb6fa0a1 - update notice

Compare with previous version

resolved all threads

resolved all threads

added 1 commit

• eba4d2e3 - update docs with 413 response

Compare with previous version

resolved all threads

regarding the failed pipeline, I see that the same jobs are failing on master too

Hi @deepapathak can you plz look into Azure Test failure

Hi @Srinivasan_Narayanan azure tests are green now, can you review the MR please

added 1 commit

• f5e265bc - update NOTICE

Compare with previous version

added 9 commits

• f5e265bc...9ef36941 - 4 commits from branch master
• bc303f7c - handle too long response from elasticsearch
• 7b522a79 - enhance too long response from elasticsearch message
• d9163728 - update notice
• 03209718 - update docs with 413 response
• 2a42805c - update NOTICE

Compare with previous version

approved this merge request

added 1 commit

• baad56fd - update NOTICE

Compare with previous version

@chad Hi, could you help with this? Azure tests failure is not related to this MR changes, can we find someone to review it?

Hi @msavchuk Let me look into. Thx

The test failure is nothing to do with this MR. Hence approving further. Thx.