Merge pull request #6353 from segmentio/develop

Release 24.14.2

Author: cmastr

src/_data/catalog/destination_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination categories last updated 2024-04-02 
+# destination categories last updated 2024-04-04 
 items:
 - display_name: A/B Testing
   slug: a-b-testing

src/_data/catalog/destinations.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-04-02 
+# destination data last updated 2024-04-04 
 items:
 - id: 637e8d185e2dec264895ea89
   display_name: 1Flow
@@ -16939,7 +16939,7 @@ items:
     label: Only Track Known Users
   - name: devicePropertyAllowlist
     type: array
-    defaultValue: ''
+    defaultValue: []
     description: >-
       By default, the Braze SDK automatically detects and collects all device
       properties in DeviceProperties. To override this behavior, provide an
@@ -54842,7 +54842,7 @@ items:
     browser: true
     mobile: false
     server: true
-    warehouse: false
+    warehouse: true
     cloudAppObject: false
   components: []
   browserUnbundlingSupported: false
@@ -58096,7 +58096,7 @@ items:
     screen: false
     page: true
   platforms:
-    browser: false
+    browser: true
     mobile: true
     server: true
     warehouse: false
@@ -58111,7 +58111,7 @@ items:
       mobile: false
       server: false
     cloud:
-      web: false
+      web: true
       mobile: true
       server: true
   settings: []
@@ -58124,7 +58124,7 @@ items:
     hidden: false
     defaultTrigger: type = "track"
     fields:
-    - id: 6xJkT6L1ma1A2a1xsiu9sV
+    - id: ttZFa3ePvTMVgpiKiEKRxb
       sortOrder: 0
       fieldKey: conversionHappenedAt
       label: Timestamp
@@ -58141,7 +58141,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: mJVRJ9sGcqURTQSVmrBXeM
+    - id: qDa2X6fpjD2HjGRCLKr7aV
       sortOrder: 1
       fieldKey: conversionValue
       label: Conversion Value
@@ -58150,12 +58150,17 @@ items:
         The monetary value for this conversion. Example: {“currencyCode”: “USD”,
         “amount”: “50.0”}.
       placeholder: ''
+      defaultValue:
+        currencyCode:
+          '@path': $.properties.currency
+        amount:
+          '@path': $.properties.revenue
       required: false
       multiple: false
       choices: null
       dynamic: false
       allowNull: false
-    - id: foEFxXqvQhpVUNcqSdGbVm
+    - id: 9vnTyhN6sQKsn83mbbfRtt
       sortOrder: 2
       fieldKey: eventId
       label: Event ID
@@ -58171,7 +58176,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: qe8iPAgX1Yp2n7JxSHqRQu
+    - id: 3vFYDU8SiJU7JkRVfcbEfM
       sortOrder: 3
       fieldKey: email
       label: Email
@@ -58181,12 +58186,14 @@ items:
         Segment will hash this value before sending it to LinkedIn. One of email
         or LinkedIn UUID or Axciom ID or Oracle ID is required.
       placeholder: ''
+      defaultValue:
+        '@path': $.traits.email
       required: false
       multiple: false
       choices: null
       dynamic: false
       allowNull: false
-    - id: nH1shvmLyMUQiwfUcov9aF
+    - id: c38o7gni9dsLvQ2mMNvZLp
       sortOrder: 4
       fieldKey: linkedInUUID
       label: LinkedIn First Party Ads Tracking UUID
@@ -58203,7 +58210,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: gQYncwAatWgacGcnu8EssL
+    - id: bxz3ZiYN69JtKHRUMV1ZzR
       sortOrder: 5
       fieldKey: acxiomID
       label: Acxiom ID
@@ -58217,7 +58224,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: dsF9HyBJqj9cfCQ7q69gSc
+    - id: nQrNduKvXEDzeZLiCFpetj
       sortOrder: 6
       fieldKey: oracleID
       label: Oracle ID
