You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8d6db43
Browse filesBrowse the repository at this point in the historyBrowse files
fix(kernel): forward telemetry_flush_interval_ms to the kernel (#1026)
* fix(kernel): forward telemetry_flush_interval_ms to the kernel
The kernel binding accepts telemetry_flush_interval_ms, but the connector
never forwarded it, so kernel connections always used the kernel's 5s
default timer even when the caller asked for a longer interval.
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
* fix(kernel): reject invalid telemetry_flush_interval_ms in connect()
PyO3 accepts True as 1ms and reports negative or non-int values with a
conversion error that does not name the option.
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
---------
Signed-off-by: Vu Anh Phung <vu.phung@databricks.com>
Co-authored-by: Isaac <no-reply@databricks.com>
|`enable_telemetry`|`bool`| ✅ | ✅ |`True` (Thrift); kernel-defined when unset | Thrift is also gated by the server flag. An explicit Kernel value is forwarded without that Python-side gate. |
187
188
|`force_enable_telemetry`|`bool`| ✅ | ❌ |`False`| Bypass the server-side feature flag on Thrift. Not forwarded to Kernel. |
188
189
|`telemetry_batch_size`|`int`| ✅ | ✅ |`100`| Events buffered before a flush. |
190
+
|`telemetry_flush_interval_ms`|`int` (ms) | ❌ | ✅ | kernel-defined when unset | Kernel-only periodic flush interval; must be a positive `int`, else `connect()` raises `ValueError`. Thrift always flushes every 300s. |
189
191
|`_telemetry_circuit_breaker_enabled`|`bool`| ✅ | ✅ | effective `False` (Thrift); kernel-defined when unset | The `ClientContext` signature defaults to `True`, but `connect()` passes `None` when this option is omitted and `bool(None)` makes the effective Thrift default `False`. An explicit value is forwarded to Kernel. |
190
192
191
193
> **Telemetry _events_ differ by backend.** Because the kernel owns result
0 commit comments