Maciej let's fix SPARK-13283. It won't block 1.6.2 though.
On Thu, Jun 23, 2016 at 5:45 AM, Maciej Bryński wrote:
> -1
>
> I need SPARK-13283 to be solved.
>
> Regards,
> Maciek Bryński
>
> 2016-06-23 0:13 GMT+02:00 Krishna Sankar :
>
>> +1 (non-binding, of course)
>>
>> 1. Compiled OSX 10.10 (Y
+1 (non-binding
Regards,
Vaquar khan
On 23 Jun 2016 07:50, "Sean Owen" wrote:
> I don't think that qualifies as a blocker; not even clear it's a
> regression. Even non-binding votes here should focus on whether this
> is OK to release as a maintenance update to 1.6.1.
>
> On Thu, Jun 23, 2016 at
I don't think that qualifies as a blocker; not even clear it's a
regression. Even non-binding votes here should focus on whether this
is OK to release as a maintenance update to 1.6.1.
On Thu, Jun 23, 2016 at 1:45 PM, Maciej Bryński wrote:
> -1
>
> I need SPARK-13283 to be solved.
>
> Regards,
>
-1
I need SPARK-13283 to be solved.
Regards,
Maciek Bryński
2016-06-23 0:13 GMT+02:00 Krishna Sankar :
> +1 (non-binding, of course)
>
> 1. Compiled OSX 10.10 (Yosemite) OK Total time: 37:11 min
> mvn clean package -Pyarn -Phadoop-2.6 -DskipTests
> 2. Tested pyspark, mllib (iPython 4.0)
>
+1 (non-binding, of course)
1. Compiled OSX 10.10 (Yosemite) OK Total time: 37:11 min
mvn clean package -Pyarn -Phadoop-2.6 -DskipTests
2. Tested pyspark, mllib (iPython 4.0)
2.0 Spark version is 1.6.2
2.1. statistics (min,max,mean,Pearson,Spearman) OK
2.2. Linear/Ridge/Lasso Regression OK
2.
+1
On Wed, Jun 22, 2016 at 1:07 PM, Kousuke Saruta
wrote:
> +1 (non-binding)
>
> On 2016/06/23 4:53, Reynold Xin wrote:
>
> +1 myself
>
>
> On Wed, Jun 22, 2016 at 12:19 PM, Sean McNamara <
> sean.mcnam...@webtrends.com> wrote:
>
>> +1
>>
>> On Jun 22, 2016, at 1:14 PM, Michael Armbrust
>> wrot
+1 (non-binding)
On 2016/06/23 4:53, Reynold Xin wrote:
+1 myself
On Wed, Jun 22, 2016 at 12:19 PM, Sean McNamara
mailto:sean.mcnam...@webtrends.com>> wrote:
+1
On Jun 22, 2016, at 1:14 PM, Michael Armbrust
mailto:mich...@databricks.com>> wrote:
+1
On Wed, Jun 22, 2
+1 myself
On Wed, Jun 22, 2016 at 12:19 PM, Sean McNamara wrote:
> +1
>
> On Jun 22, 2016, at 1:14 PM, Michael Armbrust
> wrote:
>
> +1
>
> On Wed, Jun 22, 2016 at 11:33 AM, Jonathan Kelly
> wrote:
>
>> +1
>>
>> On Wed, Jun 22, 2016 at 10:41 AM Tim Hunter
>> wrote:
>>
>>> +1 This release pas
+1
On Jun 22, 2016, at 1:14 PM, Michael Armbrust
mailto:mich...@databricks.com>> wrote:
+1
On Wed, Jun 22, 2016 at 11:33 AM, Jonathan Kelly
mailto:jonathaka...@gmail.com>> wrote:
+1
On Wed, Jun 22, 2016 at 10:41 AM Tim Hunter
mailto:timhun...@databricks.com>> wrote:
+1 This release passes al
+1
On Wed, Jun 22, 2016 at 11:33 AM, Jonathan Kelly
wrote:
> +1
>
> On Wed, Jun 22, 2016 at 10:41 AM Tim Hunter
> wrote:
>
>> +1 This release passes all tests on the graphframes and tensorframes
>> packages.
>>
>> On Wed, Jun 22, 2016 at 7:19 AM, Cody Koeninger
>> wrote:
>>
>>> If we're consid
+1
On Wed, Jun 22, 2016 at 10:41 AM Tim Hunter
wrote:
> +1 This release passes all tests on the graphframes and tensorframes
> packages.
>
> On Wed, Jun 22, 2016 at 7:19 AM, Cody Koeninger
> wrote:
>
>> If we're considering backporting changes for the 0.8 kafka
>> integration, I am sure there a
+1 This release passes all tests on the graphframes and tensorframes
packages.
On Wed, Jun 22, 2016 at 7:19 AM, Cody Koeninger wrote:
> If we're considering backporting changes for the 0.8 kafka
> integration, I am sure there are people who would like to get
>
> https://issues.apache.org/jira/br
If we're considering backporting changes for the 0.8 kafka
integration, I am sure there are people who would like to get
https://issues.apache.org/jira/browse/SPARK-10963
into 1.6.x as well
On Wed, Jun 22, 2016 at 7:41 AM, Sean Owen wrote:
> Good call, probably worth back-porting, I'll try to d
Good call, probably worth back-porting, I'll try to do that. I don't
think it blocks a release, but would be good to get into a next RC if
any.
On Wed, Jun 22, 2016 at 11:38 AM, Pete Robbins wrote:
> This has failed on our 1.6 stream builds regularly.
> (https://issues.apache.org/jira/browse/SPAR
This has failed on our 1.6 stream builds regularly. (
https://issues.apache.org/jira/browse/SPARK-6005) looks fixed in 2.0?
On Wed, 22 Jun 2016 at 11:15 Sean Owen wrote:
> Oops, one more in the "does anybody else see this" department:
>
> - offset recovery *** FAILED ***
> recoveredOffsetRange
Oops, one more in the "does anybody else see this" department:
- offset recovery *** FAILED ***
recoveredOffsetRanges.forall(((or: (org.apache.spark.streaming.Time,
Array[org.apache.spark.streaming.kafka.OffsetRange])) =>
earlierOffsetRangesAsSets.contains(scala.Tuple2.apply[org.apache.spark.str
I'm fairly convinced this error and others that appear timestamp
related are an environment problem. This test and method have been
present for several Spark versions, without change. I reviewed the
logic and it seems sound, explicitly setting the time zone correctly.
I am not sure why it behaves d
Hey Pete,
I just pushed your PR to branch 1.6. As it's not a blocker, it may or may
not be in 1.6.2, depending on if there will be another RC.
On Tue, Jun 21, 2016 at 1:36 PM, Pete Robbins wrote:
> It breaks Spark running on machines with less than 3 cores/threads, which
> may be rare, and it i
It breaks Spark running on machines with less than 3 cores/threads, which
may be rare, and it is maybe an edge case.
Personally, I like to fix known bugs and the fact there are other blocking
methods in event loops actually makes it worse not to fix ones that you
know about.
Probably not a blocke
Nice one, yeah indeed I was doing an incremental build. Not a blocker.
I'll have a look into the others, though I suspect they're problems
with tests rather than production code.
On Tue, Jun 21, 2016 at 6:53 PM, Marcelo Vanzin wrote:
> On Tue, Jun 21, 2016 at 10:49 AM, Sean Owen wrote:
>> I'm ge
On Tue, Jun 21, 2016 at 10:49 AM, Sean Owen wrote:
> I'm getting some errors building on Ubuntu 16 + Java 7. First is one
> that may just be down to a Scala bug:
>
> [ERROR] bad symbolic reference. A signature in WebUI.class refers to
> term eclipse
> in package org which is not available.
This i
I'm getting some errors building on Ubuntu 16 + Java 7. First is one
that may just be down to a Scala bug:
[ERROR] bad symbolic reference. A signature in WebUI.class refers to
term eclipse
in package org which is not available.
It may be completely missing from the current classpath, or the versio
Hey Pete,
I didn't backport it to 1.6 because it just affects tests in most cases.
I'm sure we also have other places calling blocking methods in the event
loops, so similar issues are still there even after applying this patch.
Hence, I don't think it's a blocker for 1.6.2.
On Tue, Jun 21, 2016
The PR (https://github.com/apache/spark/pull/13055) to fix
https://issues.apache.org/jira/browse/SPARK-15262 was applied to 1.6.2
however this fix caused another issue
https://issues.apache.org/jira/browse/SPARK-15606 the fix for which (
https://github.com/apache/spark/pull/13355) has not been back
Please vote on releasing the following candidate as Apache Spark version
1.6.2. The vote is open until Wednesday, June 22, 2016 at 22:00 PDT and
passes if a majority of at least 3+1 PMC votes are cast.
[ ] +1 Release this package as Apache Spark 1.6.2
[ ] -1 Do not release this package because ...
25 matches
Mail list logo