Skip to content

Commit

Permalink
dq_input_transform_lookup: fix maxKeysInRequest logic
Browse files Browse the repository at this point in the history
one row of data was lost once maxKeysInRequest reached
  • Loading branch information
yumkam committed Aug 8, 2024
1 parent f010ee3 commit c687673
Showing 1 changed file with 2 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -168,9 +168,8 @@ class TInputTransformStreamLookupBase
const auto maxKeysInRequest = LookupSource.first->GetMaxSupportedKeysInRequest();
IDqAsyncLookupSource::TUnboxedValueMap keysForLookup{maxKeysInRequest, KeyTypeHelper->GetValueHash(), KeyTypeHelper->GetValueEqual()};
while (
((InputFlowFetchStatus = FetchWideInputValue(inputRowItems)) == NUdf::EFetchStatus::Ok) &&
(keysForLookup.size() < maxKeysInRequest)
) {
(keysForLookup.size() < maxKeysInRequest) &&
((InputFlowFetchStatus = FetchWideInputValue(inputRowItems)) == NUdf::EFetchStatus::Ok)) {
NUdf::TUnboxedValue* keyItems;
NUdf::TUnboxedValue key = HolderFactory.CreateDirectArrayHolder(InputJoinColumns.size(), keyItems);
for (size_t i = 0; i != InputJoinColumns.size(); ++i) {
Expand Down

0 comments on commit c687673

Please sign in to comment.