+1
Though following is commonly use standard for
release(http://semver.org/) ,feature
also looks good as Minor release indicate significant features have been
added
1. MAJOR version when you make incompatible API changes,
2. MINOR version when you add functionality in a backwards-compatible
All,
I have resolved the issue.
Sorry for your interruption.
Regards,
Miki
-Original Message-
From: Shingo Miki(新郷 美紀)
Sent: Thursday, July 28, 2016 6:34 PM
To: dev@spark.apache.org
Subject: ERROR: java.net.UnknownHostException
To whom who has knowledge?
I have faced the following
If I define a UDF in PySpark that has a return type of FloatType, but the
underlying function actually returns an int, the UDF throws the int away
and returns None.
It seems that some machinery inside pyspark.sql.types is perhaps unaware
that it can always cast ints to floats.
Is this functionali
+1
The semantics conveyed by "feature release" are compatible with the meaning
of "minor release" under strict SemVer, but as argued are clearer from a
user-communication point of view.
http://semver.org
Nick
2016년 7월 28일 (목) 오후 7:20, Matei Zaharia 님이 작성:
> I also agree with this given the way
I also agree with this given the way we develop stuff. We don't really want to
move to possibly-API-breaking major releases super often, but we do have lots
of large features that come out all the time, and our current name doesn't
convey that.
Matei
> On Jul 28, 2016, at 4:15 PM, Reynold Xin
Hi Miki,
What version of Spark are you using?
If the version is > 1.4, you might hit SPARK-11227.
- Kousuke
On 2016/07/28 18:34, Miki Shingo wrote:
To whom who has knowledge?
I have faced the following error try to use HA configuration.
(java.net.UnknownHostException)
below is the error fo
Yea definitely. Those are consistent with what is defined here:
https://cwiki.apache.org/confluence/display/SPARK/Spark+Versioning+Policy
The only change I'm proposing is replacing "minor" with "feature".
On Thu, Jul 28, 2016 at 4:10 PM, Sean Owen wrote:
> Although 'minor' is the standard term
Although 'minor' is the standard term, the important thing is making
the nature of the release understood. 'feature release' seems OK to me
as an additional description.
Is it worth agreeing on or stating a little more about the theory?
patch release: backwards/forwards compatible within a minor
reminder -- this is happening TOMORROW.
On Wed, Jul 27, 2016 at 5:39 PM, shane knapp wrote:
> reminder -- this is happening friday afternoon.
>
> i will pause the build queue late friday morning.
>
> On Mon, Jul 25, 2016 at 2:29 PM, shane knapp wrote:
>> around 1pm friday, july 29th, we will be
*tl;dr*
I would like to propose renaming “minor release” to “feature release” in
Apache Spark.
*details*
Apache Spark’s official versioning policy follows roughly semantic
versioning. Each Spark release is versioned as
[major].[minor].[maintenance]. That is to say, 1.0.0 and 2.0.0 are both
“maj
To whom who has knowledge?
I have faced the following error try to use HA configuration.
(java.net.UnknownHostException)
below is the error for reference.
16/07/27 22:42:56 WARN TaskSetManager: Lost task 0.0 in stage 0.0 (TID 0,
dphmuyarn1107.hadoop.local): java.lang.IllegalArgumentException:
16/07/28 17:07:34 WARN shortcircuit.DomainSocketFactory: The short-circuit
local reads feature cannot be used because libhadoop cannot be loaded.
java.lang.NoClassDefFoundError: com/sun/jersey/api/client/config/ClientConfig
at
org.apache.hadoop.yarn.client.api.TimelineClient.createTimelineClien
12 matches
Mail list logo