Jarvis SDK by Fashiondata.io
Changelog
Release 1.1.9 : 2021-02-17
- Bugfix : added some extra checking for one-task TTT with dependencies specified.
Release 1.1.8 : 2021-02-16
- Added --context flag to specify which context to use.
- Added --no-launch flag to skip the DAG launch question asked to the user.
Release 1.1.7 : 2021-02-03
- All configuration types : the flag direct_execution is added and to true automatically if not present.
- All configuration type : added context management.
- TTT : added enhanced SQL parameters management.
- TTT : added GBQ Script support.
- TTT : added "use_query_cache" flag for "sql" task type.
- TTT : added "temporary_table" flag for "sql" task type.
- TTT : added enhanced information context for "sql" task type.
- Global : bugfix
Release 1.1.6 : 2020-11-24
- TTT : fixed an issue linked to partitioned table creation for direct execution mode.
- TTT : fixed "--sql-execution-date" parameter usage.
- Minor fixes
Release 1.1.5 : 2020-11-04
- TTT : the DAG can be deployed in direct execution mode.
- TTT : the user is asked if he wants to execute teh DAG upon successful upload.
- TTT : the user is not asked for the project profile. The configuration attribute "default_gcp_project_id" is used automatically.
- Updated "setup.py"
- Added file encoding verification upon reading. Everything will be converted to UTF-8
- Added specific Google Drive scope to generated DAG to allow Google Sheet as GBQ source
- When a "workflow" type configuration is uploaded, the latest workflow status (if it exists) is deleted.
- The used is asked if he wants to deploy associated cloud functions upon STS and STT deployment.
- STT : DDL infos can be processed using different methods
Release 1.1.4 : 2020-07-03
- Added Notification upon Jarvis SDK new release on PyPi
- TTT : added "client_type" and "client_version" to the stored configuration
Release 1.1.3 : 2020-06-18
- TTT : fixed another regression on function call.
Release 1.1.2 : 2020-06-18
- TTT : fixed a regression impacting SQL type tasks.
Release 1.1.1 : 2020-05-18
- Added support for ZSH under Max OS X
- TTT : Added task status
- TTT : added special check for tasks declared in "task_dependencies" but not in "workflow"
- TTT : check if task IDs are named properly
- TTT : You can run tasks locally with : jarvis configuration run YOUR-CONF.json [task1 task2 .... taskN]
- Project Profiles list is now sorted
Release 1.1.0 : 2020-02-19
- Added TTT DAG file checking upon deployment. The user must validate if he wants to overwrite TTT DAG.
- Removed Project selection validation.
Release 1.0.1 : 2020-02-10
- Fixed seek() error on file read
Release 0.0.16 : 2020-01-10
- Removed ASCII art
- Storage-to-tables : check for JSON syntax for DDL files as well
Release 0.0.15 : 2019-xx-xx
- Table-To-Table : GBQ table schema will be preserved upon WRITE_TRUNCATE
- Minor fixes
Release 0.0.14 : 2019-11-26
- Table-To-Table : added nested RECORD fields support for Bigquery table creation.
Release 0.0.13 : 2019-11-15
- Storage-To-Tables : "jarvis create configuration" support
Release 0.0.12 : 2019-11-04
- Added Storage-To-Tables configuration support.
- Table To Table (gbq to gbq) : "create_gbq_table" tasks will now use an external DDL file to describe the table schema.
Release 0.0.11 : 2019-10-23
- Table To Table (gbq to gbq) configuration will now use "configuration_type" and "configuration_id".
- Table To Table (gbq to gbq) configuration DOES NOT need "dag_name" parameter anymore.
- Storage To Storage configuration accepts "gcp_project_id" in the "source" section if the "source_type" is "gcs".
Release 0.0.10 : 2019-09-20
- Added auto creation of ".bash_profile" for Max OS X
- Added password double check upon user creation
- Added SQL file path management for "table-to-storage" deploy command
- Added : jarvis create configuration CONFIGURATION_TYPE command
- Added : jarvis check configuration CONFIG.json command
- Added : project profiles management
Metadata
Release files for jarvis-sdk 1.1.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jarvis_sdk-1.1.9-py3-none-any.whl | Python 3 | none | any | Details for jarvis_sdk-1.1.9-py3-none-any.whl |
Release files / jarvis_sdk-1.1.9-py3-none-any.whl
| Download URL | jarvis_sdk-1.1.9-py3-none-any.whl |
|---|---|
| Size | 43.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f66a53bccab9d84619f794043f00cf85fc5a0723dd282d0132d36af0458f2d8
|
|
BLAKE2b-256 checksum How to use checksums |
b25c7a8f86d287cf6229a810b4b4ecb905571c7da1be2cadd34bac77a32df44c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/53.0.0 requests-toolbelt/0.9.1 tqdm/4.51.0 CPython/3.8.5
|
Security for jarvis-sdk 1.1.9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.