OPENNLP-855: SentimentAnalysisParser deriving sentiment from text#579
Draft
OPENNLP-855: SentimentAnalysisParser deriving sentiment from text#579
Conversation
Contributor
Author
|
FYI @amensiko - I just rebased the branch on OPENNLP-855 from 2017. Could drop your comment on its state, pls? |
Contributor
Author
|
Note: Tests required. |
b9f82fb to
a0526b4
Compare
a0526b4 to
3616cb7
Compare
3616cb7 to
dc57749
Compare
dc57749 to
e46c576
Compare
e46c576 to
f70c874
Compare
f70c874 to
eddcb8a
Compare
eddcb8a to
28c78a4
Compare
28c78a4 to
17ea957
Compare
- adapts existing Sentiment code to OpenNLP 3.x module structures - introduces SentimentDetector API interface
17ea957 to
1529f53
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Tasks
Thank you for contributing to Apache OpenNLP.
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 JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with OPENNLP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions for build issues and submit an update to your PR as soon as possible.