Cloud Bigtable V2 Client - Class MemoryConfig (2.31.0)
Reference documentation and code samples for the Cloud Bigtable V2 Client class MemoryConfig.
If set, eligible single-row requests (currently limited to ReadRows)
using this app profile will be routed to the memory layer. All eligible
writes populate the memory layer. MemoryConfig can only be set if the
AppProfile uses single cluster routing and the configured cluster has a
memory layer enabled.
Generated from protobuf message google.bigtable.admin.v2.AppProfile.StandardIsolation.MemoryConfig
[[["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 2026-10-07 UTC."],[],[]]
