I'm sorry, in the previous mail I was wrong and what I had in mind was the CompletableFuture.
The use case I have in mind is a user that wants to fire say N batch jobs and then, after all these are complete, fire a last job. If TableResult extends CompletableFuture or has a method to convert to CompletableFuture, the user can use the JDK methods to compose async results, like CompletableFuture.allOf(taskOne, taskTwo, taskThree). The point of this is just to have a better integration with JDK built-in concurrency utilities. On Mon, Oct 11, 2021 at 5:01 PM Jark Wu <imj...@gmail.com> wrote: > Hi Francesco, > > Do you have a use case for "Future<CloseableIterator<Row>>"? > When do users need this? > > Best, > Jark > > On Mon, 11 Oct 2021 at 21:27, Francesco Guardiani <france...@ververica.com > > > wrote: > > > Hi all, > > Looking at the TableResult type I was wondering, given the interface has > > await methods, should we instead implement the JDK's Future as > > Future<CloseableIterator<Row>> and deprecate the await methods? > > > > This should allow users to integrate with other JDK types without going > > through the conversion from TableResult to Future/CompletableFuture. > > > > WDYT? > > > > FG > > > > -- > > > > Francesco Guardiani | Software Engineer > > > > france...@ververica.com > > > > > > <https://www.ververica.com/> > > > > Follow us @VervericaData > > > > -- > > > > Join Flink Forward <https://flink-forward.org/> - The Apache Flink > > Conference > > > > Stream Processing | Event Driven | Real Time > > > > -- > > > > Ververica GmbH | Invalidenstrasse 115, 10115 Berlin, Germany > > > > -- > > > > Ververica GmbH > > > > Registered at Amtsgericht Charlottenburg: HRB 158244 B > > > > Managing Directors: Karl Anton Wehner, Holger Temme, Yip Park Tung Jason, > > Jinwei (Kevin) Zhang > > >
