Github user pwendell commented on the issue:
https://github.com/apache/spark/pull/14342
LGTM - I added these and I think they are dead code right now.
---
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
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/10461#discussion_r48445168
--- Diff: dev/deps/spark-deps-hadoop-2.4 ---
@@ -0,0 +1,185 @@
+JavaEWAH-0.3.2.jar
--- End diff --
yes these are automatically generated
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/10395#issuecomment-166069156
LGTM (I downloaded your PR and did some grepping to make sure there are no
references). One other thing that occured to me is someone could easily create
a package
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/10317#issuecomment-164923664
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/10108#issuecomment-161418651
Hey @marmbrus is actually managing the RC - it just has my name on it
because some automated tooling uses my account. Ping @marmbrus.
---
If your project is set up
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/10108#issuecomment-161419476
BTW @srowen, some protocol for announcing these is probably a good idea to
avoid races. I think we haven't suffered from races in the past, but mostly out
of luck
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9767#issuecomment-161203603
Yeah I think it's fine to pull in - but do it quickly because an RC will go
out very soon!
---
If your project is set up for it, you can reply to this email and have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9924#issuecomment-159118994
Jenkins, retest this please. This LGTM - I think it's good to simply remove
it.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1297#issuecomment-158851260
@josephlijia this feature has moved into a Spark package. If you want to
file an issue report it's best to do it here:
https://github.com/amplab/spark
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9697#issuecomment-157469133
Yep, this 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-155962272
Regarding testing, the best way is to inspect the contents of the jar to
make sure that the shaded version is inlined. If Spark code uses the shaded
dependency
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9615#discussion_r44503873
--- Diff: pom.xml ---
@@ -2165,6 +2166,9 @@
org.eclipse.jetty:jetty-security
org.eclipse.jetty:jetty-util
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9512#issuecomment-155334662
This looks fine (i.e. LGTM). However, we could also look into actually
shading asm ourselves in our published artifacts, similar to how we now shade
jetty and other
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9503#issuecomment-155341829
I only reviewed the build changes, but they look good to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9575#issuecomment-155341204
It's hard for me to rule out that there is _no_ other reason lib_managed is
used at present. I audited all the uses of it I could find in the codebase and
it appears
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r44055168
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/EmittedRecordsDStream.scala
---
@@ -0,0 +1,101 @@
+/*
+ * Licensed
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43980418
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -350,6 +349,18 @@ class PairDStreamFunctions[K, V
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43980438
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/TrackStateSpec.scala ---
@@ -0,0 +1,111 @@
+/*
+ * Licensed to the Apache Software
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43980731
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/EmittedRecordsDStream.scala
---
@@ -0,0 +1,101 @@
+/*
+ * Licensed
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43980502
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -350,6 +349,18 @@ class PairDStreamFunctions[K, V
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43981556
--- Diff: streaming/src/main/scala/org/apache/spark/streaming/State.scala
---
@@ -0,0 +1,141 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43982348
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -350,6 +349,18 @@ class PairDStreamFunctions[K, V
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43981921
--- Diff: streaming/src/main/scala/org/apache/spark/streaming/State.scala
---
@@ -0,0 +1,141 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9256#issuecomment-153975680
I took a broad pass on the public API's and left comments throughout,
mostly around naming rather than core structure. What would really be helpful
for me is filling
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43981603
--- Diff: streaming/src/main/scala/org/apache/spark/streaming/State.scala
---
@@ -0,0 +1,141 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43981909
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/EmittedRecordsDStream.scala
---
@@ -0,0 +1,101 @@
+/*
+ * Licensed
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43982371
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -350,6 +349,18 @@ class PairDStreamFunctions[K, V
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43982459
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/dstream/PairDStreamFunctions.scala
---
@@ -350,6 +349,18 @@ class PairDStreamFunctions[K, V
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9256#discussion_r43982032
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/TrackStateSpec.scala ---
@@ -0,0 +1,111 @@
+/*
+ * Licensed to the Apache Software
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-153469556
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-153259490
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
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8512#discussion_r43717724
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkS3Util.scala ---
@@ -0,0 +1,336 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8512#discussion_r43717704
--- Diff: core/pom.xml ---
@@ -40,6 +40,11 @@
${avro.mapred.classifier}
+ com.amazonaws
+ aws-java-sdk
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-153252094
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-153252357
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-153203911
Hey @calvinjia seems okay to merge since this is just triggering other
failures. Can you explain more though how this works around the mima issue -
the patch seems
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-153208299
Got it- thanks I can merge it then.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152892982
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152891750
@calvinjia can you add "[test-hadoop1.0]" to the title of this PR and then
retest it? That will run the tests with hadoop 1. See more info here:
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152923143
Hm - can you try also adding [test-maven] - might be better to test with
maven.
On Sun, Nov 1, 2015 at 9:40 PM, Calvin Jia <notificati...@github.com>
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9395#issuecomment-152929052
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9204#issuecomment-152415593
@haoyuan hey HY - can you not merge build related patches without asking
for feedback from one of the build maintainers (me or @srowen)? This patch
makes changes
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-149127284
Yeah this was my thought - could we provide a summary in the stage page
rather than in the stage index.I do see how an aggregated summary is
significantly more
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9117#issuecomment-149125876
ping @kayousterhout to me it's the normal issue - sure it's useful for some
cases, but is it worth putting in the index page? It could be better to just
put a locality
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9126#issuecomment-148231844
ping @marmbrus for any thoughts. But I think removing them makes sense. If
someone makes it a val later they will have to reason about whether it should
be transient
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8744#discussion_r41951480
--- Diff: yarn/pom.xml ---
@@ -164,6 +164,92 @@
+
+
--- End diff --
Can this say "The YARN applic
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-147493632
I see the underlying problem posed in the JIRA - it's difficult to assess
duration since it currently includes the time spent waiting on dependent
stages. However
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-146293403
SGTM.
On Wed, Oct 7, 2015 at 11:55 AM, Reynold Xin <notificati...@github.com>
wrote:
> (and data size should include all the data,
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8931#discussion_r41426589
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregate.scala
---
@@ -69,6 +72,9 @@ case class TungstenAggregate
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-146285580
I think we want to have concise and consistent names here across all the
metrics. Here is my proposal for naming:
```
input rows
output rows
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-146288685
The reason I like accumulated memory is that it's something that should be
roughly constant over multiple runs of a workload so people can get a sense of
how much data
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/8931#discussion_r41426412
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/aggregate/TungstenAggregate.scala
---
@@ -69,6 +72,9 @@ case class TungstenAggregate
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8931#issuecomment-146289643
BTW - one alternative would be to create an accumulator that tracks max,
min, median, and total and then have it display nicely in two lines. For
instance
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8919#issuecomment-143837144
Hey Sean - looks good to me, but can't claim to be nearly as deep as you
are on this stuff!
---
If your project is set up for it, you can reply to this email and have
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8890#issuecomment-142783383
@rxin I think you should upgrade R/pkg/DESCRIPTION - otherwise LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8350#issuecomment-140562180
No problem - I should have caught it earlier. Hopefully people didn't spin
too many cycles on this.
On Tue, Sep 15, 2015 at 12:56 AM, Sean Owen <notific
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8774#issuecomment-140508440
This is perfect, thanks. LGTM. Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8350#issuecomment-140213492
I think if you update previousVersion in MimaBuild.scala many of these
should go away. I'm happy to look at the error output after doing that.
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8350#issuecomment-140231316
I tested it locally, you'll need something like this:
```
version match {
+case v if v.startsWith("1.6") =>
+
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8350#issuecomment-140286995
Hm - this is a test file that is in the source folder, so MIMA is
complaining about changes. The error message gives you a filter you can add
to the MIMA file
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8437#issuecomment-140288092
LGTM - I've modified that script recently enough to be familiar with how it
works. This seems like a good approach and could be useful for us in the future
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8570#issuecomment-137170215
For the details link - can you use the standard drop down icon we use in
other places?
---
If your project is set up for it, you can reply to this email and have your
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8570#issuecomment-137221455
Yes - I mean the triangle image used there and in a few other places (such
as showing more metrics).
---
If your project is set up for it, you can reply to this email
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/7878#discussion_r38283921
--- Diff: dev/run-tests.py ---
@@ -227,11 +228,32 @@ def build_spark_documentation():
os.chdir(SPARK_HOME)
+def get_zinc_port
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-136268566
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-136255396
Jenkins, 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
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/8531
[SPARK-10359] Enumerate Spark's dependencies in a file and diff against it
for new pull requests
DON'T MERGE ME - TESTING ON JENKINS
You can merge this pull request into a Git repository
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-136250200
Thanks for looking at this @vanzin. I do agree it would be a lot nicer to
base things on comments, but because the comment stream isn't available as
meta-data
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8531#issuecomment-136271740
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135871143
Okay this seems to be passing now - any thoughts @JoshRosen or @vanzin? IMO
this would be really nice since we can test build changes with either build,
before
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135870939
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135582563
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8218#issuecomment-135637236
ping @aarondav
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-135635256
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144791
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135144862
K - I just sent a hotfix to up the timeout.
On Wed, Aug 26, 2015 at 9:51 AM, Marcelo Vanzin notificati...@github.com
wrote:
I'm working on fixing
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134867614
Marcelo you will need to change the timeout in the code itself for it to
increase from 175
On Aug 25, 2015 11:24 PM, UCB AMPLab notificati...@github.com wrote
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135105365
I still don't understand - why not fix the issue in a separate PR, get this
passing and then merge this? It will then benefit the other PR's also that
are facing
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135103392
Okay then - I would do that separately, get this PR passing, then merge it.
It is not good to merge a PR that deterministically fails jenkins. Have we
done
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-135200381
Great - looks good!
On Aug 26, 2015 3:53 PM, Marcelo Vanzin notificati...@github.com wrote:
Yay!
â
Reply to this email directly or view
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134683004
Does this PR increase test time in some way? Just wondering why this would
consistently timeout when others don't.
On Tue, Aug 25, 2015 at 10:43 AM, Marcelo
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134732350
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134422382
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7629#issuecomment-134422378
Yeah sounds good - might be good to let it run one more time just to be
sure it's not affecting jenkins somehow.
On Mon, Aug 24, 2015 at 4:40 PM, Marcelo
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8338#issuecomment-134449642
Yes this LGTM - these are outdated and I don't even think MapR is advising
their customers to use these. They are asking people to use hadoop-provided,
which
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8095#issuecomment-129950381
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-129950164
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-129954901
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-129976266
test
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7878#issuecomment-130156023
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-130155218
Okay will merge this - I've been keeping things in a separate repo and it's
much better to have it in the upstream in case others want to modify it.
---
If your
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-129708771
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
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/8095
SPARK-7726 Add import so Scaladoc doesn't fail.
This is another import needed so Scala 2.11 doc generation doesn't fail.
See SPARK-7726 for more detail. I tested this locally and the 2.11
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/8095#issuecomment-129713711
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
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/7411#discussion_r36684757
--- Diff: dev/create-release/release-build.sh ---
@@ -0,0 +1,320 @@
+#!/usr/bin/env bash
+
+#
+# Licensed to the Apache Software Foundation
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/7411#discussion_r36684821
--- Diff: dev/create-release/release-build.sh ---
@@ -0,0 +1,320 @@
+#!/usr/bin/env bash
+
+#
+# Licensed to the Apache Software Foundation
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7411#issuecomment-129605050
Jenkins, 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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7929#issuecomment-127889147
LGTM - feel free to merge, as it is really taking a toll on our tests right
now.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/7929#discussion_r36273191
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/client/ClientWrapper.scala ---
@@ -62,6 +64,52 @@ private[hive] class ClientWrapper
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/7929#issuecomment-127890665
do feel free to get the comment thing hashed out with @srowen. My time zone
is approaching bed time, so I have to sign off. Would be nice to get something
1 - 100 of 4362 matches
Mail list logo
