Make TimeseriesOptions comparable via IDL-generated comparison operators

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      TimeseriesOptions cannot currently be safely included in IDL generate_comparison_operators because its fixedBucketing field is an OptionalBool.

      The IDL relational-operator infrastructure (idl::relop::BasicOrderOps) has no specialization for OptionalBool, so it falls back to comparing through OptionalBool::operator bool(), which returns value_or(false) and therefore collapses an unset value and an explicit false into the same value.

      Since OptionalBool is serialized only when explicitly set, this conflation means generated equality/ordering would silently treat two distinct durable states (unset vs false) as equal.

            Assignee:
            Unassigned
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: