AlanConfluent commented on PR #26567: URL: https://github.com/apache/flink/pull/26567#issuecomment-3090248330
> @AlanConfluent Given that retry-on-empty-result is an existing behavior, maybe it is OK to check in the code as is. We can do a quick follow up FLIP to improve the behavior. Please let me know if you have time for this. I can find someone from LinkedIn to help if you don't have time. Thanks. I have some time budget to follow up with this. I think your suggestions are good and it would be nice to make this more flexible. I'm happy to do a followup FLIP covering this and it might make sense to cover async scalar as well. In that case, there is always one result, but it could be null. I think the current code actually allows null, so I'm not sure that the empty response check is ever triggered for async scalar, but maybe it should be. Or maybe it makes less sense for the scalar case? Tell me what you think. Either way, happy to merge the code in this state and do an immediate follow up FLIP for empty case. -- 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]
