Package apache-airflow-backport-providers-neo4j
Release: 2021.3.3
Table of contents
Backport package
This is a backport providers package for neo4j provider. All classes for this provider package
are in airflow.providers.neo4j python package.
Only Python 3.6+ is supported for this backport package.
While Airflow 1.10.* continues to support Python 2.7+ - you need to upgrade python to 3.6+ if you want to use this backport package.
Release 2021.3.3
Bug fixes
Corrections in docs and tools after releasing provider RCs (#14082)
Installation
You can install this package on top of an existing airflow 1.10.* installation via
pip install apache-airflow-backport-providers-neo4j
PIP requirements
| PIP package | Version required |
|---|---|
neo4j |
>=4.2.1 |
Provider classes summary
In Airflow 2.0, all operators, transfers, hooks, sensors, secrets for the neo4j provider
are in the airflow.providers.neo4j package. You can read more about the naming conventions used
in Naming conventions for provider packages
Operators
New operators
New Airflow 2.0 operators: airflow.providers.neo4j package |
|---|
| operators.neo4j.Neo4jOperator |
Hooks
New hooks
New Airflow 2.0 hooks: airflow.providers.neo4j package |
|---|
| hooks.neo4j.Neo4jHook |
Releases
Release 2021.3.3
| Commit | Committed | Subject |
|---|---|---|
| 10343ec29 | 2021-02-05 | Corrections in docs and tools after releasing provider RCs (#14082) |
Release 2021.2.5
| Commit | Committed | Subject |
|---|---|---|
| ac2f72c98 | 2021-02-01 | Implement provider versioning tools (#13767) |
| 1d2977f6a | 2021-01-14 | Add Neo4j hook and operator (#13324) |
Release files for apache-airflow-backport-providers-neo4j 2021.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| apache-airflow-backport-providers-neo4j-2021.3.3.tar.gz | 11.5 kB | Without provenance | Details for apache-airflow-backport-providers-neo4j-2021.3.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apache_airflow_backport_providers_neo4j-2021.3.3-py3-none-any.whl | Python 3 | none | any | Details for apache_airflow_backport_providers_neo4j-2021.3.3-py3-none-any.whl |
Total release size: 25.5 kB
Release files / apache-airflow-backport-providers-neo4j-2021.3.3.tar.gz
| Download URL | apache-airflow-backport-providers-neo4j-2021.3.3.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
181a9cf2ff480e2250c330d65419df2d58a83da8b2c0586956409463935d2026
|
|
BLAKE2b-256 checksum How to use checksums |
275768bdbbfacf4aeb6a94b952cf9522d311de383346791ada6f4c3320507b7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.7.9
|
Release files / apache_airflow_backport_providers_neo4j-2021.3.3-py3-none-any.whl
| Download URL | apache_airflow_backport_providers_neo4j-2021.3.3-py3-none-any.whl |
|---|---|
| Size | 13.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1caf8157fd44a883ea4966dd9642e274b4a62ef20ada165c4f3326e6628fea40
|
|
BLAKE2b-256 checksum How to use checksums |
de5c8fd84f93638b553ebd6951fb9cb1616ed52aeb24bfa20bba94e81b06ac9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/50.3.2 requests-toolbelt/0.9.1 tqdm/4.56.0 CPython/3.7.9
|
Security for apache-airflow-backport-providers-neo4j 2021.3.3
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.
