Proto3的Map是否与Proto2的重复KeyValuePair向后兼容？能否替换？

Great question—this is a common point of confusion when migrating between Protobuf versions, so let's break it down step by step.

1. Are Proto3 maps backward compatible with Proto2 repeated KeyValuePair? #

Yes, they are binary compatible—but with an important caveat. Under the hood, Proto3 maps serialize to the exact same wire format as a repeated KeyValuePair message like your Proto2 example. That means:

• A Proto2 parser can read data serialized from a Proto3 map without any issues.
• A Proto3 parser can read data serialized from a Proto2 repeated KeyValuePair... unless there are duplicate keys.

The critical behavioral difference lies in how duplicate keys are handled:

• In Proto2, a repeated KeyValuePair allows multiple entries with the same key. When parsed, all entries are retained in the order they were serialized.
• In Proto3, maps automatically deduplicate keys—if multiple entries share the same key, only the last one is kept.

So if your data never includes duplicate keys, full backward compatibility holds. If duplicates are possible, the parsing results will diverge between the two definitions.

2. Can we replace the Proto2 repeated KeyValuePair with a Proto3 map? #

It depends entirely on your use case:

✅ Safe to replace if: #

Your original Proto2 usage never includes duplicate keys. The Proto3 map is a cleaner, more concise syntax that behaves identically (in terms of data representation) to a non-duplicate repeated KeyValuePair. For example:

• Proto3 definition:

  message Foo {
    map<string, string> foo = 1;
  }
  

• Is functionally equivalent (for non-duplicate keys) to your Proto2 definition:

  message Foo {
    repeated KeyValuePair foo = 1;
  }
  message KeyValuePair {
    string key = 1;
    string value = 2;
  }
  

Using the map also gives you nicer language-specific APIs (like native dictionary/map types in most languages) instead of having to work with a list of key-value objects.

❌ Not safe to replace if: #

Your application relies on supporting duplicate keys in the foo field. Since Proto3 maps discard duplicate keys, replacing the repeated field with a map would lose data in cases where multiple entries share the same key. In this scenario, you'll need to stick with a repeated message type (even in Proto3) to preserve all entries.

内容的提问来源于stack exchange，提问作者Aly