[CORE] Selecting a cost model the backend has no coster for fails with ClassNotFoundException
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Start at GlutenCostModel.find, which treats unknown names as class names, then inspect LongCostModel.Kind.values() and LongCostModel.Registry.get. Reproduce with the ClickHouse backend and spark.gluten.costModel=rough; the fix should reject an unregistered cost model during lookup and include the config name in the error. Add or update a Scala test covering an unknown kind and an empty coster chain; done means the failure happens at lookup with a clear message.
Written by the indexing model from the issue text.
Description
When spark.gluten.costModel names a built-in cost model that the backend registers no coster for, the error does not say so. The ClickHouse backend only registers LegacyCoster, so the rough kind is never initialized and is missing from LongCostModel.Kind.values(). Setting spark.gluten.costModel=rough there makes GlutenCostModel.find treat rough as a class name and fail with ClassNotFoundException: rough. Even when the kind is known, LongCostModel.Registry.get returns an empty coster chain, and the failure only surfaces later as Cost not found for node: ....
Gluten could reject such a cost model when it is looked up and name the config.
This issue was written with the assistance of AI (Claude Opus).
- Dominant language
- Scala
- Stars
- 1.6k
- Forks
- 679
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 84
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from apache/gluten
-
bug unit testing velox backend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/gluten#13463 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 3 days
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching lengthMay be free again A pull request for this issue was closed without being merged. Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/gluten#12711 · 2 comments · 1 reaction ·
Maintainers usually reply within 3 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rchillyard/TableParser#206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
? - Needs Triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
NVIDIA/cudf-spark#17063 ·
Maintainers usually reply within 2 days
-
bug 🐞 User issue 🚨
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
valkey-io/valkey-glide#7813 · 2 comments ·
Maintainers usually reply within 1 day