Hi Marcelo,
The reason I asked about the mesos profile was that I thought it was
part of the branch already and wondered why nobody used it to compile
Spark with all the code available.
I do understand no code changes were introduced during this profile
maintenance, but with the profile that
The part I don't understand is: why do you care so much about the mesos profile?
The same code exists in branch-2.0, it just doesn't need a separate
profile to be enabled (it's part of core). As Sean said, the change in
master was purely organizational, there's no added or lost
functionality.
On
Spark's branch-2.0 is a maintenance branch, effectively meaning that only
bug-fixes will be added to it. There are other maintenance branches (such
as branch-1.6) that are also receiving bug-fixes in theory, but not so much
in fact as maintenance branches get older. The major and minor version
Hi Sean,
I remember a similar discussion about the releases in Spark and I must
admit it again -- I simply don't get it. I seem to not have paid
enough attention to details to appreciate it. I apologize for asking
the very same questions again and again. Sorry.
Re the next release, I was
Master is implicitly 2.1.x right now. When branch-2.1 is cut, master
becomes the de facto 2.2.x branch. It's not true that the next release
is 2.0.2. You can see the master version:
https://github.com/apache/spark/blob/master/pom.xml#L29
On Sun, Sep 25, 2016 at 12:30 PM, Jacek Laskowski
Hi Sean,
So, another question would be when is the change going to be released
then? What's the version for the master? The next release's 2.0.2 so
it's not for mesos profile either :(
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0
It's a change to the structure of the project, and probably not
appropriate for a maintenance release. 2.0.1 core would then no longer
contain Mesos code while 2.0.0 did.
On Sun, Sep 25, 2016 at 12:26 PM, Jacek Laskowski wrote:
> Hi Sean,
>
> Sure, but then the question is why
Hi Sean,
Sure, but then the question is why it's not a part of 2.0.1? I thought
it was considered ready for prime time and so should be shipped in
2.0.1.
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark
Follow me
It was added to the master branch, and this is a release from the 2.0.x branch.
On Sun, Sep 25, 2016 at 12:12 PM, Jacek Laskowski wrote:
> Hi,
>
> That's even more interesting. How's so since the profile got added a
> week ago or later and RC2 was cut two/three days ago? Anyone
Hi,
That's even more interesting. How's so since the profile got added a
week ago or later and RC2 was cut two/three days ago? Anyone know?
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark
Follow me at
There is no "mesos" profile in 2.0.1.
On Sat, Sep 24, 2016 at 2:19 PM, Jacek Laskowski wrote:
> Hi,
>
> I keep asking myself why are you guys not including -Pmesos in your
> builds? Is this on purpose or have you overlooked it?
>
> Pozdrawiam,
> Jacek Laskowski
>
>
Hi all,
The R API documentation version error was reported in a separate thread.
I've built a release candidate (RC3) and will send out a new vote email in
a bit.
On Thu, Sep 22, 2016 at 11:01 PM, Reynold Xin wrote:
> Please vote on releasing the following candidate as
The binary artifact that's published here is built with -Pmesos. The
'real' artifact from a process standpoint is the source release,
however. That's why we do (should) test the source release foremost.
I suppose individuals are invited to test with a configuration that is
of interest to them,
Hi,
I keep asking myself why are you guys not including -Pmesos in your
builds? Is this on purpose or have you overlooked it?
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark
Follow me at
+1 (non binding)
I compiled and tested on the following two systems.
- CentOS 7.2 / Oracle JDK 1.8.0_77 / R 3.3.1 with -Pyarn -Phadoop-2.7
-Pkinesis-asl -Phive -Phive-thriftserver -Dsparkr
- CentOS 7.2 / Open JDK 1.8.0_102 with -Pyarn -Phadoop-2.7 -Pkinesis-asl
-Phive -Phive-thriftserver
Bests,
+1 non binding
No issue found.
Regards,
Vaquar khan
On 23 Sep 2016 17:25, "Mark Hamstra" wrote:
Similar but not identical configuration (Java 8/macOs 10.12 with build/mvn
-Phive -Phive-thriftserver -Phadoop-2.7 -Pyarn clean install);
Similar but not identical failure:
Similar but not identical configuration (Java 8/macOs 10.12 with build/mvn
-Phive -Phive-thriftserver -Phadoop-2.7 -Pyarn clean install);
Similar but not identical failure:
...
- line wrapper only initialized once when used as encoder outer scope
Spark context available as 'sc' (master =
+1 (non-binding)
Build:
OK, but can no longer use the "--tgz" option when
calling make-distribution.sh (maybe a problem on my side?)
Run:
No regressions from 2.0.0 detected. Tested our pipelines on a standalone
cluster (Python API)
On 23 September 2016 at 08:01, Reynold Xin
+1
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark
Follow me at https://twitter.com/jaceklaskowski
On Fri, Sep 23, 2016 at 8:01 AM, Reynold Xin wrote:
> Please vote on releasing the
19 matches
Mail list logo