summaryrefslogtreecommitdiffstats
path: root/chapters
diff options
context:
space:
mode:
authorDouglas Rumbaugh <dbr4@psu.edu>2025-05-20 17:15:37 -0400
committerDouglas Rumbaugh <dbr4@psu.edu>2025-05-20 17:15:37 -0400
commitae552423e36a12a458a1719a6607998ccf129a38 (patch)
treec71dff697da31a7bc6135326c1cd795778c88e82 /chapters
parent9dcb32a0084a702459eb26b4b024cec05af4f970 (diff)
downloaddissertation-ae552423e36a12a458a1719a6607998ccf129a38.tar.gz
updates
Diffstat (limited to 'chapters')
-rw-r--r--chapters/introduction.tex44
1 files changed, 12 insertions, 32 deletions
diff --git a/chapters/introduction.tex b/chapters/introduction.tex
index bdde070..75fad37 100644
--- a/chapters/introduction.tex
+++ b/chapters/introduction.tex
@@ -22,38 +22,18 @@ point-lookups~\cite{mysql-btree-hash, cowbook}.
This situation is unfortunate, because one of the major challenges
currently facing data systems is the processing of complex analytical
queries of varying types over large sets of data. These queries and
-data types are supported, nominally, by a relational database, but
-are not well addressed by existing indexing techniques and as a result
-have horrible performance. This has led to the development of a variety
-of specialized systems for particular types of query, such as spatial
-systems~\cite{postgis-doc}, vector databases~\cite{pinecone-db}, and
-graph databases~\cite{neptune, neo4j}.
-
-
-
-
-
-
-however the cost of this flexibility is
-
-Modern relational database systems are based upon the fundamental data
-
-
-highly optimized for addressing
-particular types of search problems, such as point lookups and range
-queries.
-
-One of the major challenges facing current data systems is the processing
-of complex and varied analytical queries over vast data sets. One commonly
-used technique for accelerating these queries is the application of data
-structures to create indexes, which are the basis for specialized database
-systems and data processing libraries. Unfortunately, the development
-of these indexes is difficult because of the requirements placed on
-them by data processing systems. Data is frequently subject to updates,
-yet a large number of potentially useful data structures are static.
-Further, many large-scale data processing systems are highly concurrent,
-which increases the barrier to entry even further. The process for
-developing data structures that satisfy these requirements is arduous.
+data types are supported, nominally, by a relational database, but are
+not well addressed by existing indexing techniques and as a result have
+horrible performance. This has led to the development of a variety of
+specialized systems for particular types of query, such as spatial
+systems~\cite{postgis-doc}, vector databases~\cite{pinecone-db},
+and graph databases~\cite{neptune, neo4j}. The development of these
+indexes is difficult because of the requirements placed on them by data
+processing systems. Data is frequently subject to updates, yet a large
+number of potentially useful data structures are static. Further,
+many large-scale data processing systems are highly concurrent, which
+increases the barrier to entry even further. The process for developing
+data structures that satisfy these requirements is arduous.
To demonstrate this difficulty, consder the recent example of the
evolution of learned indexes. These are data structures designed to