[5.x]: NcML Logical Reduce using new API

[lesserwhirls]

Versions impacted by the bug

v5.x, v6.x, v7.x

What went wrong?

Using logicalReduce in NcML when using the new builder-based API has no effect, so likely not implemented yet. Simple example - consider the following NcML:

<?xml version="1.0" encoding="UTF-8"?>
<netcdf xmlns="http://www.unidata.ucar.edu/namespaces/netcdf/ncml-2.2">
  <dimension name="a" length="5" />
  <dimension name="b" length="1" />
  <variable name="var" shape="a b" type="float">
    <values start="0" increment="1" />
  </variable>
  <variable name="var">
    <logicalReduce dimNames="b"/>
  </variable>
</netcdf>

When using the old API, the variable var looks like float var(a=5);, which is expected. Using the new API, it looks like float var(a=5, b=1);. Marked in version 5, as priority should be there for the TDS, which is where this came up.

Relevant stack trace

No response

Relevant log messages

No response

If you have an example file that you can share, please attach it to this issue.

If so, may we include it in our test datasets to help ensure the bug does not return once fixed?
Note: the test datasets are publicly accessible without restriction.

Yes

Code of Conduct

• I agree to follow the UCAR/Unidata Code of Conduct