Re: [DISCUSS] Beam public roadmap

Indeed, our current in-progress subsection isn't visible enough. It is also too coarse grained. Perhaps we can replace it with a list of current and proposed initiatives? I could see the index live on the web site, but would prefer individual, per-initiative pages to live on the wiki. That way

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

Romain has brought up two good aspects of backwards compatibility: - runtime replacement vs recompile - consumer (covariant) vs producer (contravariant, such as interfaces a user implements) In this case, I think the best shoice is covariant and contravariant (invariant) backwards compat

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

Beam does not catch Exception for function usage so it will have to do it in some places. A user does not have to execute the function so worse case it impacts tests and in any case the most important: it does not impact the user until it recompiles the code (= runtime is not impacted). Romain

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

What in Beam codebase is not ready, and how do we know that user code doesn't have the same issue? On Sun, Oct 14, 2018 at 6:04 AM Romain Manni-Bucau wrote: > Hmm, tested also and it works until something in the codeflow does not > respect that constraint - see >

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

Hmm, tested also and it works until something in the codeflow does not respect that constraint - see com.sun.tools.javac.comp.Flow.FlowAnalyzer#errorUncaught. In other words beam codebase is not ready for that and will make it fail but it is ok cause we can fix it but user code does not rely on

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

Just tried it, doesn't appear to work :( error: unreported exception Exception; must be caught or declared to be thrown On Sun, Oct 14, 2018 at 1:55 AM Romain Manni-Bucau wrote: > not with java>=8 AFAIK > > Romain Manni-Bucau > @rmannibucau | Blog >

Re: [Proposal] Euphoria DSL - looking for reviewers

Thanks Kenn and Reuven! This brings up the question, how should we proceed with the further development? Up until now, we did all changes in our own repository, which was very flexible as we could do code reviews and PR merges by ourselves. We would love to take a full responsibility for the

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

not with java>=8 AFAIK Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

But it means that other functions that call SerializableFunctions must now declare exceptions, right? If yes, this is incompatible. On Sun, Oct 14, 2018 at 1:37 AM Romain Manni-Bucau wrote: > No, only parameter types and return type is used to lookup methods. > > Romain Manni-Bucau >

Re: Can we allow SimpleFunction and SerializableFunction to throw Exception?

I've run into this problem before as well. Doesn't changing the signature involve a backwards-incompatible change though? On Wed, Oct 3, 2018 at 5:11 PM Jeff Klukas wrote: > I'm working on https://issues.apache.org/jira/browse/BEAM-5638 to add > exception handling options to single message

Re: [PROPOSAL] allow the users to anticipate the support of features in the targeted runner.

Sounds like a good idea. I don't think it will work for all capabilities (e.g. some of them such as "exactly once" apply to all of the API surface), but useful for the ones that we can capture. On Thu, Oct 4, 2018 at 2:43 AM Etienne Chauchot wrote: > Hi guys, > As part of our user experience