@@ -58232,7 +58239,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: atbJuQr3oRC45fzvNntpWj
+    - id: oEHnop4FE7g1K3v58mXKUH
       sortOrder: 7
       fieldKey: userInfo
       label: User Info
@@ -58246,7 +58253,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: rHspfR462eT5nuGiYyaVaf
+    - id: 8XbbzvWqfHS2CnP5xroUnv
       sortOrder: 8
       fieldKey: adAccountId
       label: Ad Account
@@ -58258,7 +58265,7 @@ items:
       choices: null
       dynamic: true
       allowNull: false
-    - id: 2tG5SqwxLQrAD2uLge7ST2
+    - id: a9cix4ajiPCkRrzK2GskF9
       sortOrder: 9
       fieldKey: campaignId
       label: Add Campaigns to Conversion
@@ -58274,7 +58281,7 @@ items:
       choices: null
       dynamic: true
       allowNull: false
-    - id: wNa77N2nT9dhpkLBkYjsdB
+    - id: xmmAibWFnzdjAQRtmVhPnp
       sortOrder: 10
       fieldKey: conversionRuleId
       label: Existing Conversion Rule ID
@@ -58288,7 +58295,7 @@ items:
       choices: null
       dynamic: true
       allowNull: false
-    - id: 4ZUF6BoCMMX21hqKk9DSA8
+    - id: sqRRMDCBS72wqKcj3x1M6n
       sortOrder: 11
       fieldKey: name
       label: Name
@@ -58300,7 +58307,7 @@ items:
       choices: null
       dynamic: false
       allowNull: false
-    - id: s9GEnFA2RYU4HorfUikmJi
+    - id: 9Rvza87eBc7vQHXLK6HGEb
       sortOrder: 12
       fieldKey: conversionType
       label: Conversion Type
@@ -58384,7 +58391,7 @@ items:
         value: SALES_QUALIFIED_LEAD
       dynamic: false
       allowNull: false
-    - id: onxEXKiN22jfWMJkVb8o1j
+    - id: wNkv9vT1FDVoXWkQKQcoSo
       sortOrder: 13
       fieldKey: attribution_type
       label: Attribution Type
@@ -58400,7 +58407,7 @@ items:
         value: LAST_TOUCH_BY_CONVERSION
       dynamic: false
       allowNull: false
-    - id: wC6GZhNeSdp9kAkkEMjgcF
+    - id: rv8ryaiuQC78cK9hnFSANv
       sortOrder: 14
       fieldKey: post_click_attribution_window_size
       label: Post-Click Attribution Window Size
@@ -58424,7 +58431,7 @@ items:
         value: 90
       dynamic: false
       allowNull: false
-    - id: h2jjHaUZucSe37sC4ZLSj7
+    - id: 8FbAEBwkMEvBuR7tzp1ujs
       sortOrder: 15
       fieldKey: view_through_attribution_window_size
       label: View-Through Attribution Window Size
@@ -58448,7 +58455,7 @@ items:
         value: 90
       dynamic: false
       allowNull: false
-    - id: 9K8s7kGDmqVE9USNHsJCab
+    - id: xx4ATBDA2cawRcmrCNHV7P
       sortOrder: 16
       fieldKey: onMappingSave
       label: Create a Conversion Rule

src/_data/catalog/destinations_private.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# destination data last updated 2024-04-02 
+# destination data last updated 2024-04-04 
 items:
   - id: 54521fd925e721e32a72eee1
     display_name: Pardot

src/_data/catalog/source_categories.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# source categories last updated 2024-04-02 
+# source categories last updated 2024-04-04 
 items:
   - display_name: A/B Testing
     slug: a-b-testing

src/_data/catalog/sources.yml

@@ -1,5 +1,5 @@
 # AUTOGENERATED FROM PUBLIC API. DO NOT EDIT
-# sources last updated 2024-04-02 
+# sources last updated 2024-04-04 
 items:
   - id: 8HWbgPTt3k
     display_name: .NET

src/_includes/components/actions-fields.html

