Skip to content

Conversation

@rxin
Copy link
Contributor

@rxin rxin commented May 2, 2016

What changes were proposed in this pull request?

This patch deprecates the old accumulator API.

How was this patch tested?

N/A

@rxin
Copy link
Contributor Author

rxin commented May 2, 2016

cc @cloud-fan

@SparkQA
Copy link

SparkQA commented May 2, 2016

Test build #57502 has finished for PR 12832 at commit ab7840f.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@andrewor14
Copy link
Contributor

LGTM

asfgit pushed a commit that referenced this pull request May 2, 2016
## What changes were proposed in this pull request?
This patch deprecates the old accumulator API.

## How was this patch tested?
N/A

Author: Reynold Xin <rxin@databricks.com>

Closes #12832 from rxin/SPARK-15054.

(cherry picked from commit d5c79f5)
Signed-off-by: Reynold Xin <rxin@databricks.com>
@asfgit asfgit closed this in d5c79f5 May 2, 2016
* @tparam R the full accumulated data (result type)
* @tparam T partial data that can be added in
*/
@deprecated("use AccumulatorV2", "2.0.0")
Copy link
Member

Choose a reason for hiding this comment

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

@rxin PS I think the JavaSparkContext needs similar treatment? methods like intAccumulator return the old API object.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yup we need to tweak the scala api a little bit. We can deprecate and create the Java APIs once the Scala done is finalized. I have a ticket for that.

Copy link
Member

Choose a reason for hiding this comment

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

OK, I'm making another PR to try to fix build warnings. Deprecating these methods actually makes many warnings go away (since deprecated methods calling deprecated methods is OK). Is that much OK to do or don't touch it for now? these methods are going to stay but be deprecated in any event right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Wait for one more week?

Copy link
Member

Choose a reason for hiding this comment

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

NP I'm not in a hurry. Just want to do one more cleanup of build warnings before 2.0.

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