Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-13579

Future: Use control points from python

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Test Python
    • None
    • Storage Engines
    • 5

      This includes several APIs and defining a control point in a python test program. They are grouped in difficulty below.

      • Easy APIs
        • Enable per connection: __wt_conn_control_point_enable
        • Enable per session: __wt_session_control_point_enable
        • Disable per connection: __wt_conn_control_point_disable
        • Disable per session: __wt_session_control_point_disable
        • Reconfigure a control point changing the action configuration parameters and/or the predicate configuration parameters but not changing the predicate.
      • Harder API
        • Reconfigure a control point changing the predicate in addition to the configuration parameters as above.
      • Hardest API
        • Define a new control point in the python test program.

      When the work in this ticket is done this ticket should be split into separate tickets for each of the items above.

      Note, the control points implementation tickets are in three time periods:

      1. POC - Part of the POC.
      2. MVP - Part of the minimal viable product. However, even the POC can be used but less conveniently than the MVP.
      3. Future - Enhancements after the MVP.

      The title of each ticket starts with the time period.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            tod.johnson@mongodb.com Tod Johnson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: