Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108578208
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user dibbhatt commented on the pull request:
https://github.com/apache/spark/pull/6614#issuecomment-108578541
I am sorry. My bad . Do let me know if latest change looks fine
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108584145
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108590277
[Test build #34101 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34101/consoleFull)
for PR 5400 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6606#issuecomment-108592425
[Test build #34104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34104/consoleFull)
for PR 6606 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108592240
LGTM pending tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6606#issuecomment-108592159
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6606#issuecomment-108592205
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108605386
@rxin Can you please post a link to the broken build? I don't think any
hadoop-2 specific APIs were used - either way there should be an equivalent API
in
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6504#issuecomment-108605593
Nice, it's much simpler now. The current PR looks good except for the
Java/Python examples. Who is going to add them? If you need me to, then I can
send an update
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6608
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6618#issuecomment-108616232
On closer investigation, this bug doesn't seem to directly affect Spark
1.3+.
Also, SPARK-8086 appears to be a false alarm due to some issues in test
code.
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5400#discussion_r31656765
--- Diff:
network/common/src/main/java/org/apache/spark/network/buffer/LargeByteBuffer.java
---
@@ -0,0 +1,135 @@
+/*
+* Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6585#issuecomment-108576886
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6585#issuecomment-108576822
[Test build #34087 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34087/consoleFull)
for PR 6585 at commit
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/6611#issuecomment-108577103
Mind giving this a more descriptive title that includes [MLLIB]?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108592820
[Test build #34105 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34105/consoleFull)
for PR 5400 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108593669
[Test build #34106 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34106/consoleFull)
for PR 6595 at commit
Github user rapen commented on the pull request:
https://github.com/apache/spark/pull/4449#issuecomment-108602224
@squito thanks! your work is very helpful. I'm testing now solution based
on your code. I've subclassed NewHadoopRDD with same changes you've made in
HaddopRDD and then
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108602523
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108577852
Probably not all, but those related to analysis errors.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/6618
[SPARK-8062] Fix NullPointerException in
SparkHadoopUtil.getFileSystemThreadStatistics (branch-1.2)
This patch adds a regression test for an extremely rare bug where
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108616498
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108616473
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108573176
[Test build #34097 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34097/consoleFull)
for PR 6616 at commit
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5400#discussion_r31657297
--- Diff:
core/src/main/java/org/apache/spark/network/buffer/LargeByteBufferInputStream.java
---
@@ -0,0 +1,87 @@
+/*
+ * Licensed to the Apache
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/6617
[SPARK-6777] [SQL] Implements backwards compatibility rules in
CatalystSchemaConverter
This PR introduces `CatalystSchemaConverter` for converting Parquet schema
to Spark SQL schema and vice
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6605
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108575164
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108579662
Let's do that later. We should audit all exceptions and decide what to do.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108579952
[Test build #34099 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34099/consoleFull)
for PR 6616 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6612#issuecomment-108587062
[Test build #34100 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34100/consoleFull)
for PR 6612 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108589844
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108589914
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/6613#issuecomment-108589852
Mind giving this a more descriptive title?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108589913
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108589855
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108592163
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108592255
test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5400#issuecomment-108592204
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108594717
[Test build #34093 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34093/consoleFull)
for PR 6608 at commit
Github user leahmcguire commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108594833
Anything I should try to do to fix this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108594730
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/5426#issuecomment-108600878
ping @marmbrus
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
GitHub user harishreedharan opened a pull request:
https://github.com/apache/spark/pull/6619
[HOTFIX] Fix Hadoop-1 build caused by #5972.
Replaced `fs.listFiles` with Hadoop-1 friendly `fs.listStatus` method.
You can merge this pull request into a Git repository by running:
$
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108614038
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108614022
[Test build #34095 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34095/consoleFull)
for PR 5792 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6618#issuecomment-108613848
[Test build #34112 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34112/consoleFull)
for PR 6618 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108571551
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6605#issuecomment-108574312
Thanks @andrewor14 - LGTM. Merging this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/6614#discussion_r31658272
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/receiver/ReceiverSupervisorImpl.scala
---
@@ -136,14 +136,18 @@ private[streaming] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6612#issuecomment-108586838
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6612#issuecomment-108586876
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108590980
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108590955
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108596622
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108597963
This might've broken the Hadoop 1 build
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108598202
[Test build #34107 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34107/consoleFull)
for PR 6386 at commit
Github user harishreedharan commented on the pull request:
https://github.com/apache/spark/pull/6600#issuecomment-108601071
Not suggesting that we change it here - but it looks like ErrorProne does
have a check which we might have to disable for this file -
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108602560
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108602535
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108602789
[Test build #34109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34109/consoleFull)
for PR 6591 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108602619
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6619#issuecomment-108613226
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6618#issuecomment-108613230
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108571502
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108573183
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5400#discussion_r31657556
--- Diff:
network/common/src/main/java/org/apache/spark/network/buffer/LargeByteBuffer.java
---
@@ -0,0 +1,135 @@
+/*
+* Licensed to the Apache
Github user squito commented on a diff in the pull request:
https://github.com/apache/spark/pull/5400#discussion_r31657523
--- Diff:
core/src/main/java/org/apache/spark/network/buffer/LargeByteBufferOutputStream.java
---
@@ -0,0 +1,69 @@
+/*
+ * Licensed to the Apache
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/5400#discussion_r31657551
--- Diff:
core/src/main/java/org/apache/spark/network/buffer/LargeByteBufferInputStream.java
---
@@ -0,0 +1,87 @@
+/*
+ * Licensed to the Apache
Github user dibbhatt commented on a diff in the pull request:
https://github.com/apache/spark/pull/6614#discussion_r31658998
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/receiver/ReceiverSupervisorImpl.scala
---
@@ -136,14 +136,18 @@ private[streaming] class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108591395
[Test build #34103 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34103/consoleFull)
for PR 6617 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108591591
test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108597597
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108597582
[Test build #34103 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34103/consoleFull)
for PR 6617 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108597464
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6386#issuecomment-108597486
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6598#issuecomment-108601292
Alright, one last time... retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6591#issuecomment-108601472
Jenkins, retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6619#issuecomment-108613472
LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6618#issuecomment-108613287
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6619#issuecomment-108613352
[Test build #34110 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34110/consoleFull)
for PR 6619 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6619#issuecomment-108613270
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6620#issuecomment-108613271
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6620#issuecomment-108613220
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6606#issuecomment-108616285
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6606#issuecomment-108616271
[Test build #34104 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34104/consoleFull)
for PR 6606 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6616#issuecomment-108578146
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/6394#discussion_r31657904
--- Diff:
yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala ---
@@ -253,10 +269,26 @@ private[yarn] class YarnAllocator(
* added in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108593311
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6617#issuecomment-108593334
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108593235
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/5792#issuecomment-108600343
Yea that might be good to do. It's not super high cost right now though
since it is caught by the master build matrix, and the frequency of it
happening is low.
---
If
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/5915#issuecomment-108606018
@leahmcguire I'm a bit confused. All of these test failure seem unrelated,
and that last one seemed to work but failed when posting to Github. I'm going
to try
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6615#issuecomment-108606036
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user zeitos commented on a diff in the pull request:
https://github.com/apache/spark/pull/6613#discussion_r31667004
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/RandomProjection.scala ---
@@ -0,0 +1,201 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6620#issuecomment-108613800
[Test build #34111 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/34111/consoleFull)
for PR 6620 at commit
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6600#issuecomment-108571458
In case you guys have not noticed, there's no variable to check, so you
can't loop on anything. This is just a plain wake up.
Yes, you could add one, but that
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/6600#issuecomment-108571472
It's good practice when you are `wait()`-ing on some condition to be true,
but that is not the case here. It may be flagged but it is not an instance of
the actual
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6608#issuecomment-108577456
I think we should also replace all `assert`s and `require`s along the way
with `AnalysisException`.
---
If your project is set up for it, you can reply to this email
1 - 100 of 817 matches
Mail list logo
