For what it's worth there exists a relatively easy Java8 to Scala future
conversion so this shouldn't cause an issue on the Spark runner.
On Thu, Feb 1, 2018 at 11:22 PM, Alexey Romanenko <aromanenko....@gmail.com>
> +1, sounds great!
> On 2 Feb 2018, at 07:14, Thomas Weise <t...@apache.org> wrote:
> On Thu, Feb 1, 2018 at 9:07 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
>> On 02/01/2018 07:54 PM, Kenneth Knowles wrote:
>> > Hi all,
>> > Luke, Thomas, and I had some in-person discussions about the use of
>> Java 8
>> > futures and Guava futures in the portability support code. I wanted to
>> bring our
>> > thoughts to the dev list for feedback.
>> > As background:
>> > - Java 5+ "Future" lacks the main purpose of future, which is async
>> > - Guava introduced ListenableFuture to do real future-oriented
>> > - Java 8 added CompletionStage which is more-or-less the expected
>> > It is still debatable whether Java got it right . But since it is
>> > standardized, doesn't need to be shaded, etc, it is worth trying to
>> just use it
>> > carefully in the right ways. So we thought to propose that we migrate
>> most uses
>> > of Guava futures to Java 8 futures.
>> > What do you think? Have we missed an important problem that would make
>> this a
>> > deal-breaker?
>> > Kenn
>> > 
>> > e.g. https://stackoverflow.com/questions/38744943/listenable
>> > and such discussions are likely to occur whenever you bring it up with
>> > who cares a lot about futures :-)
>> Jean-Baptiste Onofré
>> Talend - http://www.talend.com