22 at 13:50, Mich Talebzadeh
wrote:
> I have loaded docker files into my docker repository on docker hub and it
> is public.
>
>
> These are built on Spark 3.1.2 OR 3.1.1, with Scala 2.12 and with Java 11
> OR Java 8 on OS jre-slim-buster. The ones built on 3.1.1 with Java 8
&g
I have loaded docker files into my docker repository on docker hub and it
is public.
These are built on Spark 3.1.2 OR 3.1.1, with Scala 2.12 and with Java 11
OR Java 8 on OS jre-slim-buster. The ones built on 3.1.1 with Java 8
should work with GCP
No additional packages are added to PySpark
cool, thanks. testing now.
On Fri, Jul 27, 2018 at 1:04 PM, Sean Owen wrote:
> I posted on the JIRA -- looks like timezone definitions for Kiribati were
> fixed in the 2018d timezone data release, and that's the difference between
> the JDK release that works and does not.
>
> On Fri, Jul 27, 2
I posted on the JIRA -- looks like timezone definitions for Kiribati were
fixed in the 2018d timezone data release, and that's the difference between
the JDK release that works and does not.
On Fri, Jul 27, 2018 at 1:23 PM shane knapp wrote:
> hey everyone!
>
> i'm making great progress on porti
hey everyone!
i'm making great progress on porting the spark builds to run under ubuntu
16.04LTS, but have hit a show-stopper in my testing.
i am not a scala person by any definition of the term, and could really use
some help in trying to figure out what's going on.
details of what i'm running
@Sean, I'm using Java 8 but don't see these errors until I manually build
the API docs. Hence I think dropping Java 7 support may not help.
Right now we don't build docs in most of builds as building docs takes a
long time (e.g.,
https://amplab.cs.berkeley.edu/jenkins/job/spark-m
+1 for all the great work going in for this, HyukjinKwon, and +1 on what Sean
says about "Jenkins builds with Java 8" and we should catch these nasty
javadoc8 issue quickly.
I think that would be the great first step to move away from java 7
_
From: R
I don't know if this would help but I think we can also officially stop
supporting Java 7 ...
On Tue, Feb 7, 2017 at 1:06 PM, Sean Owen wrote:
> I believe that if we ran the Jenkins builds with Java 8 we would catch
> these? this doesn't require dropping Java 7 sup
I believe that if we ran the Jenkins builds with Java 8 we would catch
these? this doesn't require dropping Java 7 support or anything.
@joshrosen I know we are just now talking about modifying the Jenkins jobs
to remove old Hadoop configs. Is it possible to change the master jobs to
use J
to refer,
>
> https://github.com/apache/spark/pull/16013
>
> and the JIRA you kindly opened,
>
> https://issues.apache.org/jira/browse/SPARK-18692
>
>
> On 7 Feb 2017 9:13 a.m., "Joseph Bradley" wrote:
>
> Public service announcement: Our doc build has wor
e:
Public service announcement: Our doc build has worked with Java 8 for brief
time periods, but new changes keep breaking the Java 8 unidoc build.
Please be aware of this, and try to test doc changes with Java 8! In
general, it is stricter than Java 7 for docs.
A shout out to @HyukjinKwon and
Public service announcement: Our doc build has worked with Java 8 for brief
time periods, but new changes keep breaking the Java 8 unidoc build.
Please be aware of this, and try to test doc changes with Java 8! In
general, it is stricter than Java 7 for docs.
A shout out to @HyukjinKwon and
Spark already supports compiling with Java 8. What refactoring are you
referring to, and where do you expect to see performance gains?
On Sat, 20 Aug 2016 at 12:41, Timur Shenkao wrote:
> Hello, guys!
>
> Are there any plans / tickets / branches in repository on Java 8?
>
> I
Hello, guys!
Are there any plans / tickets / branches in repository on Java 8?
I ask because ML library will gain in performance. I'd like to take part in
refactoring.
://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-2.7/566/console
>> ):
>>
>> [error] javac: invalid source release: 1.8
>> [error] Usage: javac
>> [error] use -help for a list of possible options
>>
>>
>> On Tue, Apr 5, 2016 at
M, Josh Rosen
> wrote:
>
>> In order to be able to run Java 8 API compatibility tests, I'm going to
>> push a new set of Jenkins configurations for Spark's test and PR builders
>> so that those jobs use a Java 8 JDK. I tried this once in the past and it
>> s
Rosen wrote:
> In order to be able to run Java 8 API compatibility tests, I'm going to
> push a new set of Jenkins configurations for Spark's test and PR builders
> so that those jobs use a Java 8 JDK. I tried this once in the past and it
> seemed to introduce some rare,
In order to be able to run Java 8 API compatibility tests, I'm going to
push a new set of Jenkins configurations for Spark's test and PR builders
so that those jobs use a Java 8 JDK. I tried this once in the past and it
seemed to introduce some rare, transient flakiness in certain te
, Upender Nimbekar
wrote:
> Great News ! I've been awaiting this release to start doing some coding
> with Spark using Java 8. Can I run Spark 1.0 examples on a virtual host
> with 16 GB ram and fair descent amount of hard disk ? Or do I reaaly need
> to use a cluster of machines.
&g
Great News ! I've been awaiting this release to start doing some coding
with Spark using Java 8. Can I run Spark 1.0 examples on a virtual host
with 16 GB ram and fair descent amount of hard disk ? Or do I reaaly need
to use a cluster of machines.
Second, are there any good exmaples of using
20 matches
Mail list logo
