If so, the temporary fix may be just changing the message from the 503 unavailable to 4xx (maybe bad request?) with message like 'Storlet app failed because it doesn't set metadata to the resposne' which is useful to let user know why the request failed, rather than "Error downloading object 'storlet/test.py': Object GET failed: http://127.0.0.1:8080/v1/AUTH_107a9dd0b94547b5bb9c218c5609684a/storlet/test.py 503 Service Unavailable [first 60 chars of response] <html><h1>Service Unavailable</h1><p>The server is currently".
For design specification (it can be ok for future work), i think it would be nice to let the metadata handling can be by user trigger (i.e. sort of x-storlet-set-original-metadata: true).
Ok, Eran. That's expected.
If so, the temporary fix may be just changing the message from the 503 unavailable to 4xx (maybe bad request?) with message like 'Storlet app failed because it doesn't set metadata to the resposne' which is useful to let user know why the request failed, rather than "Error downloading object 'storlet/test.py': Object GET failed: http:// 127.0.0. 1:8080/ v1/AUTH_ 107a9dd0b94547b 5bb9c218c560968 4a/storlet/ test.py 503 Service Unavailable [first 60 chars of response] <html><h1>Service Unavailable< /h1><p> The server is currently".
For design specification (it can be ok for future work), i think it would be nice to let the metadata handling can be by user trigger (i.e. sort of x-storlet- set-original- metadata: true).