63ee69b4e8
* Claim full support for Java 17. No production code has changed, except the startup scripts. Changes: 1) Allow Java 17 without DRUID_SKIP_JAVA_CHECK. 2) Include the full list of opens and exports on both Java 11 and 17. 3) Document that Java 17 is both supported and preferred. 4) Switch some tests from Java 11 to 17 to get better coverage on the preferred version. * Doc update. * Update errorprone. * Update docker_build_containers.sh. * Update errorprone in licenses.yaml. * Add some more run-javas. * Additional run-javas. * Update errorprone. * Suppress new errorprone error. * Add exports and opens in ForkingTaskRunner for Java 11+. Test, doc changes. * Additional errorprone updates. * Update for errorprone. * Restore old fomatting in LdapCredentialsValidator. * Copy bin/ too. * Fix Java 15, 17 build line in docker_build_containers.sh. * Update busybox image. * One more java command. * Fix interpolation. * IT commandline refinements. * Switch to busybox 1.34.1-glibc. * POM adjustments, build and test one IT on 17. * Additional debugging. * Fix silly thing. * Adjust command line. * Add exports and opens one more place. * Additional harmonization of strong encapsulation parameters. |
||
|---|---|---|
| .github | ||
| .idea | ||
| benchmarks | ||
| cloud | ||
| codestyle | ||
| dev | ||
| distribution | ||
| docs | ||
| examples | ||
| extensions-contrib | ||
| extensions-core | ||
| helm/druid | ||
| hooks | ||
| indexing-hadoop | ||
| indexing-service | ||
| integration-tests | ||
| integration-tests-ex | ||
| licenses | ||
| processing | ||
| publications | ||
| server | ||
| services | ||
| sql | ||
| web-console | ||
| website | ||
| .asf.yaml | ||
| .backportrc.json | ||
| .codecov.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .lgtm.yml | ||
| CONTRIBUTING.md | ||
| LABELS | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
| README.template | ||
| check_test_suite.py | ||
| check_test_suite_test.py | ||
| it.sh | ||
| licenses.yaml | ||
| owasp-dependency-check-suppressions.xml | ||
| pom.xml | ||
| upload.sh | ||
README.md
| Workflow | Status |
|---|---|
| ⚙️ CodeQL Config |  |
| 🔍 CodeQL |  |
| 🕒 Cron Job ITS |  |
| 🏷️ Labeler |  |
| ♻️ Reusable Revised ITS |  |
| ♻️ Reusable Standard ITS |  |
| ♻️ Reusable Unit Tests |  |
| 🔄 Revised ITS |  |
| 🔧 Standard ITS |  |
| 🛠️ Static Checks |  |
| 🧪 Unit and Integration Tests Unified |  |
| 🔬 Unit Tests |  |
Apache Druid
Druid is a high performance real-time analytics database. Druid's main value add is to reduce time to insight and action.
Druid is designed for workflows where fast queries and ingest really matter. Druid excels at powering UIs, running operational (ad-hoc) queries, or handling high concurrency. Consider Druid as an open source alternative to data warehouses for a variety of use cases. The design documentation explains the key concepts.
Getting started
You can get started with Druid with our local or Docker quickstart.
Druid provides a rich set of APIs (via HTTP and JDBC) for loading, managing, and querying your data. You can also interact with Druid via the built-in web console (shown below).
Load data
Load streaming and batch data using a point-and-click wizard to guide you through ingestion setup. Monitor one off tasks and ingestion supervisors.
Manage the cluster
Manage your cluster with ease. Get a view of your datasources, segments, ingestion tasks, and services from one convenient location. All powered by SQL systems tables, allowing you to see the underlying query for each view.
Issue queries
Use the built-in query workbench to prototype DruidSQL and native queries or connect one of the many tools that help you make the most out of Druid.
Documentation
See the latest documentation for the documentation for the current official release. If you need information on a previous release, you can browse previous releases documentation.
Make documentation and tutorials updates in /docs using MarkDown and contribute them using a pull request.
Community
Visit the official project community page to read about getting involved in contributing to Apache Druid, and how we help one another use and operate Druid.
- Druid users can find help in the
druid-usermailing list on Google Groups, and have more technical conversations in#troubleshootingon Slack. - Druid development discussions take place in the
druid-devmailing list (dev@druid.apache.org). Subscribe by emailing dev-subscribe@druid.apache.org. For live conversations, join the#devchannel on Slack.
Check out the official community page for details of how to join the community Slack channels.
Find articles written by community members and a calendar of upcoming events on the project site - contribute your own events and articles by submitting a PR in the apache/druid-website-src repository.
Building from source
Please note that JDK 8 or JDK 11 is required to build Druid.
See the latest build guide for instructions on building Apache Druid from source.
Contributing
Please follow the community guidelines for contributing.
For instructions on setting up IntelliJ dev/intellij-setup.md