[FEA] Display operations unsupported by the GPU in a user-friendly way
- Dominant language
- C++
- Stars
- 9.8k
- Forks
- 1.1k
- Avg merge
- 3d 6m
- Merged PRs (30d)
- 278
Description
**Is your feature request related to a problem? Please describe.**
As of #16960, `cudf.polars` will print the set errors encountered while translating Polars IR to `cudf.polars` IR. We should print this list of errors in a user-friendly way.
**Describe the solution you'd like**
I'd like to see something like a HTML table presented with the errors as entries in the table. Some IR like `Scan`s, `GroupBy`s, or `BooleanFunction`s return different `NotImplementedError` messages depending on the arguments supplied. In these cases, we could group the errors by IR categories with a dropdown to list the errors in each category.
We should also link a github issue request that would allow users to immediately open a feature request issue in cuDF to support the unsupported operations they found. This is almost identical to what we do in the [`cudf.pandas` profiler](https://docs.rapids.ai/api/cudf/stable/cudf_pandas/usage/#using-the-function-profiler).
It would also be nice to connect the IR to the actual Polars function that was used. Eg. `GroupBy` --> `LazyFrame.group_by`
**Describe alternatives you've considered**
I haven't considered any other alternatives at the moment.
**Additional context**
Related UX issue for `cudf.polars` https://github.com/rapidsai/cudf/issues/16224
cc. @wence- @beckernick
Contributor guide
Assessment
This issue has not been assessed yet.