[#158] Separate init object reader from read itself #164

Collaborator

To be able to handle cases and return appropriate http status code
when object missed in storage but gate cache contains its metadata
we need write code after init object reader.
So we separate init reader from actual reading.

Signed-off-by: Denis Kirillov d.kirillov@yadro.com

To be able to handle cases and return appropriate http status code when object missed in storage but gate cache contains its metadata we need write code after init object reader. So we separate init reader from actual reading. Signed-off-by: Denis Kirillov <d.kirillov@yadro.com>
dkirillov self-assigned this 2023-07-06 13:45:18 +00:00
dkirillov force-pushed bugfix/158-return_404_if_object_not_found_but_cache_contains_meta from 6e537f14dd to 1979f3db15 2023-07-06 13:46:32 +00:00 Compare
dkirillov requested review from storage-services-developers 2023-07-07 06:28:00 +00:00
dkirillov requested review from storage-services-committers 2023-07-07 06:28:01 +00:00
dkirillov force-pushed bugfix/158-return_404_if_object_not_found_but_cache_contains_meta from 1979f3db15 to 8fd2ab6169 2023-07-11 14:12:48 +00:00 Compare
dkirillov force-pushed bugfix/158-return_404_if_object_not_found_but_cache_contains_meta from 8fd2ab6169 to 14ef9ff091 2023-07-11 14:33:02 +00:00 Compare
alexvanin approved these changes 2023-07-11 15:19:54 +00:00
ironbee approved these changes 2023-07-12 07:40:03 +00:00
pogpp approved these changes 2023-07-12 08:21:21 +00:00
dkirillov merged commit 14ef9ff091 into master 2023-07-12 09:27:08 +00:00
dkirillov deleted branch bugfix/158-return_404_if_object_not_found_but_cache_contains_meta 2023-07-12 09:27:38 +00:00
Sign in to join this conversation.
There is no content yet.