Feature/transfer new view spec branch#25
Merged
Conversation
…r builder, processor, database, models, and stats tracking.
…d platform are not None
…ocessing, and memory-optimized JSON serialization, introducing new configuration options and a build timeout.
…sing TermAccessionNumber
…safety and configuration management
…improved type safety and validation
…r improved readability and performance
…ataBatch, enhancing performance and memory efficiency
… a typo in the postCreateCommand grep pattern.
…CH_VCS_PRETEND_VERSION` from Dockerfile build commands.
…rror handling - Introduced ArcBuildData class for structured data handling during ARC building. - Enhanced Database class with validation methods to handle missing required columns and NULL values. - Updated InvestigationRow, StudyRow, AssayRow, PublicationRow, and ContactRow models to include spec_field for better metadata management. - Improved error logging for missing required columns and NULL values during database streaming. - Modified main entry point to accept command line arguments more flexibly. - Updated integration and unit tests to cover new validation logic and ensure robustness. - Refactored test cases to align with new model structures and validation rules.
…ust validation tests for required fields
…tion; update tests accordingly
…o use SQLAlchemy's select API.
… new validation tests
- Refactor environment files to include a new debug configuration.
- Change log level in the main config to DEBUG for better traceability.
- Modify SQL queries to use `literal_column("*")` for selecting all columns.
- Introduce validation tests to ensure correct handling of NULL values and spec overrides.
Contributor
There was a problem hiding this comment.
Code Review
This pull request refactors the sql_to_arc component to use SQLAlchemy, enabling multi-database support via connection strings and introducing a modular architecture with Pydantic-based data models. The update also improves the development environment with SOPS-based secret management and a more resilient database initialization workflow. Feedback was provided regarding the use of echo in the Docker Compose configuration, which could introduce unwanted newlines in the client key file.
…pdate README code block for better readability
…command syntax in docker-compose
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.
No description provided.