Wojciech Mitros

Results 16 issues of Wojciech Mitros

Currently, the initial values of UDA accumulators are converted to strings using the to_string() method and from strings using the from_string() method. The from_string() method is not implemented for collections,...

This patch can be treated as a follow-up to #10341, or as a preparation before migrating from the lacking C++ wasmtime bindings to our custom implementation that will use the...

Currently, UDAs can't be reused if Scylla has been restarted since they have been created. This is caused by the missing initialization of saved UDAs that should have inserted them...

This series adds the implementation and usage of rust wasmtime bindings. The WASM UDFs introduced by this patch are interruptable and use memory allocated using the seastar allocator. This series...

This series is a reupload of #13792 with a few modifications, namely a test is added and the conflicts with recent tablet related changes are fixed. See https://github.com/scylladb/scylladb/issues/12379 and https://github.com/scylladb/scylladb/pull/13583...

backport/none

Currently, when a view update backlog is changed and sent using gossip, we check whether the strtoll/strtoull function used for reading the backlog returned LLONG_MAX/ULLONG_MAX, signaling an error of a...

area/materialized views
backport/5.2
backport/5.4
backport/6.0

When gossiping the view update backlog https://github.com/scylladb/scylladb/blob/4433d2e10e1764609e98b59273b298720d301ca7/service/misc_services.cc#L237-L262 We get the backlog using `storage_proxy::get_view_update_backlog()`: https://github.com/scylladb/scylladb/blob/4433d2e10e1764609e98b59273b298720d301ca7/service/storage_proxy.cc#L2444-L2446 Which takes the backlog from the `node_view_update_backlog`: https://github.com/scylladb/scylladb/blob/4433d2e10e1764609e98b59273b298720d301ca7/db/view/view.cc#L2628-L2644 However, the received backlog is not updated if...

area/materialized views

When performing a write, we should update the view update backlog on the node and shard where the mutation is actually applied, and potentially also on the coordinator of this...

area/materialized views
backport/none

Currently, there are 2 ways of sharing a backlog with other nodes: through a gossip mechanism, and with responses to replica writes. In gossip, we check each second if the...

area/materialized views
backport/none

We have 3 sources of the view update backlog: 1) The view update semaphore on each shard: https://github.com/scylladb/scylladb/blob/2d9142250eac278286428f52f62d339691d3598a/replica/database.hh#L1847-L1849 2) The cached view update backlogs for all shards that need to...

area/materialized views