Github user squito commented on the issue:
https://github.com/apache/spark/pull/15237
merged to master, thanks @erenavsarogullari
---
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 erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Hi @squito,
Sorry, i am quite busy this week and happy to be merged this PR now if it
is also ok for you. I plan to address fileName logging via separated jira.
Also To in
Github user squito commented on the issue:
https://github.com/apache/spark/pull/15237
@erenavsarogullari sorry to push back, but if you're willing to do the
filename thing now, why not just tackle it in this same pr? seems pretty minor
to separate into its own issue, and conceptually
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72169/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72169 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72169/testReport)**
for PR 15237 at commit
[`7551cbd`](https://github.com/apache/spark/commit/7
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Hi @squito,
Firstly, thanks again for the review.
Sure, scheduler filename can be gotten via `buildPools` function by
creating a tuple / case class as `(Option[InputStream], fi
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72169 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72169/testReport)**
for PR 15237 at commit
[`7551cbd`](https://github.com/apache/spark/commit/75
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72005/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72005 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72005/testReport)**
for PR 15237 at commit
[`a1b2924`](https://github.com/apache/spark/commit/a
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72004/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72004 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72004/testReport)**
for PR 15237 at commit
[`d5597c3`](https://github.com/apache/spark/commit/d
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Hi @squito,
Firstly, sorry for delay and thanks for review again.
All comments are addressed via new patch(a1b2924) and it is ready to
re-review / merge ;)
---
If your project is
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72005 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72005/testReport)**
for PR 15237 at commit
[`a1b2924`](https://github.com/apache/spark/commit/a1
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #72004 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72004/testReport)**
for PR 15237 at commit
[`d5597c3`](https://github.com/apache/spark/commit/d5
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70571/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #70571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70571/testReport)**
for PR 15237 at commit
[`a4e06b2`](https://github.com/apache/spark/commit/a
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Hi @squito,
Many thanks again for review. All comments have just been addressed via new
commit.
Also It is ready to rereview / merge ;)
---
If your project is set up for it, you c
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #70571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70571/testReport)**
for PR 15237 at commit
[`a4e06b2`](https://github.com/apache/spark/commit/a4
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
Many thanks @squito for review.
I will address them asap ;)
---
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 proj
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69506/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #69506 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69506/consoleFull)**
for PR 15237 at commit
[`4b6053f`](https://github.com/apache/spark/commit/
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15237
**[Test build #69506 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69506/consoleFull)**
for PR 15237 at commit
[`4b6053f`](https://github.com/apache/spark/commit/4
Github user squito commented on the issue:
https://github.com/apache/spark/pull/15237
Jenkins, ok to 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
enabled and wishes so, o
Github user erenavsarogullari commented on the issue:
https://github.com/apache/spark/pull/15237
cc @kayousterhout @markhamstra @squito
Thanks and all feedbacks are welcome in advance ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15237
Can one of the admins verify this patch?
---
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 feat
30 matches
Mail list logo