@@ -39,10 +39,6 @@
 </tbody>
 </table>
 
-{% else %}
-<em>No settings available. The destination may not be publicly visible.</em>
-
-
 {% endif %}
 
 

src/connections/destinations/catalog/actions-kafka/index.md

@@ -100,4 +100,4 @@ The **Send** Action provides multiple ways to specify which Partition an event s
 
 ### What is the "SSL - Reject Unauthorized Certificate Authority" field for?
 
-This field specifies if Segment should reject server connections when a certificate is notsigned by a trusted Certificate Authority (CA). This can be useful for testing purposes or when using a self-signed certificate. 
+This field specifies if Segment should reject server connections when a certificate is not signed by a trusted Certificate Authority (CA). This can be useful for testing purposes or when using a self-signed certificate. 

src/connections/functions/insert-functions.md

@@ -371,50 +371,40 @@ The editor displays logs and request traces from the batch handler.
 
 The [Public API](/docs/api/public-api) Functions/Preview endpoint also supports testing batch handlers. The payload must be a batch of events as a JSON array.
 
+### Handling filtering in a batch
+Events in a batch can be filtered out using custom logic. The filtered events will be surfaced in the [Event Delivery](/docs/connections/event-delivery/) page with reason as `Filtered at insert function`
 
-### Handling batching errors
+```js
+async function onBatch(events, settings) {
+  let response = [];
+  try {
+    for (const event of events) {
+      // some business logic to filter event. Here filtering out all the events with name `drop`
+      if (event.properties.name === 'drop') {
+        continue;
+      }
 
-Standard [function error types](/docs/connections/functions/destination-functions/#destination-functions-error-types) apply to batch handlers. Segment attempts to retry the batch in the case of Timeout or Retry errors. For all other error types, Segment discards the batch. It's also possible to report a partial failure by returning status of each event in the batch. Segment retries only the failed events in a batch until those events are successful or until they result in a permanent error.
+      // some enrichments if needed
+      event.properties.message = "Enriched from insert function";
 
-```json
-[
-	{
-		"status": 200
-	},
-	{
-		"status": 400,
-		"errormessage": "Bad Request"
-	},
-	{
-		"status": 200
-	},
-	{
-		"status": 500,
-		"errormessage": "Error processing request"
-	},
-	{
-		"status": 500,
-		"errormessage": "Error processing request"
-	},
-	{
-		"status": 200
-	},
-]
+      // Enriched events are pushed to response
+      response.push(event);
+    }
+  } catch (error) {
+    console.log(error)
+    throw new RetryError('Failed function', error);
+  }
+
+  // return a subset of transformed event
+  return response;
+}
 ```
 
-For example, after receiving the responses above from the `onBatch` handler, Segment only retries **event_4** and **event_5**.
 
-| Error Type             | Result  |
-| ---------------------- | ------- |
-| Bad Request            | Discard |
-| Invalid Settings       | Discard |
-| Message Rejected       | Discard |
-| RetryError             | Retry   |
-| Timeout                | Retry   |
-| Unsupported Event Type | Discard |
+### Handling batching errors
 
+Standard [function error types](/docs/connections/functions/destination-functions/#destination-functions-error-types) apply to batch handlers. Segment attempts to retry the batch in the case of Timeout or Retry errors. For all other error types, Segment discards the batch.
 
-{% comment %}
 
 ## Destination insert functions logs and errors
 

src/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup.md

@@ -4,29 +4,33 @@ title: Databricks Reverse ETL Setup
 
 Set up Databricks as your Reverse ETL source. 
 
-At a high level, when you set up Databricks for Reverse ETL, the configured user needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured user to allow write permissions for that schema.
+At a high level, when you set up Databricks for Reverse ETL, the configured service-principal needs read permissions for any resources (databases, schemas, tables) the query needs to access. Segment keeps track of changes to your query results with a managed schema (`__SEGMENT_REVERSE_ETL`), which requires the configured service-principal to allow write permissions for that schema.
+
+> info ""
+> Segment supports only OAuth (M2M) authentication. To generate a client ID and Secret, follow the steps listed in Databricks' [OAuth machine-to-machine (M2M) authentication](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"} documentation.
+
 
 ## Required permissions
-* Make sure the user or the service principal you use to connect to Segment has permissions to use that warehouse. In the Databricks console go to **SQL warehouses** and select the warehouse you're using. Navigate to **Overview > Permissions** and make sure the user or the service principal you use to connect to Segment has *can use* permissions.
+* Make sure the service principal you use to connect to Segment has permissions to use that warehouse. In the Databricks console go to **SQL warehouses** and select the warehouse you're using. Navigate to **Overview > Permissions** and make sure the service principal you use to connect to Segment has *can use* permissions.
 
 * To grant access to read data from the tables used in the model query, run: 
 
     ```
