Hi, I opened PR #5206 to address issue #5167, which moves HTTP status mapping from PolarisExceptionMapper into the PolarisException hierarchy via a default httpStatusCode() method returning an int. @flyrain approved the code but raised a fair question: This puts an HTTP/transport concept into polaris-core, which is usually transport-neutral. The method uses plain int (no jakarta.ws dependency), but semantically it still represents an HTTP status code. Would the community prefer to keep this in polaris-core, or should the status mapping stay entirely in the service layer?
PR: https://github.com/apache/polaris/pull/5206 Thanks, Harshita
