Skip to content

[Python] Deprecate pyarrow.gandiva #49227

Closed

Description

@pitrou

Describe the enhancement requested

I don't think pyarrow.gandiva is getting a lot of usage. The last non-trivial change was made 2 years ago by @niyue . It is not packaged on PyPI, but it's part of the pyarrow-all package on conda-forge which is not downloaded much (35K downloads for 6 months compared to 3M for pyarrow-core).

Deprecating and then dropping pyarrow.gandiva would simplify some CI build and remove some light maintenance burden from the team. It would also make it easier to later move Gandiva C++ to a separate repository.

Component(s)

Python

Activity

  1. pitrou commented on Feb 11, 2026

    @pitrou
    MemberAuthor

    Thoughts @AlenkaF @raulcd @kou ?

  2. raulcd commented on Feb 11, 2026

    @raulcd
    Member

    I am in favor of this. Not being part of the provided wheels to PyPI helps on the decision.

    As a concrete plan we could deprecate it for 24.0.0 and drop it for 25.0.0.

    We should send an email to the dev mailing list to give visibility to this issue in case there are any concerns raised.

  3. rok commented on Feb 11, 2026

    @rok
    Member

    Agreed with all said above.

  4. kou commented on Feb 12, 2026

    @kou
    Member

    We should send an email to the dev mailing list to give visibility to this issue in case there are any concerns raised.

    +1

  5. pitrou commented on Feb 12, 2026

    @pitrou
    MemberAuthor
  6. AlenkaF commented on Apr 1, 2026

    @AlenkaF
    Member

    There are no responses/concerns raised via ML AFAICT. I can try to get a PR up today to get the deprecation part in for 24.0.0 so we can drop it in a later version.

  7. self-assigned this
    on Apr 1, 2026
  8. added this to the 24.0.0 milestone on Apr 1, 2026
  9. added a commit that references this issue on Apr 2, 2026
  10. AlenkaF commented on Apr 2, 2026

    @AlenkaF
    Member

    Issue resolved by pull request 49637
    #49637

  11. added a commit that references this issue on Apr 6, 2026
  12. added a commit that references this issue on May 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions