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

Inaccurate Thrift Installation Instructions on README

Open
#3,228 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
documentation

Research direction

Start by locating the README section containing the OSX Homebrew Thrift 0.21.0 instructions and verify the current installation behavior described in the issue. Resolve whether the project will document brew extract or support Thrift 0.22.0, then update the README so the documented installation path works for the required version.

Written by the indexing model from the issue text.

Description

Type: bug
Describe the bug, including details regarding any error messages, version, and platform.

The README currently states:

“If you’re on OSX and use Homebrew, you can instead install Thrift 0.21.0 with brew and ensure that it comes first in your PATH.”

However, since Thrift 0.22.0 was released on May 23, 2025, the Homebrew formula for Thrift 0.21.0 is no longer available by default. As a result, users following the current instructions will not be able to install the required version.

To resolve this, we should either:
1. Upgrade the project to support Thrift 0.22.0 (not available on maven yet), or
2. Update the README to guide users to install Thrift 0.21.0 using brew extract, for example:

brew tap-new temp/oldthrift
brew extract --version=0.21.0 thrift temp/oldthrift
brew install temp/oldthrift/thrift@0.21.0
Component(s)

No response

Dominant language
Java
Stars
3.1k
Forks
1.6k
Avg merge
6d 16h
Merged PRs (30d)
36

Contributor guide

No contributing guide indexed for this repository

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 apache/parquet-java

All issues in apache/parquet-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.