fix: delete data from associated pre-aggr table

[zhanghaohit]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Fix #1673

#2307 has to be fixed before this PR work correctly.

[codecov[bot]]

Codecov Report

Merging #2300 (1930963) into main (180f0e0) will decrease coverage by 0.01%. The diff coverage is 96.46%.

@@             Coverage Diff              @@
##               main    #2300      +/-   ##
============================================
- Coverage     75.71%   75.70%   -0.02%     
  Complexity      368      368              
============================================
  Files           627      627              
  Lines        118168   118431     +263     
  Branches       1050     1022      -28     
============================================
+ Hits          89470    89657     +187     
- Misses        28482    28558      +76     
  Partials        216      216              

Impacted Files	Coverage Δ
src/storage/aggregator.h	100.00% <ø> (ø)
src/tablet/tablet_impl.cc	61.48% <58.33%> (-0.20%)	:arrow_down:
src/storage/aggregator.cc	75.92% <89.65%> (+0.70%)	:arrow_up:
src/tablet/tablet_impl_test.cc	99.53% <100.00%> (+0.01%)	:arrow_up:
...4paradigm/openmldb/batch/utils/UnsafeRowUtil.scala	44.73% <0.00%> (-39.48%)	:arrow_down:
...s/query_response_time/deploy_query_response_time.h	81.25% <0.00%> (-18.75%)	:arrow_down:
.../com/_4paradigm/openmldb/batch/SparkRowCodec.scala	57.47% <0.00%> (-9.98%)	:arrow_down:
...aradigm/openmldb/batch/window/WindowComputer.scala	75.92% <0.00%> (-5.81%)	:arrow_down:
...atistics/query_response_time/query_response_time.h	78.26% <0.00%> (-4.35%)	:arrow_down:
.../query_response_time/deploy_query_response_time.cc	97.10% <0.00%> (-2.90%)	:arrow_down:
... and 21 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[github-actions[bot]]

SDK Test Report

  79 files    79 suites   7m 12s :stopwatch: 167 tests 165 :heavy_check_mark: 2 :zzz: 0 :x: 209 runs  207 :heavy_check_mark: 2 :zzz: 0 :x:

Results for commit 19309632.

:recycle: This comment has been updated with latest results.

[github-actions[bot]]

Linux Test Report

       55 files       200 suites   51m 52s :stopwatch:   9 255 tests   9 251 :heavy_check_mark: 4 :zzz: 0 :x: 13 616 runs  13 612 :heavy_check_mark: 4 :zzz: 0 :x:

Results for commit 19309632.

:recycle: This comment has been updated with latest results.

[nautaa]

https://github.com/4paradigm/OpenMLDB/blob/309dc04cdc16f5529ea09122c4e0d2849d1df90a/src/storage/aggregator.cc#L359-L363

There seems to be nothing to do, you can remove the warning log.

[zhanghaohit]

https://github.com/4paradigm/OpenMLDB/blob/309dc04cdc16f5529ea09122c4e0d2849d1df90a/src/storage/aggregator.cc#L359-L363

There seems to be nothing to do, you can remove the warning log.

here if we found a kDelete entry, we shall do Delete(key) again, right? in case during the recover, we recover the key in the aggr_buffer_map_

[nautaa]

https://github.com/4paradigm/OpenMLDB/blob/309dc04cdc16f5529ea09122c4e0d2849d1df90a/src/storage/aggregator.cc#L359-L363

There seems to be nothing to do, you can remove the warning log.

here if we found a kDelete entry, we shall do Delete(key) again, right? in case during the recover, we recover the key in the aggr_buffer_map_

yep, you are right. aggregator maybe update in recovery phase.

[zhanghaohit]

merged after 060 release