Fix Bug in Handling Empty Filters in Time Series + Minor Fixes

[ankitsultana]

We were getting NPE for empty filters since transform operator can return a null value block. This handles that case, and additionally

• Improve the explain name for Leaf Time Series Plan node.
• Improves some QueryContextUtils methods which are used in places like segment pruner service.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review.

Project coverage is 63.80%. Comparing base (59551e4) to head (6edb226).
Report is 1163 commits behind head on master.

Files with missing lines	Patch %	Lines
...ator/timeseries/TimeSeriesAggregationOperator.java	0.00%	2 Missing and 1 partial ⚠️
...query/request/context/utils/QueryContextUtils.java	50.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #14192      +/-   ##
============================================
+ Coverage     61.75%   63.80%   +2.05%     
- Complexity      207     1536    +1329     
============================================
  Files          2436     2622     +186     
  Lines        133233   144378   +11145     
  Branches      20636    22094    +1458     
============================================
+ Hits          82274    92122    +9848     
- Misses        44911    45458     +547     
- Partials       6048     6798     +750     

Flag	Coverage Δ
custom-integration1	100.00% <ø> (+99.99%)	⬆️
integration	100.00% <ø> (+99.99%)	⬆️
integration1	100.00% <ø> (+99.99%)	⬆️
integration2	0.00% <ø> (ø)
java-11	63.75% <42.85%> (+2.04%)	⬆️
java-21	63.70% <42.85%> (+2.07%)	⬆️
skip-bytebuffers-false	63.80% <42.85%> (+2.05%)	⬆️
skip-bytebuffers-true	63.66% <42.85%> (+35.93%)	⬆️
temurin	63.80% <42.85%> (+2.05%)	⬆️
unittests	63.80% <42.85%> (+2.05%)	⬆️
unittests1	55.50% <14.28%> (+8.61%)	⬆️
unittests2	34.32% <28.57%> (+6.59%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[raghavyadav01]

Can we make the changes to trigger the dump of physical and logical plan from client for timeseries? As of now we do not have a way to dump similar to explain in SQL query.

[gortiz]

Remember we just added a new explain mode that is quite more useful that the normal one we have in V2: #13733

[ankitsultana]

Yeah I think we should wait for the multistage-engine integration before explain plan support, so we have a cohesive way to compute them. The new explain mode is quite cool and we should support similar semantics for the time-series engine too. I'll be raising a proposal this month.