When using transactional map, there is no put with ttl method overload:
boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl);
But there is such method in imap interface class. In java client both maps (ordinary and transactional) use a common interface for map and put methods are equal.
Expected behavior
Method boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl); is available in hazelcast::client::transactional_map.
Actual behavior
Method boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl); is not available in hazelcast::client::transactional_map.
When using transactional map, there is no put with ttl method overload:
boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl);But there is such method in
imapinterface class. In java client both maps (ordinary and transactional) use a common interface for map and put methods are equal.Expected behavior
Method
boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl);is available inhazelcast::client::transactional_map.Actual behavior
Method
boost::future< boost::optional< R > > put (const K &key, const V &value, std::chrono::milliseconds ttl);is not available inhazelcast::client::transactional_map.