mirror of
https://github.com/featurebasedb/featurebase.git
synced 2026-08-28 10:54:59 +00:00
the RangeEnabled option now has no effect, but it still exists in the API. A few tests still use it to ensure this. This would only be considered a breaking change if someone was relying on Pilosa to enforce the RangeEnabled: false option to prevent fields being created in certain frames. This seems unlikely. |
||
|---|---|---|
| .. | ||
| administration.md | ||
| api-reference.md | ||
| architecture.md | ||
| client-libraries.md | ||
| configuration.md | ||
| data-model.md | ||
| examples.md | ||
| faq.md | ||
| getting-started.md | ||
| glossary.md | ||
| input-definition.md | ||
| installation.md | ||
| introduction.md | ||
| pdk.md | ||
| query-language.md | ||
| README.md | ||
| tutorials.md | ||
| webui.md | ||
Pilosa docs are maintained here, to stay in sync with the codebase. The format is Blackfriday markdown, with some Hugo front matter.
Please visit our website to view the docs complete with styles, diagrams, and comprehensive search.
Have you found a discrepancy, typo, or other problem? Please submit an issue or a pull request!