Spider Status Variables
You are viewing an old version of this article. View
the current version here.
Contents
The following status variables are associated with the Spider storage engine. See Server Status Variables for a complete list of status variables that can be viewed with SHOW STATUS.
See also the Full list of MariaDB options, system and status variables.
Spider_direct_aggregate
- Description:
- Scope: Global, Session
- Data Type:
numeric
Spider_direct_delete
- Description:
- Scope: Global, Session
- Data Type:
numeric
- Introduced: MariaDB 10.3.3
Spider_direct_order_limit
- Description:
- Scope: Global, Session
- Data Type:
numeric
Spider_direct_update
- Description:
- Scope: Global, Session
- Data Type:
numeric
- Introduced: MariaDB 10.3.3
Spider_mon_table_cache_version
- Description: The version of the spider monitoring table cache, always less than or equal to
Spider_mon_table_cache_version_req
. If the inequality is strict, then the cache is refreshed when the spider udfspider_ping_table
is called. When the cache is refreshed, the value ofSpider_mon_table_cache_version
is brought up to be the same value asSpider_mon_table_cache_version_req
. - Scope: Global, Session
- Data Type:
numeric
Spider_mon_table_cache_version_req
- Description: The required version of the spider monitoring table cache. A call to the spider udf
spider_flush_table_mon_cache
will cause its value to be incremented by one, thus ensuring a refresh of the cache will happen when needed. - Scope: Global, Session
- Data Type:
numeric
Spider_parallel_search
- Description:
- Scope: Global, Session
- Data Type:
numeric
- Introduced: MariaDB 10.3.3
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.