概览
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
以下是我们在处理商家评价 Feed 时可能会遇到的常见数据问题。
我们会提供每种数据问题的说明,以及您可以采取的解决每种问题的步骤。
当您的 Feed 中检测到数据问题时,商店评分汇总方支持团队会通知您该问题。
大多数数据问题都可以通过向端点提交新的 Feed 文件来解决。我们建议您不要将修复与新商家和评价的每日 Feed 合并,而是创建一个单独的文件,其中包含所有针对未解决问题的修复。另请注意包含修复的文件名。如果修复无法解决数据问题,您需要与支持团队联系以寻求帮助,这时就需要文件名。
以下是解决数据问题所涉及的典型步骤。
- 您每天向端点传送一个数据 Feed 文件:2017-11-10.xml。此文件包含无效的评分。
- 您向端点提交了第二个每日 Feed 文件,该文件没有数据问题:2017-11-11.xml。
- 支持团队通知您存在问题后,您提交了一个新的 Feed 文件 2017-11-11_fix.xml,其中包含之前提交的无效评价的有效评分。此有效记录已更新
last_update_timestamp
,表明相应评价具有有效评分,可解决数据问题。
在阅读本指南时,请注意以下几点:
- 系统会定期提取并下载您的 Feed 文件。如果在提取中检测到数据问题,系统将不会提供该提取或后续提取中的新数据,直到所有数据问题都得到解决。
- 如果您的 Feed 中存在未解决的数据问题,系统仍会继续提取和处理您的 Feed,以发现新的数据问题。
- 当所有数据问题都解决后,系统会提供从端点下载的所有数据。
- 每种数据问题都有其根本原因,无论是数据库中的无效数据,还是数据生成方式中的 bug。在针对未解决的数据问题提供修复 Feed 之前,请先确保问题根源已得到解决。解决根本原因可防止出现相同类型的新问题。修复根本原因后,您可以着手传送修复 Feed 文件。
- 修复文件(即以“_fix.xml”结尾的文件)不应包含并非旨在修复未解决的数据问题的记录。
- 如果您的修正措施无法自动解决数据问题,请回复通知您存在数据问题的电子邮件,与支持团队联系。
- 由于这些数据问题修复通常涉及在 Feed 中提供商家和评价实体,因此在阅读每个数据问题之前,请务必先查看 XML 架构文档。
- 为简单起见,以下文档假定您要修正的是特定类型的单个数据问题。实际上,可能会同时出现多个数据问题。在交付修复时,您可以将多个问题的修复合并到单个 Feed 文件中。
同样,在与支持团队联系时,请整合不同数据问题的沟通内容。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThis guide explains common data issues found in Merchant Review feeds and provides steps to resolve them.\u003c/p\u003e\n"],["\u003cp\u003eData issues halt the serving of new data until resolved, but feed fetching and processing for new issues continue.\u003c/p\u003e\n"],["\u003cp\u003eResolving the root cause of data issues is crucial to prevent recurrence before submitting fix files.\u003c/p\u003e\n"],["\u003cp\u003eFix files should only contain data intended to resolve existing issues and should have updated timestamps.\u003c/p\u003e\n"],["\u003cp\u003eContact support if fixes don't automatically resolve the issues or for assistance with multiple, simultaneous data issues.\u003c/p\u003e\n"]]],["Data issues in Merchant Review feeds are identified, and support notifies you. Deliver new feed files to resolve them, preferably separate from daily feeds, using filenames like `_fix.xml`. Ensure fixes only contain corrected data, update `last_update_timestamp`, and address the root cause to prevent recurrence. Unresolved issues halt new data service, while all data is served post-resolution. Contact support for persistent problems. You can consolidate multiple fixes in one file and consolidate your communication to support.\n"],null,["# Overview\n\nThe following are common data issues that can arise when we process your Merchant Review feeds.\nWe provide descriptions of each data issue and steps you can take to resolve each issue.\nWhen a data issue is detected in your feed, the store ratings aggregator support notifies you of\nthe issue.\n\nMost data issues can be resolved by delivering new feed files to your endpoint. We suggest that\ninstead of consolidating fixes with your daily feed of new merchants and reviews, you create a\nseparate file containing all fixes for outstanding issues. Also, take note of the filenames which\ncontain fixes. The filenames are needed in case a fix doesn't resolve a data issue and you need to\ncontact the support team for assistance.\n\nBelow are the typical steps involved in fixing a data issue.\n\n1. You deliver a daily feed file to your endpoint: 2017-11-10.xml. This file contains an [Invalid rating](/merchant-review-feeds/data-issues/invalid-rating).\n2. You deliver a second daily feed file to your endpoint, which has no data issues: 2017-11-11.xml.\n3. After the support team notifies you of an issue, you deliver a new feed file, 2017-11-11_fix.xml, which contains a valid rating for the previously delivered invalid review. This valid record has an updated `last_update_timestamp` to indicate that this review has a valid rating to resolve the data issue.\n\nAs you read this guide, keep the following points in mind:\n\n- Your feed files are downloaded in periodic fetches. If a data issue is detected in a fetch, new data from that fetch or subsequent fetches won't be served until all data issues have been resolved.\n- While there are outstanding data issues in your feed, your feeds will continue to be fetched and processed for new data issues.\n- When all data issues are resolved, all data that has been downloaded from your endpoint will be served.\n- There's a root cause for every data issue, whether it's invalid data in your database or a bug in the way the data was generated. Before providing a fix feed for outstanding data issues, first ensure the root cause of the issue is resolved. Resolving the root cause prevents new issues of the same type from occurring. After fixing the root cause, you can work on delivering fix feed files.\n- Fix files (i.e. files that end in \"_fix.xml\") should not include records that are not intended to fix outstanding data issues.\n- If your fixes don't automatically resolve data issues, contact the support team by replying to the communication that notified you of the data issue.\n- As these fixes for data issues often involve delivering merchant and review entities in your feeds, it helps to review the [XML schema](/merchant-review-feeds/xmlschema) documentation before reading each data issue.\n- For the sake of simplicity, the documentation below assumes you're fixing a single data issue of a particular type. In practice, multiple data issues can occur at the same time. When delivering fixes, you may consolidate fixes for multiple issues into a single feed file. Similarly, when contacting the support team, consolidate communications across different data issues."]]