title: Changing the partition key of a live IMap in Hazelcast (partition migration)
body: <p>I'd like to change the way one of my maps is partitioned in Hazelcast. Can Hazelcast handle this safely for an existing distributed map if I start replacing nodes with new nodes using a different partitioning strategy?</p>
  
  <p>Say I have Customers in my map partitioned by CustomerId but I want to start partitioning them with a PartitionAwareKey which keeps the key as CustomerId but changes the PartitionKey to be the customer's ZIP code.</p>
  
  <p>It's easy to do with PartitionAwareKey but I see no docs on how this works for migrating an existing distributed map.</p>
  
  <p>It seems like this will simply add new items to the map as PartitionAwareKey  uses both key and partitionKey in its equals method.</p>
  
  <p>If I made my own ParitionAware without using the partitionKey as part of the equals/hashcode implementation would I be able to live replace the way the items are partitioned without causing inconsistency in the map access?</p>
  
  <p>Thanks!</p>