Query logics using the CompositeQueryLogicTransformer are not populating sourceCount, seekCount, nextCount, yieldCount, fiRanges, docRanges in the query metric because CompositeQueryLogicTransformer doesn't implement the WritesQueryMetrics interface.
I considered delegating the totaling of the various fields to the metric-api module, but after adding "implements WritesQueryMetrics," to CompositeQueryLogicTransformer the class must implement the getters for sources, seeks, nexts, etc which iterate over the delegates to total these values.
With those methods in place, it is just simpler to use those totals in writeQueryMetrics. Any future metric field counts held by a transformer would have to be added to the WritesQueryMetrics interface.
Query logics using the CompositeQueryLogicTransformer are not populating sourceCount, seekCount, nextCount, yieldCount, fiRanges, docRanges in the query metric because CompositeQueryLogicTransformer doesn't implement the WritesQueryMetrics interface.
I considered delegating the totaling of the various fields to the metric-api module, but after adding "implements WritesQueryMetrics," to CompositeQueryLogicTransformer the class must implement the getters for sources, seeks, nexts, etc which iterate over the delegates to total these values.
With those methods in place, it is just simpler to use those totals in writeQueryMetrics. Any future metric field counts held by a transformer would have to be added to the WritesQueryMetrics interface.