You're about to publish a count of homes that “switched from rent to sale”. The join on propertyId looks sensible. The change flag comes from comparing mode .
That's where the small dread belongs. A property can advertise rent and sale together, and the Actor includes both prices when the source publishes them.
A change in collection mode does not establish a change in the property's advertised offers.
A collection label isn't an offer event
The awkward value is byUrls . Alongside rent and buy , it describes loading specific listings, rather than an advertised transaction.
Treating that field as a property's exclusive status would turn a different retrieval path into a market event. SQL will count it quite happily.…