Re: How does Ignite treat equal Keys?

[rjdamore]

Very good, you are correct about concurrentHashMap of course. I didn't 
frame that statement correctly. 5 stars for the quick response, you folks are 
doing great stuff! On Nov 21, 2016 4:07 PM, "vkulichenko [via Apache 
Ignite Users]" <ml-node+s70518n9119...@n6.nabble.com> wrote: 

        Hi,
If you insert twice for the same key, you have the latest inserted value in 
cache. So yes, the value will be overwritten and that's actually similar to 
the ConcurrentHashMap, but Ignite cache is distributed.
-Val

        
        
        
        
        
        
        
                If you reply to this email, your message will be added to the 
discussion below: 
                
http://apache-ignite-users.70518.x6.nabble.com/How-does-Ignite-treat-equal-Keys-tp9118p9119.html
 
        
        
                
                To unsubscribe from How does Ignite treat equal Keys?, click 
here . 
                NAML 
        



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/How-does-Ignite-treat-equal-Keys-tp9118p9120.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.