Skip to content

Online Store client does not map application errors #4481

@tmihalac

Description

@tmihalac

Expected Behavior

In a feast application that has a remote Online Store configured, when a feast client invokes an API on the Online Store that throws an error, the expectation is that the client will raises the same error that the online store threw

Current Behavior

When an error occurs a response with status code = 500 and error_message=Internal Server Error is returned from the server

Steps to reproduce

See Expected Behavior section.

Specifications

  • Version: 0.40.0
  • Platform: any
  • Subsystem: online store server

Possible Solution

The online store server can wrap the original exception in an error status message that the remote online store client can catch and translate into the original exception:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions