Skip to content
This repository has been archived by the owner on Sep 23, 2024. It is now read-only.

Commit

Permalink
Notice of PipelineWise being shrank (#59)
Browse files Browse the repository at this point in the history
* PipelineWise shrink Notice

* Create CODEOWNERS

---------

Co-authored-by: Luke Tang <[email protected]>
  • Loading branch information
louis-pie and ltang-wise authored Sep 20, 2024
1 parent eeb4001 commit af22b03
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 3 deletions.
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @transferwise/analytics-platform
13 changes: 10 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,10 @@
# Notice
To better serve Wise business and customer needs, the PipelineWise codebase needs to shrink.
We have made the difficult decision that, going forward many components of PipelineWise will be removed or incorporated in the main repo.
The last version before this decision is [v0.64.1](https://github.com/transferwise/pipelinewise/tree/v0.64.1)

We thank all in the open-source community, that over the past 6 years, have helped to make PipelineWise a robust product for heterogeneous replication of many many Terabytes, daily

# pipelinewise-transform-field

[![PyPI version](https://badge.fury.io/py/pipelinewise-transform-field.svg)](https://badge.fury.io/py/pipelinewise-transform-field)
Expand All @@ -10,7 +17,7 @@ This is a [PipelineWise](https://transferwise.github.io/pipelinewise) compatible

## How to use it

The recommended method of running this component is to use it from [PipelineWise](https://transferwise.github.io/pipelinewise). When running it from PipelineWise you don't need to configure this tap with JSON files, and most of things are automated.
The recommended method of running this component is to use it from [PipelineWise](https://transferwise.github.io/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](https://transferwise.github.io/pipelinewise/user_guide/transformations.html)

If you want to run this [Singer](https://singer.io) compatible component independently please read further.
Expand Down Expand Up @@ -69,7 +76,7 @@ _PS_: 1 =< n =< 9

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:
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.
Expand Down Expand Up @@ -144,7 +151,7 @@ To apply transformation conditionally, you can make use of the property `when` w
}
```

**Sample config**
**Sample config**
[config.json](./sample_config.json)

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

0 comments on commit af22b03

Please sign in to comment.