wiedld commented on code in PR #7842: URL: https://github.com/apache/arrow-datafusion/pull/7842#discussion_r1361348100
########## datafusion/physical-plan/src/sorts/batches.rs: ########## @@ -0,0 +1,29 @@ +// Licensed to the Apache Software Foundation (ASF) under one +// or more contributor license agreements. See the NOTICE file +// distributed with this work for additional information +// regarding copyright ownership. The ASF licenses this file +// to you under the Apache License, Version 2.0 (the +// "License"); you may not use this file except in compliance +// with the License. You may obtain a copy of the License at +// +// http://www.apache.org/licenses/LICENSE-2.0 +// +// Unless required by applicable law or agreed to in writing, +// software distributed under the License is distributed on an +// "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +// KIND, either express or implied. See the License for the +// specific language governing permissions and limitations +// under the License. + +#[derive(Debug, Copy, Clone, Default)] +pub(crate) struct BatchCursor<C> { + /// The index into SortOrderBuilder::batches + /// TODO: this will become a BatchId, for record batch collected (and not passed across streams) + pub batch_idx: usize, + + /// The row index within the given batch + pub row_idx: usize, + + /// The cursor for the given batch. + pub cursor: C, Review Comment: Had a choice of doing `Option<C>` in the batch cursor, or within the `SortOrderBuilder::cursors`. Chose to add the option within the latter, as the yielded merge stream will contain this BatchCursor (containing any batch and batch/slice offset identifiers). Therefore the option handling is within the SortOrderBuilder. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
