Community
Mailing Lists
- Developers [ subscribe | archives ]
- Commits [ subscribe ] | archives ]
- Issues [ subscribe ] | archives ]
Bug Tracker, Zulip Chat, and CI
Contribute
Report a bug
Note: If you find a security vulnerability, do NOT open an issue. Please email security@apache.org instead.
When filing an issue, make sure to answer these five questions:
- What version of Apache Polaris (incubating) are you using?
- What operating system and processor architecture are you using?
- What did you do?
- What did you expect to see?
- What did yo9u see instead?
Troubleshooting questions should be posted on the dev mailing list or public chat. Maintainers and community members will answer your questions there or ask you to file an issue if you've encoutered a bug.
Suggest a feature or enhancement
Apache Polaris (incubating) aims to provide the Apache Iceberg™ community with new levels of choice, flexibility and control over their data, with full enterprise security and interoperability with Amazon Web Services (AWS), Confluent, Dremio, Google Cloud, Microsoft Azure, Salesforce and more.
If you're looking for a feature that doesn't exist in Apache Polaris (incubating), you're probably not alone. Others likely have similar needs. Please open an issue describing the feature you'd like to see, why you need it, and how it should work.
When creating your feature request, document your requirements first. Please, try to not directly describe the solution.
Before contributing code
Review open issues and discuss your approach
If you want to dive into development yourself then you can check out existing open issues or requests for features that need to be implemented. Take owmership of an issue and try fix it.
Before starting on a large code change, please describe the concept/design of what you plan to do on the issue/feature request you intend to address. If unsure if the design is good or will be accepted, discuss it with the community in the respective issue first, before you do too much active development.
Provide your changes in a Pull Request
The best way to provide changes is to fork Apache Polaris repository on GitHub and provide a Pull Request with your changes. To make it easy to apply your changes please use the following conventions:
- Every Pull Request should have a matching GitHub Issue.
- Create a branch that will house your change:
git clone https://github.com/apache/polaris
cd polaris
git fetch --all
git checkout -b my-branch origin/main
Don't forget to periodically rebase your branch:
git pull --rebase
git push GitHubUser my-branch --force
Ensure the code is properly formatted:
./gradlew format
- Pull Requests should be based on the
main
branch. - Test that your changes works by adapting or adding tests. Verify the build passes (see
README.md
for build instructions). - If your Pull Request has conflicts with the
main
branch, please rebase and fix the conflicts.
Java version requirements
- SDKMAN! follow the installation instructions, then run
sdk list java
to see the available distributions and versions, then runsdk install java <identifer from list>
using the identifier for the distribution and version (>= 21) of your choice. - jenv If on a Mac you can use jenv to set the appropriate SDK.
Team
Name | ID | Mentor | PPMC | Organization |
---|---|---|---|---|
Anoop Johnson | anoop | |||
Ashvin Agrawal | ashvin | Microsoft | ||
Bertrand Delacretaz | bdelacretaz | |||
Holden Karau | holden | |||
Jack Ye | jackye | AWS | ||
JB Onofre | jbonofre | Dremio | ||
John Roesler | vvcephei | Confluent | ||
Kent Yao | yao | |||
Robert Stupp | snazy | Dremio | ||
Russell Spitzer | russellspitzer | Snowflake | ||
Ryan Blue | blue | |||
Tyler Akidau | takidau | Snowflake |