Setting import thread count to more than one breaks variables import

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.1.0-alpha1, 2.1.0
    • Affects Version/s: None
    • Component/s: backend
    • None

      AT:

      • given:
        • the elasticsearch job executor thread count is > 1 in Optimize
        • Engine is up running and contains data with variables
      • when:
        • Optimize imports the engine data
      • then:
        • the variables are not imported
      • expected:
        • all data is imported independent from the thread count setting

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: