OpenBankProject / OpenBankProject/OBP-API
Error creating Non-personal User Attributes with Kafka adapter
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
Hello,
I connected the Kafka adapter and implemented the backend, for example I process the /obp/v5.1.0/adapter method and successfully see its result in the OBP.
But some methods, for example POST /obp/v5.1.0/users/400637d0-745f-4ceb-9871-67cf5113ef3c/non-personal/attributes
{ "name":"W_LEVEL", "type":"STRING", "value":"90"}
return the following error:
{
"code": 400,
"message": "OBP-50200: Connector cannot return the data we requested. <- OBP-10010: Not Implemented setUnimplementedError$ Please check `Get Message Docs`endpoint and implement the process `obp.setUnimplementedError$` in Adapter side."
}
What does "Not Implemented" mean? Do I need to fork the OBP Api and implement this method (and many similar ones)? Or was there another solution?
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the POST /obp/v5.1.0/users/{user-id}/non-personal/attributes request and the reported obp.setUnimplementedError$ process. Read the Get Message Docs endpoint to identify the adapter message contract and determine whether the Kafka adapter must implement it. Done means the request succeeds through the Kafka adapter without the Not Implemented response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, scala
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100