6.11. Known Issues with Coherent Sets

6.11.1. Some coherent sets may be lost or reported as incomplete with batching configurations

If Connext 6.1.0 receives coherent sets from Connext 6.0.0 or lower using batching, coherent sets that are fully received and complete may be lost or marked as incomplete. (If the QoS subscriber_qos.presentation.drop_incomplete_coherent_set is set to FALSE, then the samples marked as incomplete won’t be dropped.)

[RTI Issue ID CORE-9691]

6.11.2. Copy of SampleInfo::coherent_set_info field is not supported

SampleInfo::coherent_set_info is not available when using take/read operations that do not loan the samples. The SampleInfo::coherent_set_info is always set to NULL when you call the take/read operations that do not loan the samples. To get the coherent_set_info value, make sure you use the read/take operations that loan the data.

In addition, the copy constructor and assignment operator in the Traditional C++ and Modern C++ APIs do not copy the SampleInfo::coherent_set_info field. It is always set to NULL. It is your responsibility to make the copy and handle memory allocation and deletion for this field.

[RTI Issue ID CORE-11215]

6.11.3. Other known issues with coherent sets

Coherent sets are not propagated through RTI Routing Service [RTI Issue ID ROUTING-657].

Group coherent sets are not persisted by RTI Persistence Service [RTI Issue ID PERSISTENCE-191].

Group coherent sets cannot be stored or replayed with RTI Recording Service [RTI Issue ID RECORD-1083].