rename span processor

[codeboten]

Description

Renamed BatchExportSpanProcessor to BatchSpanProcessor and SimpleExportSpanProcessor to
SimpleSpanProcessor

Fixes #1634

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Does This PR Require a Contrib Repo Change?

Answer the following question based on these examples of changes that would require a Contrib Repo Change:

• The OTel specification has changed which prompted this PR to update the method interfaces of opentelemetry-api/ or opentelemetry-sdk/

• The method interfaces of opentelemetry-instrumentation/ have changed

• The method interfaces of test/util have changed

• Scripts in scripts/ that were copied over to the Contrib repo have changed

• Configuration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in

  • pyproject.toml
  • isort.cfg
  • .flake8

• When a new .github/CODEOWNER is added

• Major changes to project information, such as in:

  • README.md
  • CONTRIBUTING.md

• Yes. - Link to PR:

• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been updated
• Documentation has been updated

[owais]

Contrib doesn't require any code changes but mentions the processor in docs in a couple of places so you might want to update that as well. https://github.com/open-telemetry/opentelemetry-python-contrib/search?q=BatchExportSpanProcessor

[owais]

Actually it also uses SimpleExportSpanProcessor in a couple of tests. https://github.com/open-telemetry/opentelemetry-python-contrib/search?q=SimpleExportSpanProcessor

Not sure why it didn't fail a contrib build.

[lzchen]

I am also curious at how this did not break instrumentation tests.

[codeboten]

I am also curious at how this did not break instrumentation tests.

I guess it didn't since the docker-tests failed. Will fix shortly