Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPARKNLP-1109 Adding Extractor to Sparknlp #14519

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

danilojsl
Copy link
Contributor

@danilojsl danilojsl commented Feb 6, 2025

Description

This PR introduces two new SparkNLP powered annotators: Extractor and Cleaner.

Extractor Annotator:
Enables seamless extraction of key information (e.g., dates, emails, IP addresses) from various data sources such as .eml files. This simplifies data parsing workflows by isolating relevant details automatically.

Cleaner Annotator:
Removes unnecessary or undesirable content from datasets, such as bullets, dashes, and non-ASCII characters, enhancing data consistency and readability.

These annotators are designed for scalable, high-performance data processing, leveraging Apache Spark to handle large datasets efficiently.

Motivation and Context

In many real-world NLP tasks, raw data often contains noise, such as irrelevant symbols, inconsistent formatting, or extraneous details. Similarly, extracting structured information from unstructured data sources can be complex and inefficient without dedicated tools. These new annotators aim to solve these challenges by providing built-in, scalable capabilities for data preprocessing, reducing manual effort and boilerplate code while improving pipeline performance and accuracy.

How Has This Been Tested?

Screenshots (if appropriate):

  • Local test
  • Google colab notebooks

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Code improvements with no or little impact
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING page.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@danilojsl danilojsl self-assigned this Feb 6, 2025
@danilojsl danilojsl added new-feature Introducing a new feature DON'T MERGE Do not merge this PR labels Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DON'T MERGE Do not merge this PR new-feature Introducing a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant