New cache implementation for the server

Cargo.toml

@@ -70,10 +70,11 @@ raphtory-storage = { version = "0.18.0", path = "raphtory-storage", default-feat
 raphtory-itertools = { version = "0.18.0", path = "raphtory-itertools" }
 clam-core = { version = "0.18.0", path = "clam-core" }
 optd-core = { version = "0.18.0", path = "optd/optd/core" }
+
 async-graphql = { version = "7.2.1", features = ["dynamic-schema"] }
 bincode = { version = "2", features = ["serde"] }
 async-graphql-poem = "7.2.1"
-dynamic-graphql = { git = "https://github.com/miratepuffin/dynamic-graphql", branch = "add-arg-descriptions" }
+dynamic-graphql = "0.10.2"
 derive_more = "2.1.1"
 tikv-jemallocator = "0.6.1"
 reqwest = { version = "0.12.28", default-features = false, features = [
@@ -167,7 +168,6 @@ pest = "2.8.6"
 pest_derive = "2.8.6"
 minijinja = "2.18.0"
 minijinja-contrib = { version = "2.18.0", features = ["datetime"] }
-
 lancedb = { version = "0.27.2", features = [] }
 heed = "0.22.0"
 sqlparser = "0.59.0"
@@ -185,6 +185,7 @@ arrow-data = { version = "57.3.0" }
 arrow-select = { version = "57.3.0" }
 serde_arrow = { version = "0.13.7", features = ["arrow-57"] }
 moka = { version = "0.12.15", features = ["future"] }
+quick_cache = "0.6.21"
 indexmap = { version = "2.13.0", features = ["rayon"] }
 fake = { version = "3.1.0", features = ["chrono"] }
 strsim = { version = "0.11.1" }

db4-storage/Cargo.toml

@@ -46,5 +46,6 @@ rayon.workspace = true
 test-log.workspace = true
 
 [features]
-test-utils = ["dep:proptest", "dep:chrono"]
-default = ["test-utils"]
+test-utils = ["dep:proptest", "dep:chrono", "panic-on-drop"]
+panic-on-drop = []
+

db4-storage/src/pages/graph_prop_store.rs

@@ -9,6 +9,7 @@ use crate::{
 };
 use raphtory_api::core::entities::properties::meta::Meta;
 use std::{
+    marker::PhantomData,
     path::{Path, PathBuf},
     sync::Arc,
 };
@@ -23,10 +24,7 @@ pub struct GraphPropStorageInner<GS, EXT> {
 
     /// Stores graph prop metadata (prop name -> prop id mappings).
     meta: Arc<Meta>,
-
-    path: Option<PathBuf>,
-
-    ext: EXT,
+    _ext: PhantomData<EXT>,
 }
 
 impl<GS: GraphPropSegmentOps<Extension = EXT>, EXT: PersistenceStrategy>
@@ -37,9 +35,8 @@ impl<GS: GraphPropSegmentOps<Extension = EXT>, EXT: PersistenceStrategy>
 
         Self {
             page,
-            path: path.map(|p| p.to_path_buf()),
             meta,
-            ext,
+            _ext: PhantomData,
         }
     }
 
@@ -52,9 +49,8 @@ impl<GS: GraphPropSegmentOps<Extension = EXT>, EXT: PersistenceStrategy>
                 path.as_ref(),
                 ext.clone(),
             )?),
-            path: Some(path.as_ref().to_path_buf()),
             meta: graph_props_meta,
-            ext,
+            _ext: PhantomData,
         })
     }
 

db4-storage/src/pages/mod.rs

@@ -42,8 +42,21 @@ pub mod session;
 #[cfg(any(test, feature = "test-utils"))]
 pub mod test_utils;
 
-// graph // (node/edges) // segment // layer_ids (0, 1, 2, ...) // actual graphy bits
+#[cfg(any(test, feature = "panic-on-drop"))]
+macro_rules! drop_error {
+    ($($arg:tt)*) => {{
+        panic!($($arg)*)
+    }};
+}
+
+#[cfg(not(any(test, feature = "panic-on-drop")))]
+macro_rules! drop_error {
+    ($($arg:tt)*) => {{
+        eprintln!($($arg)*)
+    }};
+}
 
+// graph // (node/edges) // segment // layer_ids (0, 1, 2, ...) // actual graphy bits
 #[derive(Debug)]
 pub struct GraphStore<
     NS: NodeSegmentOps<Extension = EXT>,
