generated from amazon-archives/__template_MIT-0
-
Notifications
You must be signed in to change notification settings - Fork 33
Optional Classification and Extraction Steps #63
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
Open
HatmanStack
wants to merge
16
commits into
aws-solutions-library-samples:main
Choose a base branch
from
HatmanStack:feature/optional-classification-extraction
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
a24400e
Corrected git | branch created from exsisting feature branch
7575f07
Moved gating logic from patterns to services
4fcb327
Decoupled Services from Main Processing Flow | OCR | CLASSIFICATION |…
1d09259
Surfacing errors to Processing Flow Ui for Extraction Step
ef94dab
Decoupled Assessment
0d74b98
Merge remote-tracking branch 'upstream/develop' into feature/optional…
2e91f28
reverted to original Flow with simple flag check
41a4dad
Decoupled Services from Main Processing Flow | OCR | CLASSIFICATION |…
f20862a
Surfacing errors to Processing Flow Ui for Extraction Step
f3bd5cb
Decoupled Assessment
37ceba3
reverted to original Flow with simple flag check
c1281a1
request changes made
4982fbb
removed interactive rebase leftovers
22ace72
added in configs
1b2ffc1
Removed excess Error collection in Summ Func | Updated docs | correct…
9238d97
Merge branch 'main' into feature/optional-classification-extraction
HatmanStack File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid I am confused now by the scope of this PR, including the introduction of this 'tuning' concept. I had thought this would be a simple PR, a quick win, to introduce only an 'enable' property for classification and extraction, with the simple logic in the associated lambdas to skip the associated processing if enabled is False. (Like we have already for Summarization).
And so I am confused by why this would require introduction of new stack deployment parameters and these .tuning properties.