#1558 - Add a LLM-based TextExtractor (OpenAI API compatible) #1559
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for contributing to Apache StormCrawler.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes
Is there a issue associated with this PR? Is it referenced in the commit message?
Does your PR title start with
#XXXX
whereXXXX
is the issue number you are trying to resolve?Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
Is the code properly formatted with
mvn git-code-format:format-code -Dgcf.globPattern="**/*" -Dskip.format.code=false
?For code changes
mvn clean verify
?Note
This PR introduces a new TextExtractor implementation — OpenAITextExtractor — which utilizes a Large Language Model (LLM) via an OpenAI-compatible API to extract meaningful content from HTML documents. This allows for semantically rich, context-aware extraction far beyond traditional rule-based methods. Traditional extraction using static rules is brittle and struggles with modern, dynamic layouts. Leveraging LLMs like GPT-4 or LLaMA 3 enables understanding of HTML semantics, resulting in improved text extraction quality.
Key Features are:
Breaking Change (Potential)
This change renames the previously default TextExtractor class and introduces a new TextExtractor interface, making the implementation pluggable. While this may be considered a breaking change, the existing implementation was used privately and not designed for public extensibility. Therefore, in practice, it should be safe — but feedback is welcome.