@@ -372,7 +385,7 @@ impl<
                 let checkpoint_lsn = match wal.log_shutdown_checkpoint() {
                     Ok(lsn) => lsn,
                     Err(err) => {
-                        eprintln!("Failed to log shutdown checkpoint in drop: {err}");
+                        drop_error!("Failed to log shutdown checkpoint in drop: {err}");
                         return;
                     }
                 };
@@ -381,7 +394,7 @@ impl<
                 let flush_lsn = wal.position();
 
                 if let Err(err) = wal.flush(flush_lsn) {
-                    eprintln!("Failed to flush checkpoint record in drop: {err}");
+                    drop_error!("Failed to flush checkpoint record in drop: {err}");
                     return;
                 }
 
@@ -390,12 +403,12 @@ impl<
                 control_file.set_db_state(DBState::Shutdown);
 
                 if let Err(err) = control_file.save() {
-                    eprintln!("Failed to save control file in drop: {err}");
+                    drop_error!("Failed to save control file in drop: {err}");
                     return;
                 }
             }
             Err(err) => {
-                eprintln!("Failed to flush storage in drop: {err}")
+                drop_error!("Failed to flush storage in drop: {err}");
             }
         }
     }
@@ -458,4 +471,10 @@ mod test {
 
         assert_eq!(actual, expected);
     }
+
+    #[test]
+    #[should_panic]
+    fn test_drop_error() {
+        drop_error!("failed");
+    }
 }

docs/user-guide/graphql/2_run-server.md

@@ -8,11 +8,14 @@ Before reading this topic, please ensure you are familiar with:
 
 ## Saving your Raphtory graph into a directory
 
-You will need some test data to complete the following examples. This can be your own data or one of the examples in the Raphtory documentation.
+You will need some test data to complete the following examples. This can be your own data or one of the examples in the
+Raphtory documentation.
 
-Once your data is loaded into a Raphtory graph, the graph needs to be saved into your working directory. This can be done with the following code, where `g` is your graph:
+Once your data is loaded into a Raphtory graph, the graph needs to be saved into your working directory. This can be
+done with the following code, where `g` is your graph:
 
 /// tab | :fontawesome-brands-python: Python
+
 ```{.python notest}
 import os
 working_dir = "graphs/"
@@ -21,6 +24,7 @@ if not os.path.exists(working_dir):
     os.makedirs(working_dir)
 g.save_to_file(working_dir + "your_graph")
 ```
+
 ///
 
 ## Starting a server
@@ -39,24 +43,31 @@ This option is the simplist and provides the most configuration options.
 
 ### Start a server in Python
 
-If you have a [`GraphServer`][raphtory.graphql.GraphServer] object you can use either the [`.run()`][raphtory.graphql.GraphServer.run] or [`.start()`][raphtory.graphql.GraphServer.start] functions to start a GraphQL sever and Raphtory UI.
+If you have a [`GraphServer`][raphtory.graphql.GraphServer] object you can use either the [
+`.run()`][raphtory.graphql.GraphServer.run] or [`.start()`][raphtory.graphql.GraphServer.start] functions to start a
+GraphQL sever and Raphtory UI.
 
-Below is an example of how to start the server and send a Raphtory graph to the server, where `new_graph` is your Raphtory graph object.
+Below is an example of how to start the server and send a Raphtory graph to the server, where `new_graph` is your
+Raphtory graph object.
 
 /// tab | :fontawesome-brands-python: Python
+
 ```{.python notest}
 tmp_work_dir = tempfile.mkdtemp()
-with GraphServer(tmp_work_dir, tracing=True).start():
-    client = RaphtoryClient("http://localhost:1736")
+with GraphServer(tmp_work_dir, tracing=True).start() as server:
+    client = server.get_client()
     client.send_graph(path="g", graph=new_graph)
 
     query = """{graph(path: "g") {nodes {list {name}}}}"""
     client.query(query)
 ```
+
 ///
 
 You can set the port in `RaphtoryClient()` to the port the GraphQL server should run on.
 
-The `path` parameter is always the graph in your server that you would like to read or update. So in this example, we want to send `new_graph` to graph `g` on the server to update it.
+The `path` parameter is always the graph in your server that you would like to read or update. So in this example, we
+want to send `new_graph` to graph `g` on the server to update it.
 
-The `graph` parameter is set to the Raphtory graph that you would like to send. An additional `overwrite` parameter can be stated if we want this new graph to overwrite the old graph.
+The `graph` parameter is set to the Raphtory graph that you would like to send. An additional `overwrite` parameter can
+be stated if we want this new graph to overwrite the old graph.