Non-expiring transients

Question –

This puts transients into Redis. Someone may define a transient w/o an expiration. In non-Redis WordPress, this means it’ll live in the WordPress database until explicitly deleted, updated, or all transients are flushed.

With this Redis implementation, is there any guarantee that such transients won’t get deleted from time to time? I’m not super familiar with how Redis does memory management, so want to verify that behavior.

Assuming there is no such guarantee, if I wanted non-expiring transients to indeed never be deleted, I assume I could add ‘transients’ to WP_REDIS_IGNORED_GROUPS and get the default WP transient behavior, right?