From 100c7807046e457a4b6f529a60e23f8b3edd0e50 Mon Sep 17 00:00:00 2001 From: Alan Bernstein Date: Mon, 5 Nov 2018 11:36:55 -0600 Subject: [PATCH 1/3] Switch data model diagrams to png --- docs/data-model.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/data-model.md b/docs/data-model.md index bababdd34..91d9de0db 100644 --- a/docs/data-model.md +++ b/docs/data-model.md @@ -26,7 +26,7 @@ Pilosa lays out data first in rows, so queries which get all the set bits in one Please note that Pilosa is most performant when row and column IDs are sequential starting from 0. You can deviate from this to some degree, but setting a bit with column ID 263 on a single-node cluster, for example, will not work well due to memory limitations. -![basic data model diagram](/img/docs/data-model.svg) +![basic data model diagram](/img/docs/data-model.png) *Basic data model diagram* ### Index @@ -89,14 +89,14 @@ This is one major component of Pilosa's ability to combine relationships from mu Ranked Fields maintain a sorted cache of column counts by Row ID (yielding the top rows by columns with a bit set in each). This cache facilitates the TopN query. The cache size defaults to 50,000 and can be set at Field creation. -![ranked field diagram](/img/docs/field-ranked.svg) +![ranked field diagram](/img/docs/field-ranked.png) *Ranked field diagram* #### LRU The LRU cache maintains the most recently accessed Rows. -![lru field diagram](/img/docs/field-lru.svg) +![lru field diagram](/img/docs/field-lru.png) *LRU field diagram* ### Time Quantum @@ -161,7 +161,7 @@ Set(2, B=1) Set(3, B=6) ``` -![BSI field diagram](/img/docs/field-bsi.svg) +![BSI field diagram](/img/docs/field-bsi.png) *BSI field diagram* Check out this [blog post](/blog/range-encoded-bitmaps/) for some more details about BSI in Pilosa. @@ -186,7 +186,7 @@ Set(3, A=8, 2017-05-18T00:00) Set(3, A=8, 2017-05-19T00:00) ``` -![time quantum field diagram](/img/docs/field-time-quantum.svg) +![time quantum field diagram](/img/docs/field-time-quantum.png) *Time quantum fueld diagram* #### Mutex From 497c541affba5dcb2af87b89d34adcb822d4d6c4 Mon Sep 17 00:00:00 2001 From: Alan Bernstein Date: Mon, 5 Nov 2018 11:37:03 -0600 Subject: [PATCH 2/3] Remove outdated anchor link --- docs/glossary.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/glossary.md b/docs/glossary.md index fccbe0ae8..86ae6bd70 100644 --- a/docs/glossary.md +++ b/docs/glossary.md @@ -70,4 +70,4 @@ nav = [] [TopN](../query-language/#topn): A [PQL](#pql) query that returns a list of rows, sorted by the count of [columns](#column) set in the [row](#row), within a specified [field](#field). -[View](../data-model/#view): Views separate the different data layouts within a [Field](#field). The primary view is standard, which represents the typical [row](#row)/[column](#column) data. Time based field views are automatically generated for each [time quantum](#time-quantum). Views are internally managed by Pilosa, and never exposed directly via the API. This simplifies the functional interface by separating it from the physical data representation. +View: Views separate the different data layouts within a [Field](#field). The primary view is standard, which represents the typical [row](#row)/[column](#column) data. Time based field views are automatically generated for each [time quantum](#time-quantum). Views are internally managed by Pilosa, and never exposed directly via the API. This simplifies the functional interface by separating it from the physical data representation. From be5f8c923d84cc1ab6dddd6d97a975b4783b00ec Mon Sep 17 00:00:00 2001 From: Alan Bernstein Date: Mon, 5 Nov 2018 12:34:08 -0600 Subject: [PATCH 3/3] Remove 'view' from nav --- docs/data-model.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/data-model.md b/docs/data-model.md index 91d9de0db..9bb44bb99 100644 --- a/docs/data-model.md +++ b/docs/data-model.md @@ -10,7 +10,6 @@ nav = [ "Time Quantum", "Attribute", "Shard", - "View", ] +++