Bump version and add the copy materilized pipe

v3/delete_column_from_landing_data_source_releases/.tinyenv

@@ -1,2 +1,2 @@
 TB_VERSION_WARNING=0
-VERSION=0.0.0
+VERSION=0.0.1

v3/delete_column_from_landing_data_source_releases/README.md

@@ -2,10 +2,10 @@
 
 > Remember to follow the [instructions](../README.md) to setup your Tinybird Data Project before jumping into the use-case steps
 
-- Just delete the desired column from the Data Source
-
 [Pull Request](https://github.com/tinybirdco/use-case-examples/pull/162/files)
 
+- Delete the desired column from the Data Source
+`datasources/analytics_events.datasource`
 ```diff
 SCHEMA >
     `timestamp` DateTime `json:$.timestamp`,
@@ -14,4 +14,34 @@ SCHEMA >
     `version` LowCardinality(String) `json:$.version`,
 -   `environment` Nullable(String) `json:$.environment`,
     `payload` String `json:$.payload`
-```
+```
+- Add a tag to the same Data Source file to specify the field to use to auto-populate the data
+`datasources/analytics_events.datasource`
+```diff
+ENGINE "MergeTree"
+ENGINE_PARTITION_KEY "toYYYYMM(timestamp)"
+ENGINE_SORTING_KEY "timestamp"
+ENGINE_TTL "timestamp + toIntervalDay(60)"
+
++ TAGS "backfill_column=timestamp"
+```
+
+- Bump the Version to re-create the Data Source
+`.tinyenv`
+```diff
+-   VERSION=0.0.0
++   VERSION=0.0.1
+```
+
+- Add a new Materialized Pipe to define how to move the data (copy all the fields except the field being removed)
+`datasources/live_to_new.datasource`
+```sql
+NODE live_to_new
+SQL >
+    SELECT timestamp, session_id, action, version, payload 
+    FROM live.analytics_events
+TYPE MATERIALIZED
+DATASOURCE analytics_events
+```
+
+

v3/delete_column_from_landing_data_source_releases/pipes/live_to_new.pipe

@@ -0,0 +1,7 @@
+NODE live_to_new
+SQL >
+    SELECT timestamp, session_id, action, version, payload 
+    FROM live.analytics_events
+
+TYPE MATERIALIZED
+DATASOURCE analytics_events