5.2.8. Content Filters and Query Conditions

5.2.8.1. [Critical] Unexpected data loss when using writer-side content filtering and changing QoS

This issue was fixed in release 6.1.0, but not documented at that time.

Consider the following scenario:

There are some DataReaders that are not using content filtering and other DataReaders that are using writer-side content filtering.
There is a DataWriter whose QoS (or whose Publisher’s QoS) is incompatible with the DataReaders.
At some point, the DataWriter (or Publisher) changes its QoS to be compatible with the DataReaders.
Then, the DataWriter writes some samples.

None of the samples were sent to the DataReaders that did not use content filtering.

[RTI Issue ID CORE-15760]

A late-joining DataReader setting protocol.virtual_guid may have failed to receive historical samples from a matching DataWriter.

This issue only occurred when all of the following conditions were met:

writer_qos.protocol.push_on_write was set to TRUE (default) on the DataWriter.
The DomainParticipant containing the late-joining DataReader also contained other DataReaders on the same Topic using ContentFilteredTopics.

[RTI Issue ID CORE-15992]