Skip to main content

pipelinewise-transform-field

PyPI version PyPI - Python Version License: Apache2

Transformation component between Singer taps and targets.

This is a PipelineWise compatible component.

How to use it

The recommended method of running this component is to use it from PipelineWise. When running it from PipelineWise you don't need to configure this tap with JSON files, and most of things are automated. Please check the related documentation at Transformations

If you want to run this Singer compatible component independently please read further.

Install

First, make sure Python 3 is installed on your system or follow these installation instructions for Mac or Ubuntu.

It's recommended to use a virtualenv:

  python3 -m venv venv
  pip install pipelinewise-transform-field

or

  python3 -m venv venv
  . venv/bin/activate
  pip install --upgrade pip setuptools
  pip install .

To validate transformations

transform-field --validate --config [config.json] --catalog [catalog.json]

To run

Put it between a tap and a target with simple unix pipes:

some-singer-tap | transform-field --config [config.json] | some-singer-target

It's reading incoming messages from STDIN and using config.json to transform incoming RECORD messages.

Note: To avoid version conflicts run tap, transform and targets in separate virtual environments.

Transformation types

The following are the transformation types supported by pipelinewise-transform-field:

  • SET-NULL: Transforms any input to NULL
  • HASH: Transforms string input to hash
  • HASH-SKIP-FIRST-n: Transforms string input to hash skipping first n characters, e.g. HASH-SKIP-FIRST-2
  • MASK-DATE: Replaces the months and day parts of date columns to be always 1st of Jan
  • MASK-NUMBER: Transforms any numeric value to zero
  • MASK-HIDDEN: Transforms any string to 'hidden'
  • MASK-STRING-SKIP-ENDS-n: Transforms string input to masked version skipping first and last n characters, e.g. MASK-STRING-SKIP-ENDS-3

PS: 1 =< n =< 9

Conditional transformations

It is possible to transform a record's property based on some given condition(s), the transformation will only take place when all conditions are met.

A condition is a combination of:

  • column [required]: the field to look up to
  • operation [required]: the comparison type to use, the supported ones are equals and regex_match.
  • value [required]: the column value to look for in records.

An equality condition on a column

{
  "column": "<some column name>",
  "equals": <some important value>
}

A regex condition on a column

{
  "column": "<some column name>",
  "regex_match": "<some regex pattern>"
}

A condition on a property within a JSON-type column

{
  "column": "<some column name>",
  "field_path": "<xpath to property within 'column' object>",
  "equals": <some important value>
}

Configuration

You need to define which columns have to be transformed by which method and in which condition the transformation needs to be applied.

Basic transformation

A basic transformation is where a field in all a stream records will be transformed can be achieved with:

{
  "tap_stream_name": "<stream ID>",
  "field_id": "<Name of the field to transform in the record>",
  "type": "<Transformation type>"
}

Transformation within JSON

In order to transform property(ies) within a JSON type field, you can make use of field_paths property:

{
  "tap_stream_name": "<stream ID>",
  "field_id": "<Name of the field to transform in the record>",
  "field_paths": ["xpath to property 1", "xpath to property 2"],
  "type": "<Transformation type>"
}

Conditional Transformation

To apply transformation conditionally, you can make use of the property when which can have one or many conditions:

{
  "tap_stream_name": "<stream ID>",
  "field_id": "<Name of the field to transform in the record>",
  "type": "<Transformation type>",
  "when": [
    {"column": "string_col_1", "equals": "some value"},
    {"column": "string_col_2", "regex_match": ".*PII.*"},
    {"column": "numeric_col_1", "equals": 33},
    {"column": "json_column", "field_path": "metadata/comment", "regex_match": "sensitive"}
  ]
}

Sample config config.json

(Tip: PipelineWise generating this for you from a more readable YAML format)

To check code style:

  1. Install python dependencies in a virtual env
  python3 -m venv venv
  . venv/bin/activate
  pip install --upgrade pip setuptools
  pip install .[test]
  1. Run pylint
pylint transform_field

To run tests:

  1. Install python dependencies in a virtual env and run unit and integration tests
  python3 -m venv venv
  . venv/bin/activate
  pip install --upgrade pip setuptools
  pip install .[test]
  1. Run tests:
  • Unit tests
  pytest -v tests/unit
  • Integration tests
  pytest -v tests/integration
  • All tests
  pytest -v tests

License

Apache License Version 2.0

See LICENSE to see the full text.

Metadata

Release files for pipelinewise-transform-field 2.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pipelinewise-transform-field 2.3.0
File Size Uploaded Provenance Actions
pipelinewise-transform-field-2.3.0.tar.gz 13.8 kB Without provenance Details for pipelinewise-transform-field-2.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pipelinewise-transform-field 2.3.0
File Interpreter ABI Platform Actions
pipelinewise_transform_field-2.3.0-py3-none-any.whl Python 3 none any Details for pipelinewise_transform_field-2.3.0-py3-none-any.whl

Total release size: 29.6 kB

Release files / pipelinewise-transform-field-2.3.0.tar.gz

Download URL pipelinewise-transform-field-2.3.0.tar.gz
Size 13.8 kB
Tags Source
SHA-256 checksum
How to use checksums
94676753cd7d674f9d2d180862b12b63f2cfc4de388ee3dcd137e2d3bc27f7d5
BLAKE2b-256 checksum
How to use checksums
20de5dbc0597a860471937da3134147ff7cb1c0d3efb1916caaf952845692522
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.1

Release files / pipelinewise_transform_field-2.3.0-py3-none-any.whl

Download URL pipelinewise_transform_field-2.3.0-py3-none-any.whl
Size 15.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a0316a9a35bf3378be56ea4f307c0380b149d9359ed8c3625ab9e687b6aba500
BLAKE2b-256 checksum
How to use checksums
218000a3c18d0e23c6bfcb84b4c53c5b10792830b03907fa92950c9a164fcc8d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.10.1

Security for pipelinewise-transform-field 2.3.0

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page