Layer 2: Storage
Single-purpose storage interfaces. Each store does one thing.
SqlJournalStore
SQL statement buffer for write-ahead logging: an append-only, keyless table per dataset carrying the parquet statement columns. A flush rotates the whole journal into a timestamped segment (creating a fresh table in the same DDL transaction), hands the segment over as Arrow batches, and drops it once the consumer has written them – so cleanup never deletes rows, nothing can deadlock against concurrent writers, and a failed write keeps its rows for the next flush. Concurrent flushes on one dataset are serialized by flush_lock(), and only the store that holds the rows drains them – ApiJournalStore writes, counts and clears, but does not flush. get_journal resolves the concrete store – SqliteJournalStore / PostgresJournalStore locally (picked by uri), ApiJournalStore when the lakehouse uri points at an API.
ftm_lakehouse.storage.journal.sql.SqlJournalStore
Bases: BaseJournalStore[SqlJournalWriter]
SQL-based journal for buffering writes.
An append-only heap per dataset, carrying the producer statement columns
(JOURNAL_SCHEMA). A flush claims
the whole table by renaming it to a timestamped segment and creating a
fresh one in the same DDL transaction, streams the segment out as Arrow,
and drops it – so cleanup is a catalog operation, never a DELETE.
Dialect specifics live in the subclasses SqliteJournalStore and
PostgresJournalStore, picked once by sql_journal – the
same construction-time choice get_journal makes for the api store.
Source code in ftm_lakehouse/storage/journal/sql.py
131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 | |
lock_timeout = None
class-attribute
instance-attribute
Dialect bound on how long the rotation waits for in-flight writers.
acquire()
Take a connection for a writer's inserts.
A plain connect here – the engines in this module all use
non-caching pools, so a sqlite connection costs what it costs.
PostgresJournalStore overrides it to borrow from a pool of
its own, because the ADBC write path bypasses the engine entirely
and a cold ADBC connection is expensive.
Source code in ftm_lakehouse/storage/journal/sql.py
clear()
Delete all rows for this dataset. Returns count of deleted rows.
Source code in ftm_lakehouse/storage/journal/sql.py
connect()
count()
Count rows for this dataset, across all segments.
Source code in ftm_lakehouse/storage/journal/sql.py
dispose()
flush_batches()
Rotate the journal, then stream each segment as Arrow.
Held under flush_lock for the whole
window – a second flush on the same dataset yields nothing rather than
draining the first one's segment twice. Segments left by a crashed flush are picked up
here, which is the whole of orphan recovery.
Segments stream out unordered: rows carry no shard column to sort
on, and the sort this used to do was an un-indexed pass over the whole
segment that had to finish before the first row could be handed over.
A drained table therefore spans shards and
append writes one
file per partition it touches, which compact bin-packs.
Source code in ftm_lakehouse/storage/journal/sql.py
flush_lock()
Hold this dataset's flush window, or report that someone else has it.
Rotation alone does not serialize concurrent flushes: the second one
finds the live table already empty, skips rotating, and drains the
first one's segment – duplicating every row and then failing on the
double DROP. The lock must release itself when a flusher dies,
or a crash would strand the segment it was draining.
Source code in ftm_lakehouse/storage/journal/sql.py
insert_batch(conn, batch)
iterate_entity(entity_id)
Iterate the live statements of one entity, across all segments.
A scan of the journal per call – the heap carries no index by design
(see journal_table). That is
the delete path's cost, and it is bounded by how much sits unflushed.
Source code in ftm_lakehouse/storage/journal/sql.py
read_segment(name)
release(conn)
Hand a writer's connection back.
Closing is the whole of it in both dialects, though it means
different things: file-backed sqlite drops the connection, in-memory
sqlite returns the one shared connection to its StaticPool, and
PostgresJournalStore checks the ADBC connection back into
its pool – rolled back on the way in, so the next writer never
inherits an aborted transaction.
Source code in ftm_lakehouse/storage/journal/sql.py
ParquetStore
Delta Lake parquet storage for statements, partitioned by (shard, bucket, origin). Writes are append-only; deduplication, first_seen folding, and tombstone reaping happen in three independent async ops (compact / merge / vacuum), all coordinated by a dataset-wide write fence. Reads target a live WHERE deleted_at IS NULL view with no read-time dedupe, so queries, exports, and statistics assume an optimized store – run merge before reading. shard is the odd one out: the only operation that moves rows between partitions, rewriting the whole store onto a different shard count.
ftm_lakehouse.storage.parquet.ParquetStore
Single Delta Lake table (per dataset) partitioned by (shard, bucket,
origin).
Writes are append-only: append sorts a per-partition batch in
memory and writes one parquet file. Reads target the live statement
view (deleted_at IS NULL) registered on the LakeStore
connection and assume a store made canonical by
merge – merge,
compact, vacuum are
load-bearing for read correctness, not just cleanup.
Source code in ftm_lakehouse/storage/parquet.py
120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 | |
exists
property
Check existence of deltatable
needs_merge
property
Whether any partition has been written to since its last merge.
Reads are canonical only on a merged store – the live statement
view does no read-time dedupe – so paths that publish canonical rows
(export_diff)
check this first.
The dataset-level statements/last_optimized tag cannot answer it:
OptimizeOperation stamps
that with its start time while merge bumps
statements/last_updated on completion, so the dataset pair reads
stale right after a successful optimize. The per-partition tags are
the ones merge itself compares, stamped in the order that
makes the comparison sound.
version
property
Current version of the main Delta table.
append(batch)
Append a batch of statements.
Rows arrive in
JOURNAL_SCHEMA – without a
shard column – and _with_shard derives it here. Batches
may span any number of shards; each one becomes a parquet file per
(shard, bucket, origin) partition it touches, so a bigger batch
costs fewer files, not more. The method splits by bucket so each
write_deltalake call uses the bucket-appropriate
writer_properties (small vs. large profile). Duplicates land as
separate rows and are reaped by merge.
Deliberately does not sort. Nothing downstream reads in physical
order, and merge rewrites every partition an append touched
into the file sort order anyway.
Held under the shared side of the write fence
(_append_fence): concurrent appends run in parallel – Delta
serializes their commits via optimistic concurrency – while
merge / compact /
vacuum wait for the append markers to drain
before rewriting partitions. Table creation happens
once in _ensure_table (under the exclusive lock, so two
racing imports can't both commit version 0); the write loop
itself always appends. Each touched (shard, bucket, origin)
partition is stamped with a last_updated freshness tag inside
the fence and before the Delta writes, so a later merge
can skip partitions that didn't change – see _mark_updated
for why both halves of that ordering are load-bearing.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
batch
|
Table
|
PyArrow table with the columns of
|
required |
Source code in ftm_lakehouse/storage/parquet.py
compact()
Bin-pack small parquet files within each partition.
Cheap maintenance – Delta's OPTIMIZE compact only rewrites small
files into larger ones; it does not collapse duplicate rows or drop
tombstones (use merge for that). Held under the exclusive
maintenance fence (_maintenance_fence).
Source code in ftm_lakehouse/storage/parquet.py
count(q=None)
Count distinct entities matching q.
A single count(DISTINCT entity_id) aggregate (not the
per-partition read iteration), so it's cheap enough to short-circuit an
export that would otherwise iterate every partition for zero results.
Compiled through self.source, so a schema filter folds into
the same bucket IN (...) prune as _compile_query –
non-matching partitions are pruned, not just file-skipped. Like the
other aggregates it assumes an optimized store.
Source code in ftm_lakehouse/storage/parquet.py
delete_origin(origin)
Physically drop every row of one origin.
origin is a partition column, so the predicate prunes to whole
partitions and Delta drops their files instead of rewriting rows –
unlike merge's tombstone reap this is
immediate, with no grace period and nothing left to collapse. Held
under the exclusive maintenance fence
(_maintenance_fence), like the other partition-level
rewrites.
Stamps
STATEMENTS_OPTIMIZED
on completion when rows were removed – dropping a partition moves the
store's canonical content exactly as a merge does, so exports,
statistics and diffs have to go stale against it. The append-side
STATEMENTS_UPDATED clock is deliberately left alone: no rows
landed. The dropped partitions' own tags are left behind too – they
no longer enumerate, and a later write to the same origin stamps a
fresh last_updated over the stale last_optimized, so the
partition comes back dirty.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
origin
|
str
|
The origin tag to drop. |
required |
Returns:
| Type | Description |
|---|---|
int
|
Number of rows removed. |
Raises:
| Type | Description |
|---|---|
ValueError
|
If |
RuntimeError
|
When the write fence cannot be acquired. |
Source code in ftm_lakehouse/storage/parquet.py
destroy()
Destroy the deltalake by removing the transaction log in "_delta_log" directory. This is soft deleting, as the parquet files remain (but will be cleaned up on optimize --vacuum)
Source code in ftm_lakehouse/storage/parquet.py
evolve_schema()
Add the SHARDED_SCHEMA columns this table was created without.
Metadata-only Delta schema evolution – one commit against the table's
schema, no parquet file rewritten: delta_scan reads a column the
older files don't carry as NULL, which is the "absent" sentinel of
every nullable column anyway, so nothing is owed a re-merge.
Additive only – Delta has no metadata-only drop without column mapping,
so a column removed from SHARDED_SCHEMA needs a full rewrite
instead. Idempotent, and held under the exclusive maintenance fence.
Returns:
| Type | Description |
|---|---|
list[str]
|
Names of the columns added – empty if the table is already current |
list[str]
|
or does not exist yet. |
Source code in ftm_lakehouse/storage/parquet.py
get_entity_ids(q=None, *, source=None)
Get entity IDs for given query. Use self.source_raw to
target physical storage without tombstones merged
Source code in ftm_lakehouse/storage/parquet.py
merge(force=False)
Collapse duplicates and reap expired tombstones, partition by partition.
For each (shard, bucket, origin) partition, runs the merge
query against statement_raw (non-fragment rows: keep latest
row per id by last_seen DESC; fragment rows: keep the
latest emission per (entity_id, prop, fragment) group; fold
first_seen to the min; drop tombstones older than the grace
cutoff) and atomically overwrites that partition via
partition_filters. Held under the exclusive maintenance fence
(path.LOCK + append-marker drain, _maintenance_fence).
Only partitions whose last_updated freshness tag is newer than
their last_optimized tag are rewritten – a partition untouched
since its last merge is skipped, so an optimize after a small
append rewrites only what changed instead of the whole store. Each
successful rewrite stamps last_optimized.
Because a clean partition is never revisited by a default merge,
a tombstone sitting in an otherwise-idle partition is not
physically reaped once it passes the grace window until the next
write touches that partition – this only defers disk reclamation;
read correctness is unaffected (the live view hides tombstones
regardless). force=True bypasses the skip and re-evaluates
every partition, so a forced merge (with
LAKEHOUSE_GRACE_PERIOD_DAYS=0 for an immediate purge)
physically reaps cold tombstones too.
Load-bearing for reads: the live statement view does no
dedupe, so a partition's rows are only canonical – one row per id,
fragment supersession applied, first_seen / last_seen
folded – after this runs. Reads assume every touched partition has
been merged since its last write.
A partition whose parquet size suggests the merge pipeline would
outgrow LAKEHOUSE_DUCKDB_MEMORY_LIMIT
(merge_slice_count) is merged
in contiguous entity_id range slices instead of one pass: a
reservoir sample picks boundaries
(slice_ranges), one merge
query runs per range – strictly sequentially, so only one sort
window is materialised at a time – and the slices chain into the
single atomic partition overwrite (_chained_reader). No
dedupe group spans an entity_id bound, ranges stream in
ascending order, so output content, file sort order and the Delta
commit are identical to a single-pass merge.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
force
|
bool
|
Rewrite every partition regardless of freshness tags. |
False
|
Source code in ftm_lakehouse/storage/parquet.py
643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 | |
query(q=None)
Query entities from the store.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
q
|
Query | None
|
Optional |
None
|
Yields:
| Type | Description |
|---|---|
StatementEntities
|
StatementEntity objects matching the query. |
Source code in ftm_lakehouse/storage/parquet.py
query_statements(q=None)
Query ordered Statements from the store.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
q
|
Query | None
|
Optional |
None
|
Yields:
| Type | Description |
|---|---|
Statements
|
|
Statements
|
|
Statements
|
handed straight to |
Statements
|
|
Statements
|
and land in the merge group it came from. |
Source code in ftm_lakehouse/storage/parquet.py
shard(shards)
Re-key the whole store onto shards entity-hash shards.
The physical half of a shard-count change: every row's shard
is recomputed from its entity_id
(build_shard_sql) and the
store is rewritten into the new partition layout. bucket and
origin are invariant under re-sharding – only shard
moves – so the rewrite runs one write_deltalake per
(bucket, origin) group, replacing that group's partitions
wholesale via predicate while the group's source partitions
stream in through a single chained reader
(_chained_reader). Nothing is materialised in Python, and
each group's rows land in one atomic Delta commit with the
bucket-appropriate writer_properties.
One writer per target partition stays open across a group's
write, so the target file size is scaled down by the shard count
(shard_target_file_size) to
keep their combined buffers bounded; the resulting small files are
what the follow-up compact bin-packs.
Deliberately no dedupe and no sort: the use case is a store whose
queries have outgrown their shard count, and a re-shard moves
rows rather than deciding which survive. Every rewritten
partition is therefore re-stamped as dirty, so the next
merge restores canonical content and file sort order –
run optimize afterwards. The stamps are per-partition only;
the dataset-level clocks stay put, because a re-shard changes
physical layout, not canonical content, and the exports keyed on
them are byte-identical either side of it.
Idempotent: the target shard is a function of entity_id and
the target count alone, never of the value a row currently
carries, so a run interrupted between group commits is repaired
by running it again.
Held under the exclusive maintenance fence
(_maintenance_fence), which blocks parquet appends but
not journal writes. Journalled rows carry no shard key, so a
flush after this returns places them under the new count – but
one landing between the rewrite and the config write still resolves
the old one. Run with writers stopped.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
shards
|
int
|
Target shard count; |
required |
Source code in ftm_lakehouse/storage/parquet.py
stats()
Compute statistics from the statement store.
Runs ftmq's aggregation SQL over the live statement view. Assumes
an optimized store: the live view is a plain deleted_at IS NULL
scan, so the aggregates are correct only once merge has made
the store canonical (one row per id, supersession applied). Run
optimize before heavy stats workloads.
Source code in ftm_lakehouse/storage/parquet.py
sweep(csv_key=None, tee=True)
One scan of the live view, teeing Arrow batches two ways.
Each (shard, bucket) partition streams straight from DuckDB as
Arrow batches (_execute_partitioned). Every batch can go to a
pyarrow CSV writer and be handed on as row dicts, so a caller
that wants both statements.csv and the rows behind it pays for one
scan rather than writing the csv and reading it back.
Rows come from RecordBatch.to_pylist – a bulk conversion in C,
cheaper than the Row-object marshalling of
_query_statement_data – and
carry STATEMENT_CSV_COLUMNS, which covers everything an entity
aggregation needs. They arrive entity-contiguous (the select orders by
entity_id and an entity lives in one partition), so
aggregate_unsafe can fold them directly.
The csv handle lives for the generator's lifetime; abandoning the
generator closes it through the usual GeneratorExit unwind, so the
codec trailer is always written.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
csv_key
|
str | None
|
Store key to write the sorted statements csv to.
|
None
|
tee
|
bool
|
Yield row dicts. |
True
|
Yields:
| Type | Description |
|---|---|
StatementDict
|
|
Source code in ftm_lakehouse/storage/parquet.py
unlock()
Forcibly release the dataset write fence.
Operator escape hatch for the case where a writer process died
with the fence held (or an attacker held it on purpose). Releases
both sides: the exclusive .LOCK file and any append markers
under .LOCK-APPENDS/.
Use sparingly – breaking a fence that's still held by a live writer can corrupt a write in flight. Confirm no process is actively writing before running.
Returns:
| Type | Description |
|---|---|
bool
|
|
bool
|
fence was clear. |
Source code in ftm_lakehouse/storage/parquet.py
vacuum(retention_hours=0)
Delete obsolete parquet files no longer referenced by the Delta log.
Tombstoned files (replaced by merge /
compact) become orphans on disk; vacuum
prunes them once they're past
retention_hours. Held under the exclusive maintenance fence
(_maintenance_fence).
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
retention_hours
|
int
|
Keep files newer than this many hours. |
0
|
Source code in ftm_lakehouse/storage/parquet.py
TagStore
Key-value freshness tracking.
ftm_lakehouse.storage.tags.TagStore
Bases: Tags
Key-value store for freshness tracking.
Tags are timestamps stored as key-value pairs, used to track when resources were last updated and determine if processing is needed.
Layout: tags/{tenant}/{key}
This store has the "tags/{tenant}" key prefix set, so clients must use relative paths from there.
Source code in ftm_lakehouse/storage/tags.py
is_latest(key, dependencies)
Check if the tag is more recent than all dependencies.
Parameters:
| Name | Type | Description | Default |
|---|---|---|---|
key
|
Uri
|
Tag key to check |
required |
dependencies
|
Iterable[Uri]
|
Tag keys that this key depends on |
required |
Returns:
| Type | Description |
|---|---|
bool
|
True if key is newer than all dependencies, False otherwise |
Source code in ftm_lakehouse/storage/tags.py
set(key, timestamp=None)
VersionStore
Timestamped snapshots for config / index files.