Summary

What is the problem or use case, what are we trying to achieve?

The specification does not discuss the issue of considering whether two vectors are equal. As different drivers approach this, they are bound to have opinions. This is a placeholder for a discussion of how to treat equality, both in binary and in-memory representations.

FYI: boris.dogadov@mongodb.com, shane.harvey@mongodb.com, steve.silvester@mongodb.com,kevin.albertson@mongodb.com, qingyang.hu@mongodb.com, geert.bosch@mongodb.com, mihir.patil@mongodb.com, jeff.yemin@mongodb.com 

Motivation

Consistency, and well-defined behavior.

How does this affect the end user?

Are they blocked? Are they annoyed? Are they confused?
Confused.

How likely is it that this problem or use case will occur?

Main path? Edge case?
It is likely that a user will write tests simply using ==

If the problem does occur, what are the consequences and how severe are they?

_Minor annoyance at a log message? Performance concern? Outage/unavailability?
Failover can't complete?_

Not sure.

Is this issue urgent?

Does this ticket have a required timeline? What is it?

Spec should be updated and drivers updated within a quarter.

Is this ticket required by a downstream team?

Needed by e.g. Atlas, Shell, Compass?

Server team is involved because we want consistency.

Is this ticket only for tests?

Does this ticket have any functional impact, or is it just test improvements?

Both.

Acceptance Criteria

What specific requirements must be met to consider the design phase complete?

Agreement on what equality SHOULD or MAY be defined in the implementation of drivers, and for what data types.