Reset buffer aggregators when resetting Groupers. (#16296)

Buffer aggregators can contain some cached objects within them, such as
Memory references or HLL Unions. Prior to this patch, various Grouper
implementations were not releasing this state when resetting their own
internal state, which could lead to excessive memory use.

This patch renames AggregatorAdapater#close to "reset", and updates
Grouper implementations to call this reset method whenever they reset
their internal state.

The base method on BufferAggregator and VectorAggregator remains named
"close", for compatibility with existing extensions, but the contract
is adjusted to say that the aggregator may be reused after the method
is called. All existing implementations in core already adhere to this
new contract, except for the ArrayOfDoubles build flavors, which are
updated in this patch to adhere.

Additionally, this patch harmonizes buffer sketch helpers to call their
clear method "clear" rather than a mix of "clear" and "close". (Others
were already using "clear".)
22 files changed
tree: 1c9dfe1d1d50a07686109272b0f9dd6afe35d40b
  1. .github/
  2. .idea/
  3. benchmarks/
  4. cloud/
  5. codestyle/
  6. dev/
  7. distribution/
  8. docs/
  9. examples/
  10. extensions-contrib/
  11. extensions-core/
  12. hooks/
  13. indexing-hadoop/
  14. indexing-service/
  15. integration-tests/
  16. integration-tests-ex/
  17. licenses/
  18. processing/
  19. publications/
  20. server/
  21. services/
  22. sql/
  23. web-console/
  24. website/
  25. .asf.yaml
  26. .backportrc.json
  27. .codecov.yml
  28. .dockerignore
  29. .gitignore
  30. .lgtm.yml
  31. check_test_suite.py
  32. check_test_suite_test.py
  33. CONTRIBUTING.md
  34. doap_Druid.rdf
  35. it.sh
  36. LABELS
  37. LICENSE
  38. licenses.yaml
  39. NOTICE
  40. owasp-dependency-check-suppressions.xml
  41. pom.xml
  42. README.md
  43. README.template
  44. rewrite.yml
  45. upload.sh
README.md

Coverage Status Docker Helm

WorkflowStatus
โš™๏ธ CodeQL Configcodeql-config
๐Ÿ” CodeQLcodeql
๐Ÿ•’ Cron Job ITScron-job-its
๐Ÿท๏ธ Labelerlabeler
โ™ป๏ธ Reusable Revised ITSreusable-revised-its
โ™ป๏ธ Reusable Standard ITSreusable-standard-its
โ™ป๏ธ Reusable Unit Testsreusable-unit-tests
๐Ÿ”„ Revised ITSrevised-its
๐Ÿ”ง Standard ITSstandard-its
๐Ÿ› ๏ธ Static Checksstatic-checks
๐Ÿงช Unit and Integration Tests Unifiedunit-and-integration-tests-unified
๐Ÿ”ฌ Unit Testsunit-tests

Website Twitter Download Get Started Documentation Community Build Contribute License


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

data loader Kafka

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

management

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

query view combo

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 or extended Markdown (MDX). Then, open a pull request.

To build the site locally, you need Node 16.14 or higher and to install Docusaurus 2 with npm|yarn install in the website directory. Then you can run npm|yarn start to launch a local build of the docs.

If you're looking to update non-doc pages like Use Cases, those files are in the druid-website-src repo.

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-user mailing list on Google Groups, and have more technical conversations in #troubleshooting on Slack.
  • Druid development discussions take place in the druid-dev mailing list (dev@druid.apache.org). Subscribe by emailing dev-subscribe@druid.apache.org. For live conversations, join the #dev channel 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

License

Apache License, Version 2.0