Skip to content

Conversation

@sarutak
Copy link
Member

@sarutak sarutak commented Aug 7, 2014

No description provided.

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing this seems somewhat brittle... what if we want to change the behavior on the receiving end? These results are very small, I don't see a big problem with sending them.

@pwendell
Copy link
Contributor

pwendell commented Aug 9, 2014

I took a quick look - I'm not sure we want to change this. Just because only the first result is used right now doesn't mean we won't want to do something more sophisticated in the future. And donwstream consumers of code could make the assumption that all failed fetches will be present.

@sarutak
Copy link
Member Author

sarutak commented Aug 9, 2014

Thanks for looking this ,@pwendell .
This change is also for consistency. In #1578, I discussed whether all of failures should be set to results or not with @mateiz and I decided to set only first failure for fast fail.

@rxin
Copy link
Contributor

rxin commented Sep 10, 2014

Do you mind closing this? This whole code is going to be updated by #2330

@sarutak sarutak closed this Sep 10, 2014
@sarutak sarutak deleted the SPARK-2896 branch April 11, 2015 05:22
viirya pushed a commit to viirya/spark-1 that referenced this pull request Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants