From 71edeb8590786b153dec15966b49e0b3ef6e4763 Mon Sep 17 00:00:00 2001 From: Phillip LeBlanc Date: Tue, 18 Jun 2024 07:54:18 +0900 Subject: [PATCH] Update spiceaidocs/docs/features/local-acceleration/index.md Co-authored-by: Aurash Behbahani --- spiceaidocs/docs/features/local-acceleration/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spiceaidocs/docs/features/local-acceleration/index.md b/spiceaidocs/docs/features/local-acceleration/index.md index 7420d2431..98ff7555c 100644 --- a/spiceaidocs/docs/features/local-acceleration/index.md +++ b/spiceaidocs/docs/features/local-acceleration/index.md @@ -12,7 +12,7 @@ Datasets can be locally accelerated by the Spice runtime, pulling data from any When a dataset is locally accelerated by the Spice runtime, the data is stored alongside your application, providing much faster query times by cutting out network latency to make the request. This benefit is accentuated when the result of a query is large because the data does not need to be transferred over the network. Depending on the [Acceleration Engine](/data-accelerators) chosen, the locally accelerated data can also be stored in-memory, further reducing query times. [Indexes](./indexes.md) can also be applied, further speeding up certain types of queries. -For scenarios where data quality is required, locally accelerated datasets can also have [primary key constraints](./constraints.md) applied. This feature comes with the ability to specify what should happen when a constraint is violated, either drop the specific row that violates the constraint or upsert that row into the accelerated table. +Locally accelerated datasets can also have [primary key constraints](./constraints.md) applied. This feature comes with the ability to specify what should happen when a constraint is violated, either drop the specific row that violates the constraint or upsert that row into the accelerated table. ## Example Use Case