Precompiled 2024-04-05-1f403e7

Fixed incorrectly bumping retention confirmed deleted ts (#24332)

Made it such that we don't bump the confirmed deleted timestamp of document retention on dry runs

GitOrigin-RevId: e5576a096c65195f6437fa7072896616695f4d7f

Precompiled 2024-04-04-ff31d60

Double the batch size up to 8, if we only see tombstones (#24275)

Turns out if you do .first() you are only fetching one row at a time. This is a problem since if you have 100 deleted rows, you will end up dong 100 database queries. Instead dynamically resize the batch. I have put a more conservative limit of 8 to see how much it helps but it could be larger.

In general, we should perhaps always be using this technique since currently the client just guesses the size_hint. If we use filter, we always fetch 100 rows. Instead we could be using dynamic sizing.

Similarly, if the client asks for take(10000) rows, we are going to fetch up to 5k. This might be too large if those rows are big. So some dynamic sizing with proper estimates of size might help there as well.

For now, do the simple, obvious thing.

GitOrigin-RevId: d8b69fcb370ce97399da7e94a55d0ffc277bfd65

Precompiled 2024-04-03-f3b959a

Set retention_running before starting retention in IndexWorker (#24076)

Allow retention worker to process the backfilled index while we are caching up on retention.

GitOrigin-RevId: 25a5e0eafc64e8391d0504abc8df7d7afbad41ff

Precompiled 2024-04-02-cbd5e06

JS: Export OptionalRestArgsOrSkip (#24194)

GitOrigin-RevId: 69720e7401fe77132f884e51b3f4d7eacc3dfd1a

Precompiled 2024-04-01-dde0613

Unset the dynamic linking compiler optimizations in precompile (#24195)

Since we're building a precompiled binary, we want the full binary
statically linked.

GitOrigin-RevId: 294e35084e3c023caa9b410ddec36155d3e6147d

Precompiled 2024-04-01-b6252a0

Turn MAX_PUSH_BYTES into a knob. (#24162)

GitOrigin-RevId: 6f10f889ca70ba97a7e818af99fa951d563b8e56

Precompiled 2024-03-29-9da04db

Add retention running flag to BackfillIndexState (#24069)

Create a new index_created_lower_bound field so we can update index entry in backfilled state. Currently, we rely on it never updating. Also add retention_running flag so we can so the period we don't run retention for in newly backfilled indexes is minimal.

This change adds and populates the new fields and adds a migration to backfill them properly. I am going to change IndexWorker in a separate PR.

GitOrigin-RevId: 1b28ed0391f203a373ad4706cfcc65b2628eece2

Precompiled 2024-03-28-68f7a74

sizeOfAllTables system udf (#24059)

GitOrigin-RevId: 8c1c08529b42ecc131758e99cd863670e1df2c94

Precompiled 2024-03-26-cc876c6

Precompile to zip files (#23982)

This means that the size is ~35MB instead of ~100MB.
Also, it maintains the executable bit, simplifying the process after unzip.

GitOrigin-RevId: 69a764c2548a81f24b8de5915aba957f9c5a09d9

Precompiled 2024-03-26-831f54f

Rename requestId to executionContext in json (#23879)

Rename the name of the field in the json seriealization. Make the change  forwards/backwards compatible.

GitOrigin-RevId: fdcf8e4d9232306ef8fe54896afa0565baa28c35