Update documentation to remove variables no longer in use

documentation/configuration-utils/_cairo.config.json

@@ -239,10 +239,6 @@
     "default": "64",
     "description": "Size of AnalyticColumn pool in SqlParser."
   },
-  "cairo.sql.create.table.model.pool.capacity": {
-    "default": "16",
-    "description": "Size of CreateTableModel pool in SqlParser."
-  },
   "cairo.sql.create.table.model.batch.size": {
     "default": "1000000",
     "description": "Batch size for non-atomic CREATE AS SELECT statements."
@@ -303,10 +299,6 @@
     "default": "8",
     "description": "Sets the max memory pages for storing bind variable values for JIT compiled filter."
   },
-  "cairo.sql.jit.rows.threshold": {
-    "default": "1M",
-    "description": "Sets minimum number of rows to shrink filtered rows memory after query execution."
-  },
   "cairo.sql.jit.page.address.cache.threshold": {
     "default": "1M",
     "description": "Sets minimum cache size to shrink page address cache after query execution."
@@ -315,10 +307,6 @@
     "default": "8K",
     "description": "Sets the memory page size for storing IR for JIT compilation."
   },
-  "cairo.sql.jit.ir.max.pages": {
-    "default": "8",
-    "description": "Sets max memory pages for storing IR for JIT compilation."
-  },
   "cairo.sql.page.frame.min.rows": {
     "default": "1000",
     "description": "Sets the minimum number of rows in page frames used in SQL queries."
@@ -463,4 +451,4 @@
     "default": "256k",
     "description": "mmap sliding page size that TableWriter uses to append data for each column specifically for System tables."
   }
-}
+}

documentation/configuration-utils/_http.config.json

@@ -78,10 +78,6 @@
     "description": "Size of internal buffer allocated for HTTP request headers. The value is rounded up to the nearest power of 2. When HTTP requests contain headers that exceed the buffer size server will disconnect the client with HTTP error in server log.",
     "reloadable": true
   },
-  "http.response.header.buffer.size": {
-    "default": "32K",
-    "description": "Size of the internal response buffer. The value will be rounded up to the nearest power of 2. The buffer size should be large enough to accommodate max size of server response headers."
-  },
   "http.worker.count": {
     "default": "0",
     "description": "Number of threads in private worker pool. When `0`, HTTP server will be using shared worker pool of the server. Values above `0` switch on private pool."

documentation/configuration-utils/_tcp.config.json

@@ -64,10 +64,6 @@
     "default": "32768",
     "description": "Maximum size of any measurement."
   },
-  "line.tcp.writer.queue.size": {
-    "default": "128",
-    "description": "Size of the queue between network I/O and writer jobs. Each queue entry represents a measurement."
-  },
   "line.tcp.writer.worker.count": {
     "default": "",
     "description": "Number of dedicated I/O worker threads assigned to write data to tables. When `0`, the writer jobs will use the shared pool."
@@ -116,4 +112,4 @@
     "default": "true",
     "description": "Enable or disable Access Control List (ACL) authentication for InfluxDB Line Protocol over TCP. Enterprise only."
   }
-}
+}

documentation/configuration-utils/_wal.config.json

@@ -19,10 +19,6 @@
     "default": "200000",
     "description": "Row count of how many rows are written to the same WAL segment before starting a new segment. Triggers in conjunction with `cairo.wal.segment.rollover.size` (whichever is first)."
   },
-  "cairo.wal.commit.squash.row.limit": {
-    "default": "500000",
-    "description": "Maximum row count that can be squashed together from multiple transactions before applying to the table. A very low value can delay data visibility."
-  },
   "cairo.wal.squash.uncommitted.rows.multiplier": {
     "default": "20.0",
     "description": "Multiplier to cairo.max.uncommitted.rows to calculate the limit of rows that can be kept invisible when writing to WAL table under heavy load, when multiple transactions are to be applied. It is used to reduce the number Out-Of-Order (O3) commits when O3 commits are unavoidable by squashing multiple commits together. Setting it very low can increase O3 commit frequency and decrease the throughput. Setting it too high may cause excessive memory usage and increase the latency."
@@ -35,4 +31,4 @@
     "default": "true",
     "description": "When disabled, SQL executed by the WAL apply job will always run single-threaded."
   }
-}
+}