stackabletech / stackabletech/documentation

Deep dive on Druid publishing and storage guarantees (or the lack thereof)

Open
#681 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
CSS
Stars
13
Forks
14
Avg merge
4d 8h
Merged PRs (30d)
10

Description

  • When does Druid commit ("publish") data to deep storage?
  • What happens to written but not-yet-published data if a Druid pod dies? (Both graceful and forceful cases...)
  • Is it possible to force a publish manually?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Research Druid publishing to deep storage, the graceful and forceful pod-death cases, and whether publishing can be forced manually; document sourced answers for each question in the appropriate documentation location once identified.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.