Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-28528 Fix Idempotence for Once batches in Catalyst optimizer
  3. SPARK-28237

Idempotence checker for Idempotent batches in RuleExecutors

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 3.0.0
    • 3.0.0
    • SQL
    • None

    Description

      The current RuleExecutor system contains two kinds of strategies: Once and FixedPoint. The Once strategy is supposed to run once. However, for particular rules (e.g. PullOutNondeterministic), they are designed to be idempotent, but Spark currently lacks corresponding mechanism to prevent such kind of non-idempotent behavior from happening.

      Attachments

        Issue Links

          Activity

            People

              manifoldQAQ Yesheng Ma
              manifoldQAQ Yesheng Ma
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: