Remove Vector Set Preview Checklist

[kevin-montrose]

Now that V1 is no longer receiving Vector Set updates, we can starting working through all the things we need to do to get rid of the --enable-vector-set-preview flag.

Link PRs that accomplish tasks to this issue.

In no particular order:

• Recovery (and resumption of interrupted) quantization tables and vectors (Add quant restart support to create_index and bump diskann version to 4.0.0 #1926 ; though still needs additional testing)
• Additional testing for ^
• Logging FFI additions (Update DiskANN FFI #1992)
• Implement continue_search for too-big-for-initial-buffers searches (Update DiskANN FFI #1992)
• Tests that VADD can update vectors correctly
• Remove limit on # of Vector Sets (see Remove Vector Set Limits #1900)
• RENAME(NX) support (see Implement RENAME(NX) Support For Vector Sets #1913)
• Tests that all commands either WRONGTYPE on Vector Sets, or work as expected (Add tests (and fix bugs) for commands WRONGTYPE'ing appropriately against Vector Sets #1935)
  • Subset here is that overwriting a Vector Set cleans up the Vector Set as expected
• Tests that migrated Vector Sets retain expiration metadata
• VADD updates need to be correctly ordered in the AOF and replayed in correct order on replicas
• RESP3 support for VSIM (see Implement RESP3 for VSIM (and VEMB) and RAW for VEMB #1916)
• RAW support for VEMB (see Implement RESP3 for VSIM (and VEMB) and RAW for VEMB #1916)
• VCARD (Add tests (and fix bugs) for commands WRONGTYPE'ing appropriately against Vector Sets #1935)
• VISMEMBER (Add tests (and fix bugs) for commands WRONGTYPE'ing appropriately against Vector Sets #1935)
• VLINKS (Update DiskANN FFI #1992)
• VRANDMEMBER (Update DiskANN FFI #1992)
• VSETATTR (Implement VSETATTR #2001)
• Match (or exceed) Redis limits in filter compilation for compatibility
• Exclude internal vectors data from KEYS, SCAN, etc. (Vector-set internal records are exposed/counted by DBSIZE, SCAN, KEYS, and INFO KEYSPACE #1921 ; see Exclude internal records from stats #1922)

---

VRANGE support has been removed from the checklist. VRANGE is a weird command that has a number of footguns for the large Vector Sets we expect to see, in particular - and + options could result in gigabytes of response data. Given that there's no trivial implementation path and the command is of limited utility, we'll wait until there's concrete demand to implement it.