Skip to content

Commit e0635fe

Browse files
committed
fix comments.
1 parent e4bd579 commit e0635fe

File tree

1 file changed

+5
-6
lines changed
  • datafusion/physical-plan/src/aggregates/group_values

1 file changed

+5
-6
lines changed

datafusion/physical-plan/src/aggregates/group_values/column.rs

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -207,9 +207,8 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
207207

208208
/// Scalarized intern
209209
///
210-
/// This is used only for `streaming aggregation`,
211-
/// because it depends on the order between `input rows` and their corresponding
212-
/// `group indices`.
210+
/// This is used only for `streaming aggregation`, because `streaming aggregation`
211+
/// depends on the order between `input rows` and their corresponding `group indices`.
213212
///
214213
/// For example, assuming `input rows` in `cols` with 4 new rows
215214
/// (not equal to `exist rows` in `group_values`, and need to create
@@ -222,7 +221,7 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
222221
/// row4
223222
/// ```
224223
///
225-
/// # In [`GroupValuesColumn`], their `group indices` will be
224+
/// # In `scalarized_intern`, their `group indices` will be
226225
///
227226
/// ```text
228227
/// row1 --> 0
@@ -234,7 +233,7 @@ impl<const STREAMING: bool> GroupValuesColumn<STREAMING> {
234233
/// `Group indices` order agrees with their input order, and the `streaming aggregation`
235234
/// depends on this.
236235
///
237-
/// # However In [`VectorizedGroupValuesColumn`], their `group indices` will be
236+
/// # However In `vectorized_intern`, their `group indices` will be
238237
///
239238
/// ```text
240239
/// row1 --> 2
@@ -1020,7 +1019,7 @@ impl<const STREAMING: bool> GroupValues for GroupValuesColumn<STREAMING> {
10201019
self.hashes_buffer.clear();
10211020
self.hashes_buffer.shrink_to(count);
10221021

1023-
// Such structure is only used in `non-streaming` case
1022+
// Such structures are only used in `non-streaming` case
10241023
if !STREAMING {
10251024
self.group_index_lists.clear();
10261025
self.emit_group_index_list_buffer.clear();

0 commit comments

Comments
 (0)