Welcome!¶

Apache Iceberg tracks issues in GitHub and prefers to receive contributions as pull requests.

Community discussions happen primarily on the dev mailing list, on apache-iceberg Slack workspace, and on specific GitHub issues.

Contributing¶

The Iceberg Project is hosted on Github at https://github.com/apache/iceberg.

The Iceberg community prefers to receive contributions as Github pull requests.

• View open pull requests
• Learn about pull requests

Issues¶

Issues are tracked in GitHub:

• View open issues
• Open a new issue

Slack¶

We use the Apache Iceberg workspace on Slack. To be invited, follow this invite link.

Please note that this link may occasionally break when Slack does an upgrade. If you encounter problems using it, please let us know by sending an email to dev@iceberg.apache.org.

Mailing Lists¶

Iceberg has four mailing lists:

• Developers: dev@iceberg.apache.org – used for community discussions
  • Subscribe
  • Unsubscribe
  • Archive
• Commits: commits@iceberg.apache.org – distributes commit notifications
  • Subscribe
  • Unsubscribe
  • Archive
• Issues: issues@iceberg.apache.org – Github issue tracking
  • Subscribe
  • Unsubscribe
  • Archive
• Private: private@iceberg.apache.org – private list for the PMC to discuss sensitive issues related to the health of the project
  • Archive

Setting up IDE and Code Style¶

Configuring Code Formatter for IntelliJ IDEA¶

In the Settings/Preferences dialog go to Editor > Code Style > Java. Click on the gear wheel and select Import Scheme to import IntelliJ IDEA XML code style settings. Point to intellij-java-palantir-style.xml and hit OK (you might need to enable Show Hidden Files and Directories in the dialog). The code itself can then be formatted via Code > Reformat Code.

See also the IntelliJ Code Style docs and Reformat Code docs for additional details.

Running Benchmarks¶

Some PRs/changesets might require running benchmarks to determine whether they are affecting the baseline performance. Currently there is no “push a single button to get a performance comparison” solution available, therefore one has to run JMH performance tests on their local machine and post the results on the PR.

See Benchmarks for a summary of available benchmarks and how to run them.