Common QFS configuration elements Version of the configuration file Defines whether to log commands through QF API logging facility. 'logs' folder must exist on the same level as 'bin' folder. Log file 'qfs_commands.xml' will be created. It can later be replayed using QFS Test Tool. Also, a command file for every provider that was involved in the planning or execution of a QF Command will be saved in the logs folder. Levesl 0, 1, 2 are the appropriate logging levels. Only supported on CSTD_PLATFORM_WIN32. Instructs QF to not execute commands but to log the command only and then fail the command. Number of milliseconds the cleanup thread that does cleanup of unused connections should sleep between passes. Max number of open connections allowed (“–1” means “no limit”). Connections to providers can be limited using this parameter; when the threshold is reached request to open a new connection will block for period of time configured through 'requestExpirationThreshold'. Number of milliseconds that must pass before connection can be considered “expired”. Once the internal connection to the data source is no longer used it remains available for this period of time and then deleted. Number of times that a connection can be reused, excluding "metadata" commands. Once the threshold is met, the connection is cleaned up. Number of times that a connection can be reused for "metadata" commands only. Once the threshold is met, the connection is cleaned up. Number of milliseconds between cleaning the connection pool. After this period of time passes the cleanup thread will identify and remove unused connections. Number of milliseconds for which the high-level resource pool is available for reuse after having been released. Number of milliseconds after which QFS gives up when trying to open a new connection (e.g. when connection pool is limited in size and QFS waits for a new connection "slot" to become available). Max number of elements in the metadata query pool (“–1” means “no limit”). This is the maximum allowed number of metadata queries per connection. Number of milliseconds that must pass before metadata query object can be considered “expired” (and can be deleted). Number of milliseconds between cleaning the metadata query pools. Max number of tuples that is allowed on a single edge (“–1” means “no limit”). This limit allows providers to refuse to execute certain queries that will otherwise result in memory over-consumption. Max number of data cells that are allowed in a single query (“–1” means “no limit”). This limit allows providers to refuse to execute certain queries that will otherwise result in memory over-consumption. Provider to accept the query sent to the query framework service. Provider to accept the FM command sent to the query framework service. Planner-specific number of milliseconds that must pass before connection can be considered “expired”. Once the internal connection to the data source is no longer used it remains available for this period of time and then deleted. Number of times that a connection can be reused, excluding "metadata" commands. Once the threshold is met, the connection is cleaned up. Number of times that a connection can be reused for "metadata" commands only. Once the threshold is met, the connection is cleaned up. Provider-specific max number of elements in the metadata query pool (“–1” means “no limit”). This is the maximum allowed number of metadata queries per connection. Provider-specific number of milliseconds that must pass before metadata query object can be considered “expired” (and can be deleted). Provider-specific number of milliseconds between cleaning the metadata query pools. Provider-specific max number of tuples that is allowed on a single edge (“–1” means “no limit”). This limit allows providers to refuse to execute certain queries that will otherwise result in memory over-consumption. Max number of data cells that are allowed in a single query (“–1” means “no limit”). This limit allows providers to refuse to execute certain queries that will otherwise result in memory over-consumption. Information specific for this provider. An arbitrary provider specific informaion. Symbolic name of the provider that will be passed inside "dataSourceType" QS API connection property Physical name of the provider shared library (appropriate suffix will be added on each platform) Indicates if this is a service provider Specifies element name Specifies attribute name Specifies attribute value Coordination Planner elements