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

Generate correct index updates when DeleteColumn processed before Put with same timestamp

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • None
    • None
    • None
    • None

    Description

      The following scenario is not handled correctly for mutable secondary indexing:
      1) indexed column set to null at ts1 (generates a DeleteColumn)
      2) indexed column set to value at ts1 (i.e. different client, same ts)
      3) RS processes (1) first
      4) RS processes (2) next

      Because deletes take precedence over puts even though the put happens after the delete, we still needs to not generate index updates.

      The quick fix is to add STORE_NULLS=true to the table as we skirt the issue since no deletes are issued (i.e. last put wins).

      Attachments

        Activity

          People

            Unassigned Unassigned
            jamestaylor James R. Taylor
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: