apurtell opened a new pull request, #2451: URL: https://github.com/apache/phoenix/pull/2451
`CDCBaseIT.generateMutations` has a second-half "force a delete if there was none so far" branch that flips `isDelete=true` without checking whether the candidate row was ever upserted in this run, so when random batch participation has skipped a key in every prior batch the forced `DELETE` lands on a non-existent row and produces an HBase tombstone with no matching put. The data table view sees no change, and a later legitimate upsert for the same key surfaces as the next CDC change event on a `forView=true` CDC while the expected change list still has the tombstone marked as a delete, tripping `CDCBaseIT.verifyChangesViaSCN` with `ComparisonFailure expected:<delete> but was:<upsert> in CDCQueryIT.testSelectGeneric[forView=true, encodingScheme=TWO_BYTE_QUALIFIERS, multitenant=false, tableSaltBuckets=null, withSchemaName=false, caseSensitiveNames=false]`. The fix gates the forced-delete branch on `mutatedRows.contains(rows.get(j))` so a delete is only ever forced on a row that has already been upserted. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
