-
Notifications
You must be signed in to change notification settings - Fork 2
Feature/ndit 821 address ddb dc performance issues #35
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
Closed
stevenhsd
wants to merge
22
commits into
develop_v06
from
feature/ndit-821_address_ddb_dc_performance_issues
Closed
Feature/ndit 821 address ddb dc performance issues #35
stevenhsd
wants to merge
22
commits into
develop_v06
from
feature/ndit-821_address_ddb_dc_performance_issues
Conversation
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
…. Duckdb no long relies on pandas- use of pyarrow, multiprocessing and background thread batch writing to avoid memory pressure
…ed_file_path during file transformation
…ion_that_submitted_files_had_been_transferred_to_processed_file_path fix: deal with pathing assumption that file(s) had been moved to processed file location
…atches to increase tolerance to large files with large numbers of validation errors
…reporting to module name rather than legacy name
* feat: Added new option to check csv headers in duckdb csv readers * refactor: small changes to foundry pipeline and duckdb csv to fix header check * feat: Added new check to base reader for sense check of whether processing a text file - applied for all reads via read_to_entity_type * refactor: Address review comments
…ging_around_dve_processing_errors Bugfix/gr ndit 850 improve logging around dve processing errors
Release v0.5.2
…and error reports (#36) * style: Additional logging around file transformation, business rules and error reports * style: remove unnecessary f string * refactor: further logging details * refactor: tweaked some logging messages following review
|
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.



No description provided.