[FEA] Expose logger as argument to Python (and other) APIs
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
cuML’s estimators make use of the underlying logging in c++ in order to allow the log level to be set at runtime by users. While the runtime level defaults to INFO, the compiled artifacts are capable of going all the way down to DEBUG by default (and can be recompiled for TRACE if desired).
We should mirror this capability in cuVS, because it’s very powerful. It allows us to specify the logging at the lowest layer and have it propagate all the way up through the language wrappers.
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 by locating the cuVS estimators' Python and other language API entry points, then trace how their underlying C++ logging is configured. Confirm how cuML exposes runtime log levels and determine the cuVS API surface that should accept the logger. Done means users can set the logging level through the wrappers and have it propagate to the lowest layer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100