kglite 0.10.22

Pure-Rust knowledge graph engine — Cypher pipeline, snapshot/working CoW transactions, columnar/mmap/disk storage backends, optional dataset loaders (SEC EDGAR, Sodir, Wikidata). PyO3 wrappers live in the sibling kglite-py crate (the Python wheel); embeddable directly from any Rust binary without PyO3 in the dep tree.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56

//! Pure-Rust fetcher for the Wikimedia `latest-truthy` RDF dump.
//!
//! The crate has no Python or PyO3 dependency. It owns only the dump
//! *cache* lifecycle — the resumable download and the staleness /
//! cooldown state machine. The N-Triples → graph build already lives
//! in the main `kglite` crate (`KnowledgeGraph::load_ntriples`), so it
//! is *not* re-implemented here.
//!
//! PyO3 bindings live in the main crate under `src/wikidata.rs`; the
//! Python-facing API is `kglite.datasets.wikidata.open(...)`.
//!
//! ```text
//! lib (public API)
//!   ├── cache    ensure_dump + remote_last_modified — staleness state machine
//!   ├── client   HEAD probe + resumable streaming download
//!   ├── layout   Workdir — dump + .part paths
//!   └── error    WikidataError
//! ```

pub mod cache;
pub mod client;
pub mod error;
pub mod freshness;
pub mod layout;

pub use cache::{ensure_dump, remote_last_modified};
pub use client::{RemoteMeta, WikidataClient};
pub use error::{Result, WikidataError};
pub use freshness::{
    age_days, decide, file_mtime_utc, read_remote_mtime_from_source_meta, CacheDecision,
    FreshnessInputs,
};
pub use layout::{Workdir, DUMP_FILE, DUMP_URL};

// Blocking-runtime wrappers for bindings without their own async
// runtime. Each one spins up a single-thread tokio runtime via
// `crate::datasets::blocking::run` and blocks on the async fetcher.
// See `crate::datasets::blocking` for the rationale.

use chrono::{DateTime, Utc};
use std::path::PathBuf;

/// Sync wrapper around [`ensure_dump`] — see [`crate::datasets::blocking`]
/// for the rationale. Pure convenience for synchronous bindings.
pub fn ensure_dump_blocking(
    workdir: &Workdir,
    cooldown_days: i64,
    verbose: bool,
) -> Result<(PathBuf, Option<DateTime<Utc>>)> {
    crate::datasets::blocking::run(ensure_dump(workdir, cooldown_days, verbose))
}

/// Sync wrapper around [`remote_last_modified`].
pub fn remote_last_modified_blocking() -> Option<DateTime<Utc>> {
    crate::datasets::blocking::run(remote_last_modified())
}