Skip to content

Commit 1bc473d

Browse files
committed
Replace broken mermaid diagram with PNG
Diagram looked fine in Chrome, but not Firefox, so I'm reluctantly replacing the dynamically generated figure with a static image.
1 parent f700125 commit 1bc473d

File tree

2 files changed

+1
-10
lines changed

2 files changed

+1
-10
lines changed

images/one-vs-many-files.png

68.2 KB
Loading

sections/cloud-scale-data.qmd

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -670,16 +670,7 @@ resembles a traditional Zarr store (many addressable pieces as separate
670670
files). This highlights two different approaches that you've encountered
671671
in this courses:
672672

673-
```{mermaid}
674-
flowchart LR
675-
A["Keep data in one file, but make
676-
it so that clients can efficiently
677-
extract subsets of interest"]
678-
<-->
679-
B["Separate data into many
680-
independent files, with metadata
681-
binding them together"];
682-
```
673+
![](../images/one-vs-many-files.png){fig-align="center" width="90%"}
683674

684675
Which is better? The likely answer is ... both! Indeed, the community
685676
seems to be converging on a hybrid model whereby we use a combination of

0 commit comments

Comments
 (0)