In-Memory Tables

In-memory tables are not persisted by default like a regular table. You can add, modify, or delete records in an in-memory table.

The default nature of the listed endpoints below is to create an in-memory table (unless persistence is specified):

• Aggregate Groupby in-memory table -- created from /aggregate/groupby with the result_table option specified
• Aggregate Unique in-memory table -- created from /aggregate/unique with the result_table option specified
• Aggregate Unpivot in-memory table -- created from /aggregate/unpivot with the result_table option specified
• Projection -- created from /create/projection
• Union (also includes intersect and except operations) -- created from /create/union
• Creating a table using /create/table with the is_result_table option set to true

Limitations and Cautions

• Primary Key fields contained within in-memory tables cannot be updated
• Object ID cannot be used to update or delete records -- this means updating or deleting records in an in-memory table is not possible through the GAdmin Data UI
• Individual in-memory table types have additional limitations and properties that may differ from the preceding limitations. More information can be found in Aggregate Groupby In-Memory Tables, Aggregate Unique In-Memory Tables, Aggregate Unpivot In-Memory Tables, Except, Intersect, Projections, and Union respectively

Memory Implications

All in-memory table types listed above copy data from their source data sets, thus their memory footprint can be quite large compared to a join view or a filtered view. However, because the data is copied, there's no reliance on lookups between connected join data sets or scanning mask on filtered data sets, resulting in faster queries.