[ENH]: Rust frontend proptest for collection operations against SQLite impl

[codetheweb]

Description of changes

Adds a Rust proptest for collection operations against the SQLite implementation. Follow up work includes:

• adding a test against distributed (requires changes to the compaction API)
• enabling KNN queries
• improving shrinking
• backtesting against previous correctness bugs

The proptest outputs stats about generated query selectivity after running as naive generation of requests for .get() will usually result in selecting all or no records. Example output:

Statistics:
  A total of 15646 log operations were created.
  .get() selectivity (570 total requests):
    .get() with a where clause only (64.74%):
      47.97% of queries returned no results
      23.31% of queries returned some results
      28.73% of queries returned all results
    .get() with a where clause & IDs (22.11%):
      69.05% of queries returned no results
      30.95% of queries returned some results
      00.00% of queries returned all results
    .get() with IDs only (13.16%):
      42.67% of queries returned no results
      57.33% of queries returned some results
      00.00% of queries returned all results

Note that 23% of queries returned only part of the collection when filtering with a where clause. This doesn't sound super high, but it started at 3-4% before I fixed filter generation to bias towards known values. We can make this higher if we want by tweaking a few parameters.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

n/a

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[codetheweb]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [TST]: enable KNN queries in proptest #3937
• [ENH]: Rust frontend proptest for collection operations against SQLite impl #3814 👈 (View in Graphite)
• [ENH]: add in-memory frontend impl #3902 : 1 other dependent PR (#3813 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.