-    GRANT USAGE ON SCHEMA <schema_name> TO `<user or service principal you are using to connect to Segment>`; 
-    GRANT SELECT, READ_METADATA ON SCHEMA <schema_name> TO `<user or service principal you are using to connect to Segment>`; 
+    GRANT USAGE ON SCHEMA <schema_name> TO `<service principal you are using to connect to Segment>`; 
+    GRANT SELECT, READ_METADATA ON SCHEMA <schema_name> TO `<service principal you are using to connect to Segment>`; 
     ```
 
 * To grant Segment access to create a schema to keep track of the running syncs, run: 
 
     ```
-    GRANT CREATE on catalog <name of the catalog, usually hive_metastore or main if using unity-catalog> TO `<user or service principal you are using to connect to Segment>`;
+    GRANT CREATE on catalog <name of the catalog, usually hive_metastore or main if using unity-catalog> TO `<service principal you are using to connect to Segment>`;
     ```
 
 * If you want to create the schema yourself instead and then give Segment access to it, run:
 
     ```
     CREATE SCHEMA IF NOT EXISTS __segment_reverse_etl; 
-    GRANT ALL PRIVILEGES ON SCHEMA __segment_reverse_etl TO `<user or service principal you are using to connect to Segment>`;
+    GRANT ALL PRIVILEGES ON SCHEMA __segment_reverse_etl TO `<service principal you are using to connect to Segment>`;
     ```
 
 ## Set up guide
@@ -46,12 +50,14 @@ To set up Databricks as your Reverse ETL source:
     * Hostname: `adb-xxxxxxx.azuredatabricks.net`
     * Http Path: `/sql/1.0/warehouses/xxxxxxxxx`
     * Port: `443` (default)
-    * Token: `<your-token>`
-    * Catalog [optional]: `hive_metastore` (default)
+    * Service principal client ID: `<your client ID>`
+    * OAuth secret: `<OAuth secret used during connection>`
+    * Catalog [optional]: If not specified, Segment will use the default catalog
 11. Click **Test Connection** to see if the connection works. If the connection fails, make sure you have the right permissions and credentials, then try again.
 12. Click **Add source** if the test connection is successful. 
 
-> info ""
-> To generate a token, follow the steps listed in the [Databricks docs](https://docs.databricks.com/dev-tools/auth.html#pat){:target="_blank"}. Segment recommends you create a token with no expiration date by leaving the lifetime field empty when creating it. If you already have a token with an expiration date, be sure to keep track of the date and renew it on time.   
+> warning ""
+> Segment previously supported token-based authentication, but now uses OAuth (M2M) authentication at the recommendation of Databricks.
+> If you previously set up your source using token-based authentication, Segment will continue to support it. If you want to create a new source or update the connection settings of an existing source, Segment only supports [OAuth machine-to-machine (M2M) authentication](https://docs.databricks.com/en/dev-tools/auth/oauth-m2m.html){:target="_blank"}.
 
 Once you've succesfully added your Databricks source, [add a model](/docs/connections/reverse-etl/#step-2-add-a-model) and follow the rest of the steps in the Reverse ETL setup guide.