Merge branch 'master' into algolia-fast-follow

Author: markzegarelli

src/connections/destinations/catalog/lantern/index.md

@@ -9,8 +9,6 @@ Lantern is a user behavior monitoring solution for modern product teams. Lantern
 
 This destination is maintained by Lantern. For any issues with the destination, contact [Lantern's support](mailto:[email protected]).
 
-{% include content/beta-note.md %}
-
 ## Getting Started
 
 {% include content/connection-modes.md %}
@@ -65,7 +63,7 @@ analytics.identify('userId123', {
 });
 ```
 
-Lantern does not surface information that links to a user's personal identity. Lantern only analyses the volume of identify calls to detect anomalies related to the total number of unique users and perform various computation over aggregated data. 
+Lantern does not surface information that links to a user's personal identity. Lantern only analyses the volume of identify calls to detect anomalies related to the total number of unique users and perform various computation over aggregated data.
 
 
 ## Track

src/connections/spec/common.md

@@ -119,7 +119,7 @@ Beyond this common structure, each API call adds a few specialized top-level fie
 
 ## Context
 
-Context is a dictionary of extra information that provides useful context about a datapoint, for example the user's `ip` address or `locale`. Context is a complete and explicit specification, so properties outside the spec are ignored. You should **only use** Context fields for their intended meaning.
+Context is a dictionary of extra information that provides useful context about a datapoint, for example the user's `ip` address or `locale`. You should **only use** Context fields for their intended meaning.
 
 <table>
   <tr>

src/connections/storage/warehouses/redshift-faq.md

@@ -25,27 +25,15 @@ Like with most data warehouses, column data types (string, integer, float, etc.)
 
 ## VARCHAR size limits
 
-All Segment-managed schemas have a default VARCHAR size of 512 in order to keep performance high. If you wish to increase the VARCHAR size, you can run the following query to create a temp column with the VARCHAR size of your choosing. The query then copies over the data from the original column, drops the original column and finally renames the temp column back to the original column. Keep in mind that this process will not backfill any truncated data. The only way to currently backfill this truncated data is to run a backfill which requires a Business Tier Segment account. NOTE: The following query will only work if you're changing the VARCHAR size of a string column. Do not use this query to change a column type (i.e. integer to float).
+All Segment-managed schemas have a default VARCHAR size of 512 in order to keep performance high. If you wish to increase the VARCHAR size, you can run the following query.
 
 ```sql
-BEGIN;
-  LOCK table_name;
-  ALTER TABLE table_name ADD COLUMN column_new column_type;
-  UPDATE table_name SET column_new = column_name;
-  ALTER TABLE table_name DROP column_name;
-  ALTER TABLE table_name RENAME column_new TO column_name;
-  COMMIT;
+  ALTER TABLE table_name ALTER COLUMN column_name column_type;
 ```
 
 Example:
 ```sql
-BEGIN;
-  LOCK segment_prod.identifies;
-  ALTER TABLE segment_prod.identifies ADD COLUMN new_account_id VARCHAR(1024);
-  UPDATE segment_prod.identifies SET new_account_id = account_id;
-  ALTER TABLE segment_prod.identifies DROP account_id;
-  ALTER TABLE table_name RENAME new_account_id TO account_id;
-  COMMIT;
+  ALTER TABLE segment_prod.identifies ALTER COLUMN account_id TYPE VARCHAR(1024);
 ```
 > warning ""
 > Increasing the default size can impact query performance as it needs to process more data to accomodate the increased column size. See [Amazon's Redshift Documentation](https://docs.aws.amazon.com/redshift/latest/dg/c_best-practices-smallest-column-size.html) for more details.

src/connections/storage/warehouses/schema.md

@@ -602,8 +602,6 @@ After analyzing the data from dozens of customers we set the string column lengt
 
 We special-case compression for some known columns like event names and timestamps. The others default to LZO. We may add look-ahead sampling down the road, but from inspecting the datasets today this would be unnecessary complexity.
 
-After a column is created, Redshift doesn't allow altering. Swapping and renaming may work down the road, but this would cause thrashing and performance issues. If you would like to change the column size, see our [docs here](/docs/connections/storage/warehouses/redshift-faq/#varchar-size-limits).
-
 ## Timestamps
 
 The Segment API associates four timestamps with every call: `timestamp`, `original_timestamp`, `sent_at` and `received_at`.