Profile filters use different FCV depending on how the filter is set

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.0.0, 8.2.0-rc0
    • Component/s: None
    • Query Integration
    • ALL
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      There are three ways to set a filter on the profiler:

      1. profile command
      2. setProfilingFilterGlobally command
      3. operationProfiling.filter server option on startup

      Options 1 and 2 are set at runtime by a customer at any time. Option 3 is set at startup and we currently parse the expression before FCV is initialized here. That means, options 1 and 2 permits users to create filters with all new query features enabled on the latest FCV. However, option 3 only allows users to create filters with query features enabled on lastLTS.

            Assignee:
            Unassigned
            Reporter:
            Gil Alon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: