Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18721
**[Test build #79899 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79899/testReport)**
for PR 18721 at commit
Github user LantaoJin commented on the issue:
https://github.com/apache/spark/pull/17953
@HyukjinKwon Sure. Thank you for reminding me. I almost forgot it.
---
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 kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/18719#discussion_r128953394
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetCacheSuite.scala ---
@@ -25,6 +25,11 @@ import org.apache.spark.storage.StorageLevel
class
GitHub user kiszk opened a pull request:
https://github.com/apache/spark/pull/18721
[SPARK-21516][SQL][Test] Overriding afterEach() in DatasetCacheSuite must
call super.afterEach()
## What changes were proposed in this pull request?
This PR ensures to call
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18711
**[Test build #79898 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79898/testReport)**
for PR 18711 at commit
Github user 10110346 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18711#discussion_r128952895
--- Diff: docs/configuration.md ---
@@ -1106,7 +1106,7 @@ Apart from these, the following properties are also
available, and may be useful
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/18684
@srowen any further comment?
---
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 debugger87 commented on the issue:
https://github.com/apache/spark/pull/18649
@cloud-fan @srowen If we can't find maintainer of hive-thriftserver in
Spark, I may have to close this PR in few days later.
---
If your project is set up for it, you can reply to this email
Github user devaraj-kavali commented on the issue:
https://github.com/apache/spark/pull/18708
Thanks @HyukjinKwon for checking this and for the link.
> Are you saying "file:///C:/Users//.ivy2/jars/.jar" is not the correct
form of URI on Windows?
This URI form is
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18664
In my opinion, we should definitely specify the timezone to keep the
correct timestamp.
I'm not sure which is the suitable one yet, but the candidates would be:
1. `"UTC"`
Spark SQL
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18711
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18711
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79895/
Test PASSed.
---
Github user yssharma commented on the issue:
https://github.com/apache/spark/pull/18071
I noticed that now. Yes I will post an updated patch today. Thanks
@HyukjinKwon
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18711
**[Test build #79895 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79895/testReport)**
for PR 18711 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18709
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18709
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79896/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18709
**[Test build #79896 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79896/testReport)**
for PR 18709 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18687
This really depends on how you implement the global statement cache and
management. All the compiled plans can be stored in the cache. The plans can be
reused, if possible (the reused plans
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18612
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18612
**[Test build #79897 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79897/testReport)**
for PR 18612 at commit
Github user liyichao commented on the issue:
https://github.com/apache/spark/pull/18093
Sorry about that, I will test it when I have time.
---
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 AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18612
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79897/
Test PASSed.
---
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18540#discussion_r128947347
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/windowExpressions.scala
---
@@ -106,173 +101,167 @@ case class
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18071
It looks the last test was failed by style checking. Would you have some
time to fix them up?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user yssharma commented on the issue:
https://github.com/apache/spark/pull/18071
@HyukjinKwon The PR is ready. Just waiting for some ð from the reviewers.
---
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 maropu commented on the issue:
https://github.com/apache/spark/pull/18250
I think we could be back if we have better way to handle this, so I'll
close this for now (we better keeping this discussion in jira).
---
If your project is set up for it, you can reply to this
Github user maropu closed the pull request at:
https://github.com/apache/spark/pull/18250
---
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 jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18711#discussion_r128945012
--- Diff: docs/configuration.md ---
@@ -1106,7 +1106,7 @@ Apart from these, the following properties are also
available, and may be useful
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18711#discussion_r128945886
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -580,7 +580,8 @@ private[deploy] class Master(
* The number of
Github user jiangxb1987 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18711#discussion_r128943527
--- Diff: core/src/main/scala/org/apache/spark/deploy/master/Master.scala
---
@@ -580,7 +580,8 @@ private[deploy] class Master(
* The number of
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/13320
No, so I'll close this for now and we move this discussion to jira.
---
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 maropu closed the pull request at:
https://github.com/apache/spark/pull/13320
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17882
Thank you @jerryshao.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18154
I don't know ML as much as reviewing this. I just wanted to be sure if it
is in progress in any way.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16577
@aray WDYT on ^?
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16445
Hi @yaooqinn, is this PR active? if so, would you address or answer to the
review comments above?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18093
I think a patch should at least be manually tested @liyichao.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18071
Hi @yssharma, is it still WIP? I think we should make the PR on the
mergable state at least.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/17882
I think this could be closed, @vanzin already created a new PR based on
this (#18663).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18127
Hi @weiqingy, I just wonder if it is in progress in any way.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/13706
@gatorsmile, I just wonder if it is ready to proceed further this PR. It
looks the PR you linked is merged properly.
---
If your project is set up for it, you can reply to this email and have
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17371
gentle ping @uncleGen, is this PR still active?
---
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 agsachin commented on the issue:
https://github.com/apache/spark/pull/14601
Thanks @jiangxb2987 will add this test case by tomorrow and will be update
the pr with results
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user zhengruifeng commented on the issue:
https://github.com/apache/spark/pull/18154
@hhbyyh @HyukjinKwon Sorry to reply late.
I think it may be better to use a special logic if it is more efficient in
performance.
What is your opinion? @yanboliang @HyukjinKwon
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18242
ping @arsinux
---
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,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17953
@LantaoJin do you have some time to address the review comment above?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17979
@yanji84, is this PR active? if so, would you answer to the question above?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17180
Hi @zhzhan is this PR active? if so, would you answer or address the review
comment?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/13320
@maropu, I just wonder if it is in progress in any way.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16365
ping @bravo-zhang for adding the 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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18154
@zhengruifeng Would you answer or address the review comments above?
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18717#discussion_r128944222
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -2739,6 +2752,26 @@ class Dataset[T] private[sql](
}
/**
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/12147
Gentle ping @xwu0226, how is the update going?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17882
gentle ping @witgo for review comments above.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18612
**[Test build #79897 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79897/testReport)**
for PR 18612 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/11205
gentle ping @rustagi
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16766
Hi @mariusvniekerk, would you be able to fix the javadoc errors?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14239
Is it @f7753 ?
---
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,
Github user nblintao commented on the issue:
https://github.com/apache/spark/pull/14158
@HyukjinKwon It's still active. I'll fix it when I'm available. Thanks.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14085
@zenglinxi0615 Could you answer to the question above if you are active?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18328
@dosoft Is this PR active? then would you mind if I ask to reply to the
review comment above?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18717#discussion_r128943409
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/Dataset.scala ---
@@ -2739,6 +2752,26 @@ class Dataset[T] private[sql](
}
/**
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17530
gentle ping @themodernlife on ^.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/11494
gentle ping @yzotov.
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14158
gentle ping @nblintao, is this PR active? If so, I guess the test failure
should be fixed if related.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user djvulee commented on a diff in the pull request:
https://github.com/apache/spark/pull/18651#discussion_r128943316
--- Diff:
resource-managers/yarn/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocator.scala
---
@@ -525,9 +534,11 @@ private[yarn] class
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15227
gentle ping @yaooqinn on ^.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18269
gentle ping @bbossy, I just want to be sure if it is in progress in any way.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/14601
gentle ping @agsachin.
---
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
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18711
yea, I understand the issue now. Thank you for clarify!
---
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 viirya commented on a diff in the pull request:
https://github.com/apache/spark/pull/18717#discussion_r128942266
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetCacheSuite.scala ---
@@ -25,9 +25,22 @@ import org.apache.spark.storage.StorageLevel
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18250
ok, thanks!
---
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
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17519
Hi @lins05, is this PR active?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18354
@bdrillard, sounds properly backported. Would you close 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 project
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18687
cc @cloud-fan Can you help review this too? Thanks.
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18383
gentle ping @dijingran. I want to be sure if it is in progress in any way.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18250
I am sorry @maropu. I can't think of a good way to handle this for now ...
Will be back after thinking more maybe ..
---
If your project is set up for it, you can reply to this email and have
Github user yaooqinn commented on the issue:
https://github.com/apache/spark/pull/18668
ping @cloud-fan
---
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,
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18687
> So far, we do not support dynamic SQL statement, but this is a potential
feature we can explore in the future. A global statement cache and management
can reduce the optimization costs, especially
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17096
gentle ping ...
---
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,
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/16611
gentle ping ...
---
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,
Github user maropu commented on the issue:
https://github.com/apache/spark/pull/18592
@gatorsmile Could we merge this first? I feel we could discuss more on jira?
---
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 HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18304
Would you mind if I ask to wait the resolution of
`https://github.com/apache/spark/pull/18581` ? Strictly, they are orthogonal as
that PR tries to not change the default line separator but I
Github user 10110346 commented on the issue:
https://github.com/apache/spark/pull/18711
If the other application is finished, it will release cores
---
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 jinxing64 commented on the issue:
https://github.com/apache/spark/pull/18713
cc @cloud-fan @jiangxb1987
---
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
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18711
How can we wait for new free cores on the same worker, if we only start one
executor for each worker initially?
---
If your project is set up for it, you can reply to this email and have your
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/18687
So far, we do not support dynamic SQL statement, but this is a potential
feature we can explore in the future. A global statement cache and management
can reduce the optimization costs,
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18719
good catch, i will create a follow-up PR today.
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/18709
**[Test build #79896 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79896/testReport)**
for PR 18709 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18711
**[Test build #79895 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79895/testReport)**
for PR 18711 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/18719#discussion_r128937203
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/DatasetCacheSuite.scala ---
@@ -25,6 +25,11 @@ import org.apache.spark.storage.StorageLevel
Github user 10110346 commented on the issue:
https://github.com/apache/spark/pull/18711
@jiangxb1987 If `app.coresLeft` is not zero and there is no more free
cores left, it is not ending.Waiting for some workers have free cores, this
app will be assigned cores continue, and this
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/18687
Do we have dynamic SQL statements?
---
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 ericl commented on the issue:
https://github.com/apache/spark/pull/18714
Got it.
On Sun, Jul 23, 2017, 10:40 PM Wenchen Fan wrote:
> *@cloud-fan* commented on this pull request.
> --
>
> In
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18717
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18717
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79894/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18717
**[Test build #79894 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79894/testReport)**
for PR 18717 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18709
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18709
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79893/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18709
**[Test build #79893 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/79893/testReport)**
for PR 18709 at commit
1 - 100 of 245 matches
Mail list logo