Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
3.0.1
-
None
-
None
-
1
Description
There is no way to set the tracing threshold time for queries or search from the connection string. If you call cntl programmatically, it works fine. The issue is super simple to fix:
from src/cntl.cc:
976 {"tracing_threshold_queue_size", LCB_CNTL_TRACING_THRESHOLD_QUEUE_SIZE, convert_u32}, |
977 {"tracing_threshold_kv", LCB_CNTL_TRACING_THRESHOLD_KV, convert_timevalue}, |
978 {"tracing_threshold_search", LCB_CNTL_TRACING_THRESHOLD_QUERY, convert_timevalue}, |
979 {"tracing_threshold_view", LCB_CNTL_TRACING_THRESHOLD_VIEW, convert_timevalue}, |
980 {"tracing_threshold_search", LCB_CNTL_TRACING_THRESHOLD_SEARCH, convert_timevalue}, |
981 {"tracing_threshold_analytics", LCB_CNTL_TRACING_THRESHOLD_ANALYTICS, convert_timevalue}, |
|
So – we have 2 tracing_threshold_search, and no tracing_threshold_query. And of course the search actually sets the query (the second one is never hit), so neither really works from the connection string.
I'll make a simple patch for this. Python tests will skip this one until this goes in - ideally in 3.0.2.