macOS
Homebrewverifiziert · 100%
brew install druidprovider-native install command
brew / Rang 5902
druid mit Homebrew installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für druid in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
High-performance, column-oriented, distributed data store
Projektlinks
Befehle und Aliase
- druid-broker.sh
- druid-coordinator.sh
- druid-historical.sh
- druid-jconsole.sh
- druid-middleManager.sh
- druid-node.sh
- druid-overlord.sh
- druid-router.sh
Verlauf
Projektgeschichte und Nutzung
Apache Druid is a high-performance real-time analytics database aimed at fast ingestion, low-latency OLAP queries, operational dashboards, and high-concurrency analytical applications. In package-manager terms, the Homebrew formula is less a tiny CLI utility and more a local entry point into a distributed data system with multiple node-role scripts.
Projektgeschichte
Druid entered the Apache Incubator on February 28, 2018. During incubation, source control moved to ASF Git/GitHub, incubating releases were cut in 2018 and 2019, and the project graduated as an Apache top-level project on December 18, 2019.
The current Apache Druid repository and website present Druid as a real-time analytics database with native ingestion, SQL/native query support, a web console, APIs, and deployment paths for local, Docker, and Kubernetes environments.
Adoptionsgeschichte
Druid adoption is tied to workloads that need fast ingest plus interactive analytical queries, especially dashboards, operational analytics, and user-facing data applications. Its Apache governance, public mailing lists, Slack/community pages, official Docker image, and separate Kubernetes operator are signals of an ecosystem beyond a single package.
Wie es verwendet wird
The Homebrew package exposes scripts for Druid process roles such as broker, coordinator, historical, middleManager, overlord, router, and node. Users typically start with the quickstart or Docker/Kubernetes deployment paths, then configure runtime properties under the documented `conf/druid` layout.
Warum Paket-Nerds sich dafür interessieren
Druid is significant to package maintainers because it stretches the definition of a package: installing it gives local executables, but the software is really a cluster with role-specific daemons, config trees, Java runtime requirements, web UI, APIs, and external integrations. It is a reminder that data infrastructure packages often package orchestration entry points as much as binaries.
Zeitleiste
- 2018-02-28: Druid enters the Apache Incubator.
- 2018-07-06: Druid source control moves to ASF Git/GitHub.
- 2018-12-12: Druid 0.13.0-incubating is released.
- 2019-04-09: Druid 0.14.0-incubating is released.
- 2019-12-18: Druid graduates as an Apache top-level project.
- Docs era: Apache Druid publishes docs, quickstarts, Docker guidance, and a separate Kubernetes operator.
Related projects
- Apache Druid Operator is maintained separately for Kubernetes deployments.
- The Druid website source is maintained separately from the main code repository.
- Druid commonly integrates with streaming and batch ingestion systems and exposes HTTP and JDBC query APIs.
Quellen
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für druid wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- Unix
conf/druid/_common/common.runtime.propertiesconf/druid/_common/log4j2.xmlconf/druid/broker/runtime.propertiesconf/druid/coordinator/runtime.propertiesconf/druid/historical/runtime.propertiesconf/druid/middleManager/runtime.propertiesconf/druid/overlord/runtime.properties
Executables
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
druid-broker.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-coordinator.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-historical.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-jconsole.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-middleManager.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-node.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-overlord.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
druid-router.sh | Executable | indexiertes Executable | Aus dem lokalen Executable-Index erkannt. |
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-08-03
Manager-Version37.0.0
Manager aktualisiert2026-06-22
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
- OKEs wurden keine Aktualitätswarnungen generiert.
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | brew:druid |
|---|---|
| Version | 37.0.0 |
| Paketmanager | Homebrew |
| Homepage | https://druid.apache.org/ |
| Zuletzt aktualisiert | 2026-06-22T14:03:12-07:00 |
| Pulse | updated |
| Bottle | nicht erfasst |
| Dienst | keiner deklariert |
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- Geiger risk classifier
- Nucleus package database
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation