Skip to content

Commit d34dfb5

Browse files
committed
Data modelling: Populate index page
1 parent 73f922b commit d34dfb5

File tree

8 files changed

+118
-2
lines changed

8 files changed

+118
-2
lines changed

docs/start/modelling/fulltext.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-fulltext)=
12
# Full-text data
23

34
CrateDB features **native full‑text search** powered by **Apache Lucene** and Okapi BM25 ranking, fully accessible via SQL. You can blend this seamlessly with other data types—JSON, time‑series, geospatial, vectors and more—all in a single SQL query platform.

docs/start/modelling/geospatial.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-geospatial)=
12
# Geospatial data
23

34
CrateDB supports **real-time geospatial analytics at scale**, enabling you to store, query, and analyze 2D location-based data using standard SQL over two dedicated types: **GEO\_POINT** and **GEO\_SHAPE**. You can seamlessly combine spatial data with full-text, vector, JSON, or time-series in the same SQL queries.

docs/start/modelling/index.md

Lines changed: 111 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,99 @@
1+
(modelling)=
2+
(data-modelling)=
13
# Data modelling
24

5+
:::{div} sd-text-muted
36
CrateDB provides a unified storage engine that supports different data types.
7+
:::
8+
9+
:::::{grid} 2 3 3 3
10+
:padding: 0
11+
:class-container: installation-grid
12+
13+
::::{grid-item-card} Relational data
14+
:link: model-relational
15+
:link-type: ref
16+
:link-alt: Relational data
17+
:padding: 3
18+
:text-align: center
19+
:class-card: sd-pt-3
20+
:class-body: sd-fs-1
21+
:class-title: sd-fs-6
22+
23+
{fas}`table-list`
24+
::::
25+
26+
::::{grid-item-card} JSON data
27+
:link: model-json
28+
:link-type: ref
29+
:link-alt: JSON data
30+
:padding: 3
31+
:text-align: center
32+
:class-card: sd-pt-3
33+
:class-body: sd-fs-1
34+
:class-title: sd-fs-6
35+
36+
{fas}`file-lines`
37+
::::
38+
39+
::::{grid-item-card} Timeseries data
40+
:link: model-timeseries
41+
:link-type: ref
42+
:link-alt: Timeseries data
43+
:padding: 3
44+
:text-align: center
45+
:class-card: sd-pt-3
46+
:class-body: sd-fs-1
47+
:class-title: sd-fs-6
48+
49+
{fas}`timeline`
50+
::::
51+
52+
::::{grid-item-card} Geospatial data
53+
:link: model-geospatial
54+
:link-type: ref
55+
:link-alt: Geospatial data
56+
:padding: 3
57+
:text-align: center
58+
:class-card: sd-pt-3
59+
:class-body: sd-fs-1
60+
:class-title: sd-fs-6
61+
62+
{fas}`globe`
63+
::::
64+
65+
::::{grid-item-card} Fulltext data
66+
:link: model-fulltext
67+
:link-type: ref
68+
:link-alt: Fulltext data
69+
:padding: 3
70+
:text-align: center
71+
:class-card: sd-pt-3
72+
:class-body: sd-fs-1
73+
:class-title: sd-fs-6
74+
75+
{fas}`font`
76+
::::
77+
78+
::::{grid-item-card} Vector data
79+
:link: model-vector
80+
:link-type: ref
81+
:link-alt: Vector data
82+
:padding: 3
83+
:text-align: center
84+
:class-card: sd-pt-3
85+
:class-body: sd-fs-1
86+
:class-title: sd-fs-6
87+
88+
{fas}`lightbulb`
89+
::::
90+
91+
:::::
92+
93+
494
```{toctree}
595
:maxdepth: 1
96+
:hidden:
697
798
relational
899
json
@@ -12,10 +103,28 @@ fulltext
12103
vector
13104
```
14105

15-
Because CrateDB is a distributed OLAP database designed store large volumes
16-
of data, it needs a few special considerations on certain details.
106+
:::{rubric} Implementation notes
107+
:::
108+
109+
Because CrateDB is a distributed analytical database (OLAP) designed to store
110+
large volumes of data, users need to consider certain details compared to
111+
traditonal RDBMS.
112+
113+
114+
:::{card} Primary key strategies
115+
:link: model-primary-key
116+
:link-type: ref
117+
CrateDB is built for horizontal scalability and high ingestion throughput.
118+
+++
119+
To achieve this, operations must complete independently on each node—without
120+
central coordination. This design choice means CrateDB does not support
121+
traditional auto-incrementing primary key types like `SERIAL` in PostgreSQL
122+
or MySQL by default.
123+
:::
124+
17125
```{toctree}
18126
:maxdepth: 1
127+
:hidden:
19128
20129
primary-key
21130
```

docs/start/modelling/json.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-json)=
12
# JSON data
23

34
CrateDB combines the flexibility of NoSQL document stores with the power of SQL. It enables you to store, query, and index **semi-structured JSON data** using **standard SQL**, making it an excellent choice for applications that handle diverse or evolving schemas.

docs/start/modelling/primary-key.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-primary-key)=
12
# Primary key strategies
23

34
CrateDB is built for horizontal scalability and high ingestion throughput. To achieve this, operations must complete independently on each node—without central coordination. This design choice means CrateDB does **not** support traditional auto-incrementing primary key types like `SERIAL` in PostgreSQL or MySQL by default.

docs/start/modelling/relational.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-relational)=
12
# Relational data
23

34
CrateDB is a **distributed SQL database** that offers rich **relational data modeling** with the flexibility of dynamic schemas and the scalability of NoSQL systems. It supports **primary keys,** **joins**, **aggregations**, and **subqueries**, just like traditional RDBMS systems—while also enabling hybrid use cases with time-series, geospatial, full-text, vector search, and semi-structured data.

docs/start/modelling/timeseries.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-timeseries)=
12
# Time series data
23

34
CrateDB employs a relational representation for time‑series, enabling you to work with timestamped data using standard SQL, while also seamlessly combining with document and context data.

docs/start/modelling/vector.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
(model-vector)=
12
# Vector data
23

34
CrateDB natively supports **vector embeddings** for efficient **similarity search** using **approximate nearest neighbor (ANN)** algorithms. This makes it a powerful engine for building AI-powered applications involving semantic search, recommendations, anomaly detection, and multimodal analytics—all in the simplicity of SQL.

0 commit comments

Comments
 (0)