Re: critical bugs to be fixed in Spark 2.0.1?

https://issues.apache.org/jira/plugins/servlet/mobile#issue/SPARK-17100 It's a blocker for upgrading. I'd be happy to try and fix it if anyone has any hints. On Tue, 23 Aug 2016, 04:20 Robert Kruszewski, wrote: > SPARK-16991 (https://github.com/apache/spark/pull/14661)

Re: critical bugs to be fixed in Spark 2.0.1?

SPARK-16991 (https://github.com/apache/spark/pull/14661) would be nice Robert From: Reynold Xin Date: Monday, August 22, 2016 at 8:14 PM To: "dev@spark.apache.org" Subject: critical bugs to be fixed in Spark 2.0.1? We should work on a 2.0.1

critical bugs to be fixed in Spark 2.0.1?

We should work on a 2.0.1 release soon, since we have found couple critical bugs in 2.0.0. Are there any critical bugs outstanding that we should address in 2.0.1?

Analyzer.resolver a duplicate of CatalystConf.resolver?

Hi, Analyzer.resolver returns a Resolver per CatalystConf setting [1] that seems a duplicate of CatalystConf.resolver. Unless I'm mistaken, the code could get simpler and be as follows: def resolver: Resolver = conf.resolver Would you agree? I'm ready with a PR if so (plus some other typo

Why is isStreaming naming-inconsistent with analyzed and resolved in LogicalPlan?

Hi, Just noticed that LogicalPlan.isStreaming flag [1] is inconsistent name-wise to analyzed and resolved flags. Why is isStreaming not a mere "streaming"? That would make sense to me (esp. given the others). (I did manage to find a reason why it could be isStreaming but would like to hear the