更新版本冲突
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
说明
当 review 或 merchant 具有多个更新（具有相同 review 或 merchant ID 的条目），但内容不同，last_update_timestamp 却相同时，就会发生冲突的更新。由于这些条目具有相同的 last_update_timestamp，我们无法确定哪个更新是最新更新。
解决方法
传送包含最新内容且 last_update_timestamp 已更新的 review 或 merchant。
时间戳创建冲突
如果两个更新因 create_timestamp 的值不同而发生冲突，则应再次传送 review 或 merchant，并使创建时间与最初发送的创建时间相匹配。如果创建时间与原始创建时间不一致，则会发生其他数据问题。
如果两个更新因 create_timestamp 的值不同而发生冲突，并且您认为新的 create_timestamp 是正确的值，请按照以下步骤为 review 或 merchant 设置新的创建时间，而不会生成新的数据问题：
- 再次交付
review 或 merchant，并附上预期的 create_timestamp 和更新后的 last_update_timestamp。
- 告知支持团队您打算使用新的创建时间，并提供包含具有新创建时间的条目的文件名。支持团队会确保使用新的创建时间，并且不会生成新的数据问题。
如果因 XML 文件形成方式的更改（例如格式更改）而导致冲突，但基础数据并未更改，那么更改更新时间就没有意义。在这种情况下，请按以下步骤操作。
- 告知支持团队更新
last_update_timestamp 不合理的原因。
- 生成包含最新内容的文件（在本例中，无需更新
last_update_timestamp）
- 向支持团队提供最新内容的相应文件名。支持团队会确保使用最新内容。
示例
3 月 1 日，您将 Feed 文件“2017_03_01.xml”上传到端点。该文件包含以下内容：
<review id="156368" mid="2739">
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-25T03:02:23Z</create_timestamp>
<last_update_timestamp>2017-02-25T03:02:23Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10">9</overall>
<customer_service min="1" max="10">10</customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
3 月 5 日，您将 Feed 文件“2017_03_05.xml”上传到端点。该文件包含用户对评价标题的修改，但 last_update_timestamp 与之前针对此评价发送的条目相比未发生变化：
<review id="156368" mid="2739">
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-25T03:02:23Z</create_timestamp>
<last_update_timestamp>2017-02-25T03:02:23Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices and customer service!</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10"<9>/overall>
<customer_service min="1" max="10"<10>/customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
收到支持团队发来的通知，告知您发生了冲突的更新数据问题后，您将“2017_03_10-fix.xml”上传到端点，以解决该问题。
<review id="156368" mid="2739">
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-25T03:02:23Z</create_timestamp>
<last_update_timestamp>2017-03-04T02:01:20Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices and customer service!</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10">9</overall>
<customer_service min="1" max="10">10</customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-26。
[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eConflicting updates happen when a review or merchant has multiple updates with the same ID, different content, but identical \u003ccode\u003elast_update_timestamp\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo fix a conflicting update, deliver the review or merchant with the most recent content and an updated \u003ccode\u003elast_update_timestamp\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eIf the conflict is due to differing \u003ccode\u003ecreate_timestamp\u003c/code\u003e values, the review or merchant should be delivered with the original \u003ccode\u003ecreate_timestamp\u003c/code\u003e or the support team should be informed of the new intended \u003ccode\u003ecreate_timestamp\u003c/code\u003e to avoid further data issues.\u003c/p\u003e\n"],["\u003cp\u003eFor XML formatting changes that don't affect underlying data, inform the support team and provide a file with the updated content without changing the \u003ccode\u003elast_update_timestamp\u003c/code\u003e.\u003c/p\u003e\n"]]],["Conflicting updates arise when multiple entries for the same review or merchant have different content but identical `last_update_timestamp`. To resolve this, deliver the most recent content with an updated `last_update_timestamp`. If conflicts are due to differing `create_timestamp` values, resubmit with the original creation time. If a new create time is needed, deliver the review with the updated create and update timestamps and inform the support team. For XML formatting conflicts, notify the support team, provide the updated file, and the timestamp does not need to change.\n"],null,["# Conflicting update\n\nDescription\n-----------\n\nA conflicting update occurs when a [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) has multiple\nupdates (entries with the same [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) ID) with\ndiffering contents, but identical `last_update_timestamp`. Because these entries have the same\n`last_update_timestamp`, we're unable to identify which update is more recent.\n\nHow to fix\n----------\n\nDeliver the [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e) or\n[`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) with the most\nrecent content and with an updated `last_update_timestamp`.\n\n### Timestamp creation conflicts\n\nFor cases where two updates conflict due to different values for `create_timestamp`,\nthe [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e) or\n[`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) should be delivered\nagain with a create time matching the create time that was originally sent. If the create time does\nnot match the original create time, an additional data issue will occur.\n\nWhen two updates conflict as a result of different values for `create_timestamp`, and\nyou believe the new `create_timestamp` is the correct one, follow the below steps for\nsetting a new create time for the [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) without\ngenerating a new data issue:\n\n1. Deliver the [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e) or [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) again with the intended `create_timestamp` and updated last_update_timestamp.\n2. Inform the support team that you intend to use the new create time and provide the filename containing the entry with the new create time. The support team ensures the new create time is used and a new data issue isn't generated.\n\n### XML formatting change conflicts\n\nWhen there is a conflict as a result of a change to the way the XML files are formed\n(e.g., changes to formatting), but the underlying data isn't changing, it doesn't make sense to\nchange the update time. Under those circumstances, follow the steps below.\n\n1. Inform the support team the reason why updating `last_update_timestamp` is unreasonable.\n2. Generate a file with the most updated content (in this case, it isn't necessary to update `last_update_timestamp`)\n3. Provide the filename to the most updated content to the support team. The support team ensures the most updated content is used.\n\nExample\n-------\n\nOn March 1st, you upload the feed file \"2017_03_01.xml\" to your endpoint. The file contains the\nfollowing contents: \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\"\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-02-25T03:02:23Z\u003c/last_update_timestamp\u003e\n \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\"\u003e9\u003c/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003e10\u003c/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```\n\nOn March 5th, you upload the feed file \"2017_03_05.xml\" to your endpoint. The file contains a\nuser edit to the title of a review, however, the `last_update_timestamp` has not\nchanged from the previous entry sent for this review: \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\"\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-02-25T03:02:23Z\u003c/last_update_timestamp\u003e\n \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices and customer service!\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\"\u003c9\u003e/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003c10\u003e/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```\n\nUpon receiving a notification from the support team that a conflicting update data issue has\noccurred, you upload \"2017_03_10-fix.xml\" to your endpoint, to resolve the issue. \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\"\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-03-04T02:01:20Z\u003c/last_update_timestamp\u003e\n \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices and customer service!\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\"\u003e9\u003c/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003e10\u003c/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```"]]
