Support for latching about rosbag2 HOT 3 CLOSED

This is related to #125 in a way that there is currently no direct way to obtain the QoS parameters solely given a topic name. The subscriber has to know the correct QoS settings a priori.

One workaround, same as for unreliable connections is to introduce keywords within the command line tool to manually specify which topics are reliable, unreliable or latched.
Something like:

ros2 bag record <reliable_topic1> <reliable_topic2> --unreliable <unreliable_topic1> <unreliable_topic2> --latched <latched_topic1> <latched_topic2>

Does this sound feasible to you?

from rosbag2.

Thanks
That is probably a good workaround, since there seems to be no other solution until ros2/rmw#151 is resolved. But it would still be important to have this feature in the end.

from rosbag2.

This functionality will be handled by #125, closing as duplicate

from rosbag2.