Tulona
======
A utility to compare tables, espacially useful to perform validations for migration projects.
.. list-table::
:widths: 50 200
* - Testing
- |CI Test| |Deployment| |Coverage|
* - Package
- |PyPI Latest Release| |PyPI Downloads|
* - Meta
- |License Apache-2.0| |Codestyle Black|
Functionality
-------------
The basic functionality of `tulona` is to compare datasets, write them into Excel files and highlight the mismatches.
Connection Profiles
-------------------
Connection profiles is a `yaml` file that will store credentials and other details to connect to the databases/data sources.
It must be setup in `profiles.yml` file and it must be placed under `$HOME/.tulona` dierctory.
Create a directory named `.tulona` under your home directory and place `profiles.yml` under it.
This is what a sample `profiles.yml` looks like:
.. code-block:: yaml
integration_project: # project_name
profiles:
pgdb:
type: postgres
host: localhost
port: 5432
database: postgres
username: postgres
password: postgres
mydb:
type: mysql
host: localhost
port: 3306
database: db
username: user
password: password
snowflake:
type: snowflake
account: snowflake_account
warehouse: dev_x_small
role: dev_role
database: dev_stage
schema: user_schema
user: dev_user
private_key: 'rsa_key.p8'
private_key_passphrase: 444444
mssql:
type: mssql
connection_string: 'DRIVER={ODBC Driver 18 for SQL Server};SERVER=dagger;DATABASE=test;UID=user;PWD=password'
bigquery:
type: bigquery
method: service_account
project: training-338516
key_file: "/path/to/service_account/training-338516-362fa3727bae.json"
Project Config File
-------------------
Project config file stores the properties of the tables that need to be compared.
It must be created in `tulona-project.yml` file and this file can be placed anywhere and that directory will be considered project root directory.
Which means that the `output`` folder will be created under that directory where all results will be stored.
It's always a good idea to create an empty directory and store `tulona-project.yml` under it.
This is how a `tulona-project.yml` file looks like:
.. code-block:: yaml
version: '2.0'
name: integration_project
config_version: 1
outdir: output # optional
# Datasource names must be unique
datasources:
employee_postgres:
connection_profile: pgdb
database: postgresdb
schema: corporate
table: employee
primary_key: Employee_ID
exclude_columns:
- Email
- Name
compare_column: Employee_ID
employee_mysql:
connection_profile: mydb
schema: corporate
table: employee
primary_key: Employee_ID
exclude_columns:
- Phone_Number
compare_column: Employee_ID
person_postgres:
connection_profile: pgdb
database: postgresdb
schema: corporate
table: people_composite_key
primary_key:
- ID_1
- ID_2
# exclude_columns:
# - name
compare_column:
- ID_1
- ID_2
person_mysql:
connection_profile: mydb
schema: corporate
table: people_composite_key
primary_key:
- ID_1
- ID_2
# exclude_columns:
# - phone_number
compare_column:
- ID_1
- ID_2
postgresdb_postgres:
connection_profile: pgdb
database: postgresdb
none_mysql:
connection_profile: mydb
postgresdb_postgres_schema:
connection_profile: pgdb
database: postgresdb
schema: corporate_copy
none_mysql_schema:
connection_profile: mydb
schema: corporate
employee_postgres_query:
connection_profile: pgdb
database: postgresdb
schema: corporate
query: select * from postgresdb.corporate.employee
primary_key: Employee_ID
exclude_columns:
- name
compare_column: Employee_ID
employee_mysql_query:
connection_profile: mydb
schema: corporate
query: select * from corporate.employee
primary_key: Employee_ID
exclude_columns:
- phone_number
compare_column: Employee_ID
employee_postgres_query_tab:
connection_profile: pgdb
database: postgresdb
schema: corporate
table: employee
query: select * from postgresdb.corporate.employee
primary_key: Employee_ID
exclude_columns:
- name
compare_column: Employee_ID
employee_mysql_query_tab:
connection_profile: mydb
schema: corporate
table: employee
query: select * from corporate.employee
primary_key: Employee_ID
exclude_columns:
- phone_number
compare_column: Employee_ID
cust_bq:
connection_profile: bigquery
project: training-338516
dataset: dummy_fashion_retail
table: customers
primary_key: customer_id
compare_column:
- customer_id
cust_snow:
connection_profile: snowflake
database: training
schema: dummy_fashion_retail
table: customers
primary_key: customer_id
compare_column:
- customer_id
# List of task configs(Dict)
# Depending on the accepted params, task config can have different params
# The value for that `task` key is the name of the command you want to run
task_config:
- task: ping
datasources:
- person_postgres
- none_mysql
- employee_mysql_query
- task: profile
datasources:
- employee_postgres
- employee_mysql
compare: true
- task: profile
datasources:
- person_postgres
- person_mysql
- task: compare-row
datasources:
- employee_postgres
- employee_mysql
sample_count: 30
- task: compare-row
datasources:
- employee_postgres
- employee_mysql
- task: compare-row
datasources:
- employee_postgres_query
- employee_mysql_query
- task: compare-column
datasources:
- employee_postgres
- employee_mysql
- task: compare-column
datasources:
- person_postgres
- person_mysql
composite: false # If it's false, specifying it is optional
- task: compare-column
datasources:
- person_postgres
- person_mysql
composite: true
- task: compare
datasources:
- employee_postgres
- employee_mysql
composite: true
- task: compare
datasources:
- person_postgres
- person_mysql
composite: true
sample_count: 30
- task: scan
datasources:
- postgresdb_postgres_schema
- task: scan
datasources:
- postgresdb_postgres
- none_mysql
compare: false
- task: scan
datasources:
- postgresdb_postgres_schema
- none_mysql_schema
compare: true
- task: scan
datasources:
- postgresdb_postgres
- none_mysql
compare: true
- task: compare
datasources:
- employee_postgres_query_tab
- employee_mysql_query_tab
- task: compare
datasources:
- cust_bq
- cust_snow
Features
--------
Executing `tulona` or `tulona -h` or `tulona --help` returns available commands.
If you don't setup `task_config`, all commands take one mandatory parameter, `--datasources`, a comma separated list of names of datasources from project config file (`tulona-project.yml`).
Tulona has following commands available:
* **ping**: To test connectivity to the databases for the datasources. Sample command:
* To ping one data source pass the name to the `--datasources` parameter:
``tulona ping --datasources employee_postgres``
* More than one datasources can be passed to the `--datasources` parameter separated by commas:
``tulona ping --datasources employee_postgres,employee_mysql``
* To ping all the datasources, just skip the `--datasources` parameter:
``tulona ping``
* **profile**: To extract and compare metadata of two sources/tables. It includes metadata from `information_schema` related to the tables and some column level metrics (min, max, average, count & distinct_count). Note that specifying `database`, `schema` and `table` is required for `profile` to work regardless the use of `query`. Sample commands:
* Profiling without `--compare` flag. It will write metadata and metrics about different sources/tables in different sheets/tabs in the excel file (not a comparison view):
``tulona profile --datasources employee_postgres,employee_mysql``
* Profiling with `--compare` flag. It will produce a comparison view (side by side):
``tulona profile --compare --datasources employee_postgres,employee_mysql``
* Sample output will be something like this:
|profile|
* **compare-row**: To compare sample data from two sources/tables/queries. It will create a comparative view of all common columns from both sources/tables side by side (like: id_ds1 <-> id_ds2) and highlight mismatched values in the output excel file. By default it compares 20 common rows from both tables (subject to availabillity) but the number can be overridden with the command line argument `--sample-count`. Command samples:
* Command without `--sample-count` parameter:
``tulona compare-row --datasources employee_postgres,employee_mysql``
* Command with `--sample-count` parameter:
``tulona compare-row --sample-count 50 --datasources employee_postgres,employee_mysql``
* Compare queries instead of tables, useful when you want to compare resutls of two queries:
``tulona compare-row --datasources employee_postgres_query,employee_mysql_query``
* Sample output will be something like this:
|compare_row|
* **compare-column**: To compare columns from tables from two sources/tables. This is expecially useful when you want see if all the rows from one table/source is present in the other one by comparing the primary/unique key. The result will be an excel file with extra primary/unique keys from both sides. If both have the same set of primary/unique keys, essentially means they have the same rows, excel file will be empty. Command samples:
* Column[s] to compare is[are] specified in `tulona-project.yml` file as part of datasource configs, with `compare_column` property. Sample command:
``tulona compare-column --datasources employee_postgres,employee_mysql``
* Compare multiples columns as composite key (combination of column values will be compared) with additional `--composite` flag:
``tulona compare-column --composite --datasources employee_postgres,employee_mysql``
* Sample output will be something like this:
|compare_column|
* **compare**: To prepare a comparison report for evrything together. To executed this command just swap the command from any of the above commands with `compare`. It will prepare comparison of everything and write them into different sheets of a single excel file. Sample command:
``tulona compare --datasources employee_postgres,employee_mysql``
* **scan**: To scan and compare databases or schemas in terms of metadata and tables present if you want to compare all tables and don't want to set up datasource config for all of them. Sample commands:
* Scan without comparing:
``tulona scan --datasources postgresdb_postgres_schema,none_mysql_schema``
* Scan and compare:
``tulona scan --compare --datasources postgresdb_postgres_schema,none_mysql_schema``
* **run**: To execute all the tasks defined in the `task_config` section. Sample command:
``tulona run``
If you setup `task_config`, there is no need to pass the `--datasources` parameter.
In that case the following command (to compare some datasoruces):
``tulona compare --datasources employee_postgres,employee_mysql``
will become this:
``tulona compare``
and it will run all the `compare` tasks defined in the `task_config` section. From our example project config file above, it will run 2 `compare` tasks.
Also setting up `task_config` can be greatly benificial as you can set up different instance of same/different tasks with different config to execute in one go with the `run` command.
Please look at the sample project config from above to understand how to set up `task_config` property.
To know more about any specific command, execute `tulona <command> -h`.
Supported Data Platforms
------------------------
.. list-table::
:widths: 20 20 200
:header-rows: 1
* - Platform
- Adapter Name
- Supported Auth Mechanism
* - Postgres
- postgres
- Connection string, Password
* - MySQL
- mysql
- Connection string, Password
* - Snowflake
- snowflake
- Password, Key pair, SSO (Externalbrowser)
* - Microsoft SQL Server
- mssql
- Connection string
* - BigQuery
- bigquery
- Service Account Json Key
Development Environment Setup
-----------------------------
* For live installation execute `pip install -e ".[dev]"`.
Build Wheel Executable
----------------------
* Execute `python -m build`.
Install Wheel Executable File
-----------------------------
* Execute `pip install <wheel-file.whl>`
.. |profile| image:: images/profile.png
:alt: Profile output
.. |compare_row| image:: images/compare_row.png
:alt: Row comparison output
.. |compare_column| image:: images/compare_column.png
:alt: Column comparison output
.. |CI Test| image:: https://github.com/mrinalsardar/tulona/actions/workflows/test.yaml/badge.svg
:target: https://github.com/mrinalsardar/tulona/actions/workflows/test.yaml
.. |Deployment| image:: https://github.com/mrinalsardar/tulona/actions/workflows/publish.yaml/badge.svg
:target: https://github.com/mrinalsardar/tulona/actions/workflows/publish.yaml
.. |Coverage| image:: https://codecov.io/gh/mrinalsardar/tulona/graph/badge.svg?token=UGNjjgRskE
:target: https://codecov.io/gh/mrinalsardar/tulona
:alt: Coverage status
.. |PyPI Latest Release| image:: https://img.shields.io/pypi/v/tulona.svg
:target: https://pypi.python.org/pypi/tulona/
.. |PyPI Downloads| image:: https://img.shields.io/pypi/dm/tulona.svg?label=PyPI%20downloads
:target: https://pypi.org/project/tulona/
.. |License Apache-2.0| image:: https://img.shields.io/:license-Apache%202-brightgreen.svg
:target: http://www.apache.org/licenses/LICENSE-2.0.txt
.. |Codestyle Black| image:: https://img.shields.io/badge/code%20style-black-000000.svg
:target: https://github.com/psf/black
Raw data
{
"_id": null,
"home_page": null,
"name": "tulona",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "tulona, comparison, data comparison, database scan, database profile",
"author": "Mrinal Kanti Sardar",
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/59/c7/2bec423d946d947f60a4f249a4ae0fa32bf38ffa4a087f7e1ee8fa9253a6/tulona-0.11.0.tar.gz",
"platform": null,
"description": "Tulona\n======\nA utility to compare tables, espacially useful to perform validations for migration projects.\n\n.. list-table::\n :widths: 50 200\n\n * - Testing\n - |CI Test| |Deployment| |Coverage|\n * - Package\n - |PyPI Latest Release| |PyPI Downloads|\n * - Meta\n - |License Apache-2.0| |Codestyle Black|\n\nFunctionality\n-------------\nThe basic functionality of `tulona` is to compare datasets, write them into Excel files and highlight the mismatches.\n\n\nConnection Profiles\n-------------------\nConnection profiles is a `yaml` file that will store credentials and other details to connect to the databases/data sources.\n\nIt must be setup in `profiles.yml` file and it must be placed under `$HOME/.tulona` dierctory.\nCreate a directory named `.tulona` under your home directory and place `profiles.yml` under it.\n\nThis is what a sample `profiles.yml` looks like:\n\n.. code-block:: yaml\n\n integration_project: # project_name\n profiles:\n pgdb:\n type: postgres\n host: localhost\n port: 5432\n database: postgres\n username: postgres\n password: postgres\n mydb:\n type: mysql\n host: localhost\n port: 3306\n database: db\n username: user\n password: password\n snowflake:\n type: snowflake\n account: snowflake_account\n warehouse: dev_x_small\n role: dev_role\n database: dev_stage\n schema: user_schema\n user: dev_user\n private_key: 'rsa_key.p8'\n private_key_passphrase: 444444\n mssql:\n type: mssql\n connection_string: 'DRIVER={ODBC Driver 18 for SQL Server};SERVER=dagger;DATABASE=test;UID=user;PWD=password'\n bigquery:\n type: bigquery\n method: service_account\n project: training-338516\n key_file: \"/path/to/service_account/training-338516-362fa3727bae.json\"\n\n\nProject Config File\n-------------------\nProject config file stores the properties of the tables that need to be compared.\nIt must be created in `tulona-project.yml` file and this file can be placed anywhere and that directory will be considered project root directory.\nWhich means that the `output`` folder will be created under that directory where all results will be stored.\nIt's always a good idea to create an empty directory and store `tulona-project.yml` under it.\n\nThis is how a `tulona-project.yml` file looks like:\n\n.. code-block:: yaml\n\n version: '2.0'\n name: integration_project\n config_version: 1\n\n outdir: output # optional\n\n # Datasource names must be unique\n datasources:\n employee_postgres:\n connection_profile: pgdb\n database: postgresdb\n schema: corporate\n table: employee\n primary_key: Employee_ID\n exclude_columns:\n - Email\n - Name\n compare_column: Employee_ID\n employee_mysql:\n connection_profile: mydb\n schema: corporate\n table: employee\n primary_key: Employee_ID\n exclude_columns:\n - Phone_Number\n compare_column: Employee_ID\n person_postgres:\n connection_profile: pgdb\n database: postgresdb\n schema: corporate\n table: people_composite_key\n primary_key:\n - ID_1\n - ID_2\n # exclude_columns:\n # - name\n compare_column:\n - ID_1\n - ID_2\n person_mysql:\n connection_profile: mydb\n schema: corporate\n table: people_composite_key\n primary_key:\n - ID_1\n - ID_2\n # exclude_columns:\n # - phone_number\n compare_column:\n - ID_1\n - ID_2\n postgresdb_postgres:\n connection_profile: pgdb\n database: postgresdb\n none_mysql:\n connection_profile: mydb\n postgresdb_postgres_schema:\n connection_profile: pgdb\n database: postgresdb\n schema: corporate_copy\n none_mysql_schema:\n connection_profile: mydb\n schema: corporate\n employee_postgres_query:\n connection_profile: pgdb\n database: postgresdb\n schema: corporate\n query: select * from postgresdb.corporate.employee\n primary_key: Employee_ID\n exclude_columns:\n - name\n compare_column: Employee_ID\n employee_mysql_query:\n connection_profile: mydb\n schema: corporate\n query: select * from corporate.employee\n primary_key: Employee_ID\n exclude_columns:\n - phone_number\n compare_column: Employee_ID\n employee_postgres_query_tab:\n connection_profile: pgdb\n database: postgresdb\n schema: corporate\n table: employee\n query: select * from postgresdb.corporate.employee\n primary_key: Employee_ID\n exclude_columns:\n - name\n compare_column: Employee_ID\n employee_mysql_query_tab:\n connection_profile: mydb\n schema: corporate\n table: employee\n query: select * from corporate.employee\n primary_key: Employee_ID\n exclude_columns:\n - phone_number\n compare_column: Employee_ID\n cust_bq:\n connection_profile: bigquery\n project: training-338516\n dataset: dummy_fashion_retail\n table: customers\n primary_key: customer_id\n compare_column:\n - customer_id\n cust_snow:\n connection_profile: snowflake\n database: training\n schema: dummy_fashion_retail\n table: customers\n primary_key: customer_id\n compare_column:\n - customer_id\n\n\n # List of task configs(Dict)\n # Depending on the accepted params, task config can have different params\n # The value for that `task` key is the name of the command you want to run\n task_config:\n - task: ping\n datasources:\n - person_postgres\n - none_mysql\n - employee_mysql_query\n\n - task: profile\n datasources:\n - employee_postgres\n - employee_mysql\n compare: true\n\n - task: profile\n datasources:\n - person_postgres\n - person_mysql\n\n - task: compare-row\n datasources:\n - employee_postgres\n - employee_mysql\n sample_count: 30\n\n - task: compare-row\n datasources:\n - employee_postgres\n - employee_mysql\n\n - task: compare-row\n datasources:\n - employee_postgres_query\n - employee_mysql_query\n\n - task: compare-column\n datasources:\n - employee_postgres\n - employee_mysql\n\n - task: compare-column\n datasources:\n - person_postgres\n - person_mysql\n composite: false # If it's false, specifying it is optional\n\n - task: compare-column\n datasources:\n - person_postgres\n - person_mysql\n composite: true\n\n - task: compare\n datasources:\n - employee_postgres\n - employee_mysql\n composite: true\n\n - task: compare\n datasources:\n - person_postgres\n - person_mysql\n composite: true\n sample_count: 30\n\n - task: scan\n datasources:\n - postgresdb_postgres_schema\n\n - task: scan\n datasources:\n - postgresdb_postgres\n - none_mysql\n compare: false\n\n - task: scan\n datasources:\n - postgresdb_postgres_schema\n - none_mysql_schema\n compare: true\n\n - task: scan\n datasources:\n - postgresdb_postgres\n - none_mysql\n compare: true\n - task: compare\n datasources:\n - employee_postgres_query_tab\n - employee_mysql_query_tab\n - task: compare\n datasources:\n - cust_bq\n - cust_snow\n\n\nFeatures\n--------\nExecuting `tulona` or `tulona -h` or `tulona --help` returns available commands.\nIf you don't setup `task_config`, all commands take one mandatory parameter, `--datasources`, a comma separated list of names of datasources from project config file (`tulona-project.yml`).\n\nTulona has following commands available:\n\n* **ping**: To test connectivity to the databases for the datasources. Sample command:\n\n * To ping one data source pass the name to the `--datasources` parameter:\n\n ``tulona ping --datasources employee_postgres``\n\n * More than one datasources can be passed to the `--datasources` parameter separated by commas:\n\n ``tulona ping --datasources employee_postgres,employee_mysql``\n\n * To ping all the datasources, just skip the `--datasources` parameter:\n\n ``tulona ping``\n\n* **profile**: To extract and compare metadata of two sources/tables. It includes metadata from `information_schema` related to the tables and some column level metrics (min, max, average, count & distinct_count). Note that specifying `database`, `schema` and `table` is required for `profile` to work regardless the use of `query`. Sample commands:\n\n * Profiling without `--compare` flag. It will write metadata and metrics about different sources/tables in different sheets/tabs in the excel file (not a comparison view):\n\n ``tulona profile --datasources employee_postgres,employee_mysql``\n\n * Profiling with `--compare` flag. It will produce a comparison view (side by side):\n\n ``tulona profile --compare --datasources employee_postgres,employee_mysql``\n\n * Sample output will be something like this:\n\n |profile|\n\n* **compare-row**: To compare sample data from two sources/tables/queries. It will create a comparative view of all common columns from both sources/tables side by side (like: id_ds1 <-> id_ds2) and highlight mismatched values in the output excel file. By default it compares 20 common rows from both tables (subject to availabillity) but the number can be overridden with the command line argument `--sample-count`. Command samples:\n\n * Command without `--sample-count` parameter:\n\n ``tulona compare-row --datasources employee_postgres,employee_mysql``\n\n * Command with `--sample-count` parameter:\n\n ``tulona compare-row --sample-count 50 --datasources employee_postgres,employee_mysql``\n\n * Compare queries instead of tables, useful when you want to compare resutls of two queries:\n\n ``tulona compare-row --datasources employee_postgres_query,employee_mysql_query``\n\n * Sample output will be something like this:\n\n |compare_row|\n\n* **compare-column**: To compare columns from tables from two sources/tables. This is expecially useful when you want see if all the rows from one table/source is present in the other one by comparing the primary/unique key. The result will be an excel file with extra primary/unique keys from both sides. If both have the same set of primary/unique keys, essentially means they have the same rows, excel file will be empty. Command samples:\n\n * Column[s] to compare is[are] specified in `tulona-project.yml` file as part of datasource configs, with `compare_column` property. Sample command:\n\n ``tulona compare-column --datasources employee_postgres,employee_mysql``\n\n * Compare multiples columns as composite key (combination of column values will be compared) with additional `--composite` flag:\n\n ``tulona compare-column --composite --datasources employee_postgres,employee_mysql``\n\n * Sample output will be something like this:\n\n |compare_column|\n\n* **compare**: To prepare a comparison report for evrything together. To executed this command just swap the command from any of the above commands with `compare`. It will prepare comparison of everything and write them into different sheets of a single excel file. Sample command:\n\n ``tulona compare --datasources employee_postgres,employee_mysql``\n\n* **scan**: To scan and compare databases or schemas in terms of metadata and tables present if you want to compare all tables and don't want to set up datasource config for all of them. Sample commands:\n\n * Scan without comparing:\n\n ``tulona scan --datasources postgresdb_postgres_schema,none_mysql_schema``\n\n * Scan and compare:\n\n ``tulona scan --compare --datasources postgresdb_postgres_schema,none_mysql_schema``\n\n* **run**: To execute all the tasks defined in the `task_config` section. Sample command:\n\n ``tulona run``\n\nIf you setup `task_config`, there is no need to pass the `--datasources` parameter.\nIn that case the following command (to compare some datasoruces):\n\n``tulona compare --datasources employee_postgres,employee_mysql``\n\nwill become this:\n\n``tulona compare``\n\nand it will run all the `compare` tasks defined in the `task_config` section. From our example project config file above, it will run 2 `compare` tasks.\n\nAlso setting up `task_config` can be greatly benificial as you can set up different instance of same/different tasks with different config to execute in one go with the `run` command.\n\nPlease look at the sample project config from above to understand how to set up `task_config` property.\n\nTo know more about any specific command, execute `tulona <command> -h`.\n\n\nSupported Data Platforms\n------------------------\n\n.. list-table::\n :widths: 20 20 200\n :header-rows: 1\n\n * - Platform\n - Adapter Name\n - Supported Auth Mechanism\n * - Postgres\n - postgres\n - Connection string, Password\n * - MySQL\n - mysql\n - Connection string, Password\n * - Snowflake\n - snowflake\n - Password, Key pair, SSO (Externalbrowser)\n * - Microsoft SQL Server\n - mssql\n - Connection string\n * - BigQuery\n - bigquery\n - Service Account Json Key\n\n\nDevelopment Environment Setup\n-----------------------------\n* For live installation execute `pip install -e \".[dev]\"`.\n\n\nBuild Wheel Executable\n----------------------\n* Execute `python -m build`.\n\nInstall Wheel Executable File\n-----------------------------\n* Execute `pip install <wheel-file.whl>`\n\n\n.. |profile| image:: images/profile.png\n :alt: Profile output\n.. |compare_row| image:: images/compare_row.png\n :alt: Row comparison output\n.. |compare_column| image:: images/compare_column.png\n :alt: Column comparison output\n\n\n.. |CI Test| image:: https://github.com/mrinalsardar/tulona/actions/workflows/test.yaml/badge.svg\n :target: https://github.com/mrinalsardar/tulona/actions/workflows/test.yaml\n.. |Deployment| image:: https://github.com/mrinalsardar/tulona/actions/workflows/publish.yaml/badge.svg\n :target: https://github.com/mrinalsardar/tulona/actions/workflows/publish.yaml\n.. |Coverage| image:: https://codecov.io/gh/mrinalsardar/tulona/graph/badge.svg?token=UGNjjgRskE\n :target: https://codecov.io/gh/mrinalsardar/tulona\n :alt: Coverage status\n.. |PyPI Latest Release| image:: https://img.shields.io/pypi/v/tulona.svg\n :target: https://pypi.python.org/pypi/tulona/\n.. |PyPI Downloads| image:: https://img.shields.io/pypi/dm/tulona.svg?label=PyPI%20downloads\n :target: https://pypi.org/project/tulona/\n.. |License Apache-2.0| image:: https://img.shields.io/:license-Apache%202-brightgreen.svg\n :target: http://www.apache.org/licenses/LICENSE-2.0.txt\n.. |Codestyle Black| image:: https://img.shields.io/badge/code%20style-black-000000.svg\n :target: https://github.com/psf/black\n",
"bugtrack_url": null,
"license": null,
"summary": "A tool to compare data from different sources.",
"version": "0.11.0",
"project_urls": {
"Documentation": "https://github.com/mrinalsardar/tulona",
"Homepage": "https://github.com/mrinalsardar/tulona",
"Issues": "https://github.com/mrinalsardar/tulona/issues",
"Repository": "https://github.com/mrinalsardar/tulona.git"
},
"split_keywords": [
"tulona",
" comparison",
" data comparison",
" database scan",
" database profile"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "47fef9f97c14e6efcc3eed66fdabee0ca0586e501e117173ac8ec51f5476fd51",
"md5": "6d3136b2570740e6395c66827e322d5d",
"sha256": "c0ad9e50c6e108730421f128ea516ddcd7287c854b049e0cf8f176915a84609b"
},
"downloads": -1,
"filename": "tulona-0.11.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "6d3136b2570740e6395c66827e322d5d",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 39807,
"upload_time": "2024-08-05T07:41:34",
"upload_time_iso_8601": "2024-08-05T07:41:34.110839Z",
"url": "https://files.pythonhosted.org/packages/47/fe/f9f97c14e6efcc3eed66fdabee0ca0586e501e117173ac8ec51f5476fd51/tulona-0.11.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "59c72bec423d946d947f60a4f249a4ae0fa32bf38ffa4a087f7e1ee8fa9253a6",
"md5": "b654de1a678812ae2466ffbfa3eadcc6",
"sha256": "eaee88e9c9d20de690238b1dac188a7fc810897ad39ccd4e869c42f940aed66a"
},
"downloads": -1,
"filename": "tulona-0.11.0.tar.gz",
"has_sig": false,
"md5_digest": "b654de1a678812ae2466ffbfa3eadcc6",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 35577,
"upload_time": "2024-08-05T07:41:36",
"upload_time_iso_8601": "2024-08-05T07:41:36.171507Z",
"url": "https://files.pythonhosted.org/packages/59/c7/2bec423d946d947f60a4f249a4ae0fa32bf38ffa4a087f7e1ee8fa9253a6/tulona-0.11.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-08-05 07:41:36",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "mrinalsardar",
"github_project": "tulona",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [],
"lcname": "tulona"
}
JSON
