OpenBankProject / OpenBankProject/OBP-API
elasticSearchWarehouseV300 vs mappedmetric
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
It looks like no issue was opened here when discovered a few months ago (see https://github.com/OpenBankProject/OBP-API-Scripts/blob/master/obp_api_scripts/generate_stats/stats.py#L161) so i will do it now:
With the advent of function elasticSearchWarehouseV300, table mappedmetric can not give us information about the usage of the warehouse anymore. The parameters have moved from the URL to the POST payload which is not covered by mappedmetric. Is there another place in the database where the parameters can be retrieved from?
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 referenced line in obp_api_scripts/generate_stats/stats.py and trace how elasticSearchWarehouseV300 receives parameters compared with mappedmetric. Inspect the database paths involved to determine whether POST payload parameters are stored elsewhere. Done means identifying a reliable source for warehouse usage parameters or documenting that no such source exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elasticsearch, python
- Domain
- backend-api-design, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100