Support attribute filters in table deletion

[jt2594838]

Summary

• Support table deletion with attribute filters by converting matched devices into deletion predicates
• Support IS NOT NULL for attribute filters and tag filters
• Add a SegmentNotNull TagPredicate for tag IS NOT NULL without device schema fetch
• Add integration tests for attribute/tag/time condition combinations and operator coverage

Tests

• mvn spotless:apply -pl iotdb-core/datanode,integration-test -P with-integration-tests
• mvn verify -DskipUTs "-Dit.test=IoTDBDeletionTableIT#testDeleteDataByTagIsNotNullFilter" "-DfailIfNoTests=false" "-Dfailsafe.failIfNoSpecifiedTests=false" "-Drat.skip=true" -pl integration-test -am -PTableSimpleIT -P with-integration-tests
• mvn verify -DskipUTs "-Dit.test=IoTDBDeletionTableIT#testDeleteDataByAttributeFilterWithOtherOperators" "-DfailIfNoTests=false" "-Dfailsafe.failIfNoSpecifiedTests=false" "-Drat.skip=true" -pl integration-test -am -PTableSimpleIT -P with-integration-tests

[codecov]

Codecov Report

❌ Patch coverage is 42.91045% with 153 lines in your changes missing coverage. Please review.
✅ Project coverage is 41.59%. Comparing base (cd5c3a3) to head (cf04c05).
⚠️ Report is 24 commits behind head on master.

Files with missing lines	Patch %	Lines
...otdb/db/queryengine/plan/analyze/AnalyzeUtils.java	15.57%	103 Missing ⚠️
...geengine/dataregion/modification/TagPredicate.java	63.80%	38 Missing ⚠️
.../iotdb/db/storageengine/dataregion/DataRegion.java	50.00%	3 Missing ⚠️
...ine/dataregion/modification/DeletionPredicate.java	82.35%	3 Missing ⚠️
...ne/dataregion/modification/TableDeletionEntry.java	0.00%	2 Missing ⚠️
...ol/thrift/impl/DataNodeInternalRPCServiceImpl.java	0.00%	1 Missing ⚠️
...ne/plan/relational/analyzer/StatementAnalyzer.java	0.00%	1 Missing ⚠️
...ryengine/plan/relational/sql/ast/DeleteDevice.java	0.00%	1 Missing ⚠️
...g/apache/iotdb/db/storageengine/StorageEngine.java	87.50%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #18079      +/-   ##
============================================
+ Coverage     41.41%   41.59%   +0.18%     
  Complexity      318      318              
============================================
  Files          5281     5295      +14     
  Lines        369096   371621    +2525     
  Branches      47749    48105     +356     
============================================
+ Hits         152862   154584    +1722     
- Misses       216234   217037     +803     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Caideyipi]

Thanks for the work on supporting attribute filters in table deletion. I found a few issues that should be addressed before merge:

1. IS NOT NULL tag predicates are dropped when they are combined with attribute filters.

   In AnalyzeUtils.parsePredicate, the IsNotNullPredicate branch only handles shouldQueryDevice(). Unlike the ComparisonExpression and IsNullPredicate branches, it does not add tag-only predicates to deviceFilterExpressions when shouldFilterDevice() is true. Later, when any attribute predicate exists, tagPredicate is replaced by new DeviceIn(deviceIDs), so the original SegmentNotNull predicate is lost.

   For example:

   DELETE FROM t WHERE site IS NOT NULL AND attr1 = 'red'

   may delete data from devices whose attr1 = 'red' but whose site tag is NULL. Please either include tag IS NOT NULL in the schema fetch predicate list, or preserve/intersect the original tag predicate when converting matched devices to DeviceIn.

2. The existing integration test expectation for deviceId IS NOT NULL looks stale.

   testDeleteData still expects:

   DELETE FROM vehicle1 WHERE time < 10 AND deviceId IS NOT NULL

   to fail with "Unsupported expression", but this PR adds tag IS NOT NULL support via parseIsNotNull. This test should now fail unless the expectation and subsequent data validation are updated.

3. Attribute comparison predicates need explicit validation before being sent to the schema fetcher.

   parseComparison returns PredicateParseResult.attribute(...) without checking the operator or right-hand value type. Inputs such as attr1 = 1, attr1 = null, or unsupported comparison operators can flow into later schema-filter conversion code and trigger casts/internal exceptions instead of a clear semantic error. Please validate attribute predicates here, or make the schema predicate conversion layer return a proper SemanticException for invalid attribute predicates.

[sonarqubecloud]

Quality Gate passed

Issues
16 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
3.3% Duplication on New Code

See analysis details on SonarQube Cloud