Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3784

Chunk commit data using lower of byte-based and row-count limits

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 4.11.0
    • None
    • None

    Description

      We have a byte-based limit that determines how much data we send over at a time when a commit occurs (PHOENIX-541), but we should also have a row-count limit. We could check both the byte-based limit and the row-count limit and ensure the batch size meets both constraints. This would help prevent too many rows from being submitted to the server at one time and decrease the likelihood of conflicting rows amongst batches.

      Attachments

        1. PHOENIX-3784-final.patch
          16 kB
          Thomas D'Silva
        2. PHOENIX-3784.patch
          15 kB
          Thomas D'Silva

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. PHOENIX-3782 MutationStates with too many rows should transparently split requests instead of throwing exception

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              tdsilva Thomas D'Silva
              jamestaylor James R. Taylor
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: