virgodb 0.3.0-x86_64-linux-gnu → 0.4.2-x86_64-linux-gnu

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6141e1a5628b4293f7d63bd3143fe20bcbff6f697df38fc67c1da4c2669369ab
-  data.tar.gz: 7814e9e3a10ba0ce4e5126e492d38410637aa818d21abb4352b6f038fc9b4139
+  metadata.gz: c1f9d93ae7a3e693c2d7f2d7ba19a30ea89a3e54c53c7e9ab604eadc3afe3eda
+  data.tar.gz: c25d394c1ee0e2554abebdbcc58233f6fb13a816b8676e916861511e8689f81a
 SHA512:
-  metadata.gz: '0468833ba6f07aed2d56ea13ca5d158a523fb64486ec4fa5259c969200f9c4e991fb96a545ad26a78c8531460855c59dcbcc0904be5a8d43f558dd2bb4f27255'
-  data.tar.gz: 475c654f9a604b83c05b0036c4cdffb478c339b05fb794a9cef445b5244584394cef90289bbb57cdc8f7c65a8918fb7a8111e545d9a790c6b375eca454929a47
+  metadata.gz: bc0fce13a70b6de835b7ad1077520915ef5baacaa48b7bacc69cfe35607de9e9e5be1e717e0fa3a9e654c5a8d0f7624cb4be8c6db7b957ca7026842c498b8b1e
+  data.tar.gz: bc9891ee73cffeb89a56f2512cc8047af9779cdac1c3b6671a4c542c2c38ed29eb8e337831c78e6aa72ed911dfc537de2f0a2cbc1090a30c8c6681506321fd8c

data/lib/virgodb/table.rb

@@ -4,7 +4,8 @@ require "json"
 require "fileutils"
 
 module Virgodb
-  # A memoized Writer + its maintenance thread, both created lazily on first
+  # A memoized Writer + its maintenance thread + its periodic flush timer
+  # (see `ensure_flush_timer_started` below), all created lazily on first
   # use -- not eagerly at process boot, since Writer.new and
   # Virgodb.start_maintenance both raise if this table hasn't been migrated
   # yet, and eager init would crash the whole process on that instead of
@@ -44,6 +45,7 @@ module Virgodb
       @tuning = tuning
       @mutex = Mutex.new
       @maintenance_started = false
+      @flush_timer_started = false
     end
 
     attr_reader :manifest_path
@@ -124,6 +126,18 @@ module Virgodb
       Virgodb.release_maintenance_lease(@manifest_path, @sql_table_name, holder.to_s)
     end
 
+    # Extends a lease claimed via `claim_maintenance_lease` above without
+    # needing it to expire first -- calling `claim_maintenance_lease` again
+    # on a lease you already validly hold is a guaranteed no-op, not a
+    # renewal (see `Manifest::renew_maintenance_lease`'s own doc comment).
+    # For a caller whose work under the lease might run longer than one
+    # fixed grant. Returns `false` (not an error) if `holder` no longer
+    # matches the current holder -- treat that as "lost the lease," not
+    # something to retry blindly.
+    def renew_maintenance_lease(holder:, lease_duration_secs:)
+      Virgodb.renew_maintenance_lease(@manifest_path, @sql_table_name, holder.to_s, lease_duration_secs)
+    end
+
     private
 
     def writer
@@ -132,6 +146,7 @@ module Virgodb
 
     def build_writer
       ensure_maintenance_started
+      ensure_flush_timer_started
       Virgodb::Writer.new(@manifest_path, @sql_table_name, @tier1_max_rows, @tier1_max_age_secs, @data_dir)
     end
 
@@ -142,5 +157,41 @@ module Virgodb
       Virgodb.start_maintenance(@manifest_path, @sql_table_name, @data_dir, @key_column, @sort_by, @tuning, @partition_column)
       @maintenance_started = true
     end
+
+    # Periodically force-flushes this table's Tier 1 buffer on a real
+    # timer, independent of write traffic -- see `Writer#write_row`'s own
+    # doc comment (crates/virgodb_ruby/src/writer.rs) for the full
+    # reasoning: write_row's inline flush only fires on the ROW-COUNT half
+    # of tier1_max_rows/tier1_max_age_secs, not age, because an actual
+    # flush fsyncs (storage::write_inline_file) and checking age inline
+    # meant whichever request happened to cross that threshold paid for a
+    # real disk sync on its own thread -- under low/sparse traffic, that
+    # was effectively every request. This background thread is what makes
+    # tier1_max_age_secs a real wall-clock bound again, off any caller's
+    # own thread -- moved here (not left to each host app to build its
+    # own copy) so every consumer of this gem gets the same guarantee
+    # write_row itself no longer provides alone.
+    #
+    # Uses `flush!` (force-flush regardless of policy) through the SAME
+    # `@mutex` write_row/tombstone already use -- a Ruby Thread cooperates
+    # correctly with that lock, unlike a Rust-native thread would (the
+    # underlying Writer's RefCell isn't safe for genuine concurrent access
+    # outside Ruby's own GVL/Mutex protection -- see this class's own doc
+    # comment above). No locking needed around @flush_timer_started itself:
+    # this method only ever runs from inside build_writer, which only ever
+    # runs once per instance, already inside `writer`'s own @mutex-guarded
+    # lazy-init (`@writer ||= build_writer`).
+    def ensure_flush_timer_started
+      return if @flush_timer_started
+
+      @flush_timer_started = true
+      Thread.new { loop { sleep(@tier1_max_age_secs); flush_timer_tick } }
+    end
+
+    def flush_timer_tick
+      flush!
+    rescue => e
+      warn "[virgodb] #{@sql_table_name} periodic flush failed: #{e.class}: #{e.message}"
+    end
   end
 end

data/lib/virgodb/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Virgodb
-  VERSION = "0.3.0"
+  VERSION = "0.4.2"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: virgodb
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.4.2
 platform: x86_64-linux-gnu
 authors:
 - virgodb
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-09-02 00:00:00.000000000 Z
+date: 2026-09-03 00:00:00.000000000 Z
 dependencies: []
 description: |
   Embeds virgodb (an OLAP engine backed by Parquet + DataFusion) directly into a Ruby process