You've already forked mariadb-columnstore-engine
mirror of
https://github.com/mariadb-corporation/mariadb-columnstore-engine.git
synced 2025-07-30 19:23:07 +03:00
MCOL-5021 Add an option in Columnstore.xml, fastdelete (disabled
by default), which when enabled, indiscriminately invalidates all column extents and performs the actual DELETE only on the AUX column. The trade-off with this approach would now be that the first SELECT for certain query patterns (those containing a WHERE predicate) after the DELETE operation will slow down as the invalidated column extent would need to be scanned again to set the min/max values.
This commit is contained in:
@ -122,6 +122,14 @@ class Config
|
||||
*/
|
||||
EXPORT static std::string getBulkRollbackDir();
|
||||
|
||||
/**
|
||||
* @brief MCOL-5021 Option to enable/disable fast deletes.
|
||||
* When enabled (option is disabled by default),
|
||||
* all column extents are indiscriminately invalidated
|
||||
* and actual delete is only performed on the AUX column.
|
||||
*/
|
||||
EXPORT static bool getFastDelete();
|
||||
|
||||
/**
|
||||
* @brief Max percentage of allowable file system disk usage for each DBRoot
|
||||
*/
|
||||
@ -187,6 +195,7 @@ class Config
|
||||
static unsigned m_ExtentsPerSegmentFile; // # extents per segment file
|
||||
static int m_BulkProcessPriority; // cpimport.bin proc priority
|
||||
static std::string m_BulkRollbackDir; // bulk rollback meta data dir
|
||||
static bool m_FastDelete; // fast delete option
|
||||
static unsigned m_MaxFileSystemDiskUsage; // max file system % disk usage
|
||||
static unsigned m_NumCompressedPadBlks; // num blks to pad comp chunks
|
||||
static bool m_ParentOAMModuleFlag; // are we running on parent PM
|
||||
|
Reference in New Issue
Block a user