Weekly meeting 2025 09 10

Agenda

• Review initial analysis of the valkey 9 implication on search - https://github.com/valkey-io/valkey-search/issues/364
  • Going to delay to next week for more attendance
• READONLY user experience, I want to discuss this approach - https://github.com/valkey-io/valkey-search/pull/356
  • Discussed briefly - didn't have quorum - but it seems that side-effecting READONLY shouldn't be the complete story
  • Ideally, users could specify some lag tolerance in the query
  • Default search behavior may make sense to have a server-level option
• ASM integration
  • We will need the core to implement a module consistency check
  • Zvi brought up concerns with delaying slot migration for index consistency, suggested HNSW may make sense to exclude due to long indexing times
  • Jacob discussed current ideas - one of which was sending lag back to the source from the target,
  • Zvi brought up that it may be useful to have a general lag indicator broadcasted across the cluster, which also helps with fanout where we may want to specify a maximum lag
  • Plan is to draft up a proposal for using the cluster bus to send lag indicator from target to source, and for source to use this lag indicator to determine when it is safe to begin the handover
• https://github.com/valkey-io/valkey-search/issues/344#issuecomment-3222713767
  • Discussed, and it does seem like there is a problem with inline filtering
  • Karthik to investigate how to compose the EntriesFetchers for more accurate filtering