SizeConstraints
The constraints on the sizes of the hash lists.
| JSON representation |
{
"maxUpdateEntries": integer,
"maxDatabaseEntries": integer
} |
| Fields |
maxUpdateEntries |
integer
The maximum size in number of entries. The update will not contain more entries than this value, but it is possible that the update will contain fewer entries than this value. This MUST be at least 1024. If omitted or zero, no update size limit is set.
|
maxDatabaseEntries |
integer
Sets the maximum number of entries that the client is willing to have in the local database for the list. (The server MAY cause the client to store less than this number of entries.) If omitted or zero, no database size limit is set.
|
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 2024-09-18 UTC.
[null,null,["Last updated 2024-09-18 UTC."],[[["The JSON schema defines constraints for hash list sizes, using `maxUpdateEntries` and `maxDatabaseEntries`."],["`maxUpdateEntries` limits the number of entries in an update, with a minimum value of 1024 and no limit if omitted or zero."],["`maxDatabaseEntries` limits the total entries allowed in the client's local database, with no limit if omitted or zero."]]],["The content defines the structure for specifying constraints on hash list sizes using a JSON object with two integer fields: `maxUpdateEntries` and `maxDatabaseEntries`. `maxUpdateEntries` sets the maximum number of entries in an update, with a minimum of 1024. `maxDatabaseEntries` limits the number of entries a client is willing to store locally. Omitting either field or setting it to zero indicates no size limit for that aspect.\n"]]
