Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Spark 4.0 / DBR 14.2+ - bleeding edge changes

Open
#787 11 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
scala, spark
Domain
data

Research direction

Start by reviewing SPARK-44913 and the related discussions in #755 and #300 to understand the StaticInvoke changes and prior compatibility approach. The issue needs a settled route between a bleeding-edge release and a separate swappable compatibility jar before implementation can begin.

Written by the indexing model from the issue text.

Description

enhancement feature

Per my comment on #755 DBR 14.2, 4.0 and likely all later versions includes SPARK-44913 StaticInvoke changes.

Whilst this hasn't yet been backported to 3.5 branch it could well end up there.

I'm happy to fork and publish a bleeding edge / non-standard frameless if needed but I also wonder if a compat layer as a separate swappable jar is the best route similar to #300 for example.

What is the collective preferred route to fixing / working around this?

Dominant language
Scala
Stars
895
Forks
135
Avg merge
1d 16h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from typelevel/frameless

All issues in typelevel/frameless

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.