QA Checklist
Stay organized with collections
Save and categorize content based on your preferences.
Before implementing the Version 5 (V5) schema, please ensure that the following are true of your V5 feeds:
- Merchant
last_update_timestamp
changes when anymerchant
field is updated
- Merchant IDs are unique across all V5 incrementals, that is, a merchant ID should refer to only one merchant
- Multiple merchant entries referring to a single merchant ID will be considered updates to a single merchant
- Review
last_update_timestamp
changes when anyreview field is updated
- Review IDs are unique across all V5 incrementals, that is, a review ID should refer to only one review
- Multiple review entries for a single review ID will be considered updates to a single review
- A review ID should be attached to only a single merchant ID
- Creation timestamps do not change
- Update times (that is,
last_update_timestamp
) must be the same as or after create times (that is, create_timestamp
)
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2023-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-08-11 UTC."],[[["\u003cp\u003eV5 feeds require unique Merchant and Review IDs with updates reflected in their respective \u003ccode\u003elast_update_timestamp\u003c/code\u003e values.\u003c/p\u003e\n"],["\u003cp\u003eWhen any merchant or review field is updated, the corresponding \u003ccode\u003elast_update_timestamp\u003c/code\u003e must also be updated.\u003c/p\u003e\n"],["\u003cp\u003eCreation timestamps should remain unchanged, and update timestamps should always be equal to or later than creation timestamps.\u003c/p\u003e\n"],["\u003cp\u003eA single merchant ID should represent only one merchant, and a review ID should be associated with only one merchant and represent a single review.\u003c/p\u003e\n"]]],["V5 feeds require specific conditions: Merchant `last_update_timestamp` must change with any merchant field update, and merchant IDs must be unique, with multiple entries considered updates. Similarly, review `last_update_timestamp` must reflect any review field update, and review IDs must be unique and tied to a single merchant ID. Creation timestamps must remain constant, and update times must be at or after creation times.\n"],null,["# QA Checklist\n\nBefore implementing the Version 5 (V5) schema, please ensure that the following are true of your V5 feeds:\n\n- Merchant `last_update_timestamp` changes when **any**merchant field is updated\n- Merchant IDs are unique across all V5 incrementals, that is, a merchant ID should refer to only one merchant\n - Multiple merchant entries referring to a single merchant ID will be considered updates to a single merchant\n- Review `last_update_timestamp` changes when **any**review field is updated\n- Review IDs are unique across all V5 incrementals, that is, a review ID should refer to only one review\n - Multiple review entries for a single review ID will be considered updates to a single review\n - A review ID should be attached to only a single merchant ID\n- Creation timestamps do not change\n- Update times (that is, `last_update_timestamp`) must be the same as or after create times (that is, `create_timestamp`)"]]
