OpenBankProject / OpenBankProject/OBP-API

Error at the Kafka Connector level should give nicer Error at the API level

Open
#88 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.7k
Forks
482
Avg merge
1d 12h
Merged PRs (30d)
15

Description

Can we return nicer errors than this to the API in case of Kafka Connector level error?

Bad response code (500) from OBP API server:

Exception occured while processing /obp/v2.0.0/my/banks/SGBC/accounts/44ea4f603acac9c64d0e21af5c7ec4f429f0ec1c67b59d67a111807bab9f05b3/transactions
Message: com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key Map(bankId -> SGBC, username -> 123@simon.com, accountId -> 85bf9a150a1030857f8e6d6a7b898b8aa44c6ec5d625c0b2d98b66dd752f2b0b).
    com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2350)
    com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2320)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the transactions request at /obp/v2.0.0/my/banks/{bank}/accounts/{account}/transactions and trace how the Kafka Connector error becomes the shown CacheLoader exception and HTML response. Done means connector-level failures return a clearer API-level error instead of the raw 500 HTML and stack trace.

Written by the indexing model from the issue text.

Assessment

Tech stack
kafka, scala
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.