f547049929
Old: Merged segments are deleted upon successful push, or on IOException. New: Merged segments are deleted on any Exception, but NOT successful push. Deleting a merged segment means that the next merge-and-push run will try to push it again. So we want that to happen if there was any sort of Exception. We *don't* want it to happen if the merge-and-push was successful, since in that case, we are just waiting for historical nodes to load the segment. It might take a while, but there's no reason to re-push while waiting. |
||
|---|---|---|
| cassandra-storage | ||
| common | ||
| docs | ||
| examples | ||
| hdfs-storage | ||
| histogram | ||
| indexing-hadoop | ||
| indexing-service | ||
| install | ||
| kafka-eight | ||
| kafka-seven | ||
| processing | ||
| publications | ||
| rabbitmq | ||
| s3-extensions | ||
| server | ||
| services | ||
| .gitignore | ||
| CodeStyle.jar | ||
| DruidCorporateCLA.pdf | ||
| DruidIndividualCLA.pdf | ||
| LICENSE | ||
| README.md | ||
| build.sh | ||
| eclipse_formatting.xml | ||
| pom.xml | ||
| upload.sh | ||
README.md
Druid
Druid is a distributed, column-oriented, real-time analytics data store that is commonly used to power exploratory dashboards in multi-tenant environments. Druid excels as a data warehousing solution for fast aggregate queries on petabyte sized data sets. Druid supports a variety of flexible filters, exact calculations, approximate algorithms, and other useful calculations Druid can load both streaming and batch data and integrates with Storm and Hadoop.
More Information
Much more information about Druid can be found on our website.
Documentation
We host documentation on our website. If you want to contribute documentation changes, please submit a pull request to this repository.
Tutorials
We have a series of tutorials to get started with Druid, starting with this one.
Support
Contact us through our forum or on IRC in #druid-dev on irc.freenode.net.