Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/1254#issuecomment-49602573
Adding the Drop function to a contrib library of functions (which requires
manual import) , as erik suggests, seems like a really good option. I could
see such a
GitHub user jayunit100 opened a pull request:
https://github.com/apache/spark/pull/2964
SPARK-4040. Update documentation to exemplify use of local (n) value, fo...
This is a minor docs update which helps to clarify the way local[n] is used
for streaming apps.
You can merge this
Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/2964#issuecomment-61104470
(bump) - any thoughts on this ? I'd also like role some more improvements
into it in a follow up..
---
If your project is set up for it, you can reply to
Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/2964#issuecomment-61191921
Hi sean . I like that idea of running with 2 threads , and making it
explicit : Thats the main purpose of the PR i'll update that, and then
rebase th
Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/2964#issuecomment-61193334
okay ! updated .After this i think we can look into some deeper
updates into the streaming docs as well.
---
If your project is set up for it, you can reply to
Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/2964#issuecomment-61434987
@mateiz @srowen okay, updated w/ the threads vs workers disambiguation...
thanks for the feedback, just ping if any other updates are necessary.!
---
If your
Github user jayunit100 commented on the pull request:
https://github.com/apache/spark/pull/2964#issuecomment-61704211
(bump) all set on this guy ? or shall we wait till after the upcoming
spark release?
---
If your project is set up for it, you can reply to this email and have your
GitHub user jayunit100 opened a pull request:
https://github.com/apache/spark/pull/14347
Update Ivy artifacts statement for dev/audit
## What changes were proposed in this pull request?
Updating the readme regarding ivy artifacts for dev/audit
## How was this patch
Github user jayunit100 commented on the issue:
https://github.com/apache/spark/pull/14347
Fixes https://github.com/apache/spark/pull/14347
---
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 jayunit100 commented on the issue:
https://github.com/apache/spark/pull/14347
Hmmm... Ok, so What are we replacing audit tests with?
---
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
10 matches
Mail list logo
