Lambda functions return success on malformed payload about aws-athena-query-federation HOT 2 CLOSED

It is my understanding that the HTTP Status Code reflects the state of the call to AWS Lambda, not the success/failure of the code running within the Lambda invocation.

The status code in the API response doesn't reflect function errors. Error codes are reserved for errors that prevent your function from executing, such as permissions errors, limit errors, or issues with your function's code and configuration. For example, Lambda returns TooManyRequestsException if executing the function would cause you to exceed a concurrency limit at either the account level (ConcurrentInvocationLimitExceeded) or function level (ReservedFunctionConcurrentInvocationLimitExceeded).

from https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html

I've seen the Lambda java client re-throw uncaught exceptions from the Lambda function invocation as a LambdaInvocationException. This seems to suggest that there is some application level protocol for serializing the exception from within the Lambda invocation.

In fact, this page seems to show how Lambda functions (written in Java) handle uncaught exceptions:

Expected payload format when encountering an uncaught exception:

{
  "errorMessage": "Name John Doe is invalid. Exception occurred...",
  "errorType": "java.lang.Exception",
  "stackTrace": [
    "example.Hello.handler(Hello.java:9)",
    "sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)",
    "sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)",
    "sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)",
    "java.lang.reflect.Method.invoke(Method.java:497)"
  ]
}

from this page: https://docs.aws.amazon.com/lambda/latest/dg/java-exceptions.html

Alternatively, many of the docs seems to suggest you can get custom HTTP Status Codes by using API Gateway in front of your Lambda function. It has been a while since I looked closely at API Gateway by they did not support sufficiently long timeouts or request/response payload sizes to be advisable in conjunction with Query Federation.

I'll see what else I can find but I also don't see a way to affect the HTTP Status Codes from the Java interface our Lambda's implement.

from aws-athena-query-federation.

Closing per chat with @grundprinzip . @grundprinzip please reopen if you are still blocked.

from aws-athena-query-federation.