<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>EGRESS on Kinetica Docs</title><link>/7.2/snippet-tags/egress/</link><description>Recent content in EGRESS on Kinetica Docs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/7.2/snippet-tags/egress/index.xml" rel="self" type="application/rss+xml"/><item><title>Exporting Data</title><link>/7.2/snippets/export-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.2/snippets/export-data/</guid><description>EXPORT ... INTO Sources (Table/Query) Data Sinks (File/Table/DML) Delimited Text Options Parquet Files Naming Options Sizing Options EXPORT ... INTO Sources (Table/Query) Table Query Table 1 2 EXPORT TABLE employee INTO FILE PATH &amp;#39;/export/employee.csv&amp;#39; Query 1 2 3 4 5 6 7 EXPORT QUERY ( SELECT id, manager_id, first_name, last_name, salary, hire_date FROM employee WHERE dept_id = 2 ) INTO FILE PATH &amp;#39;/export/employee_dept2.csv&amp;#39; Data Sinks (File/Table/DML) File Table (via JDBC) DML (via JDBC) Init Options (via JDBC) File 1 2 3 EXPORT TABLE employee INTO FILE PATH &amp;#39;/data/employee.</description></item><item><title>JSON Egress</title><link>/7.2/snippets/json-egress/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.2/snippets/json-egress/</guid><description>Simple Egress Egress with Parameters Egress with Aggregation The /get/records/json REST endpoint can be called to retrieve data in JSON form directly from the database.
See Overview for call details and Responses for return values.
Simple Egress cURL Python Java JavaScript Node.js cURL 1 2 3 4 5 6 7 8 9 10 KINETICA_URL=http://localhost:9191 USERNAME=auser PASSWORD=apassword TABLE_NAME=product # Quote the URL when passing multiple options, or any &amp;amp; will stop the URL # parsing and run the URL parsed up to that point as a background job curl -sS ${KINETICA_URL}/get/records/json?</description></item><item><title>Creating Data Sinks</title><link>/7.2/snippets/create-data-sinks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.2/snippets/create-data-sinks/</guid><description>Azure BLOB Google Cloud Storage HDFS JDBC Kafka Local Table S3 Webhook Several authentication schemes across multiple consumers are supported. For a detailed overview of all of the consumer-specific options, see the SQL documentation.
Note
Creating an authenticated data sink may require creating a corresponding credential object to store the authentication information and then referencing that object when creating the data sink. See Creating Credentials for examples.
Azure BLOB Credential Managed Credentials Credential 1 2 3 4 5 6 7 CREATE DATA SINK azure_dsink LOCATION = &amp;#39;AZURE&amp;#39; WITH OPTIONS ( CREDENTIAL = &amp;#39;azure_cred&amp;#39;, CONTAINER NAME = &amp;#39;samplecontainer&amp;#39; ) Managed Credentials 1 2 3 4 5 6 7 8 9 CREATE DATA SINK azure_dsink LOCATION = &amp;#39;AZURE&amp;#39; WITH OPTIONS ( USE_MANAGED_CREDENTIALS = true, STORAGE ACCOUNT NAME = &amp;#39;sampleacc&amp;#39;, CONTAINER NAME = &amp;#39;samplecontainer&amp;#39;, TENANT ID = &amp;#39;x0xxx10-00x0-0x01-0xxx-x0x0x01xx100&amp;#39; ) Google Cloud Storage Credential Managed Credentials Public (No Auth) JSON Key Credential 1 2 3 4 5 6 7 CREATE DATA SINK gcs_dsink LOCATION = &amp;#39;GCS&amp;#39; WITH OPTIONS ( CREDENTIAL = &amp;#39;gcs_cred&amp;#39;, GCS_BUCKET_NAME = &amp;#39;gcs-private&amp;#39; ) Managed Credentials 1 2 3 4 5 6 7 CREATE DATA SINK gcs_dsink LOCATION = &amp;#39;GCS&amp;#39; WITH OPTIONS ( USE_MANAGED_CREDENTIALS = true, GCS_BUCKET_NAME = &amp;#39;gcs-private&amp;#39; ) Public (No Auth) 1 2 3 CREATE DATA SINK gcs_dsink LOCATION = &amp;#39;GCS&amp;#39; WITH OPTIONS (GCS_BUCKET_NAME = &amp;#39;gcs-public&amp;#39;) JSON Key 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 CREATE DATA SINK gcs_dsink LOCATION = &amp;#39;GCS&amp;#39; WITH OPTIONS ( GCS_SERVICE_ACCOUNT_KEYS = &amp;#39; { &amp;#34;type&amp;#34;: &amp;#34;service_account&amp;#34;, &amp;#34;project_id&amp;#34;: &amp;#34;auser&amp;#34;, &amp;#34;private_key_id&amp;#34;: &amp;#34;abcdef1234567890&amp;#34;, &amp;#34;private_key&amp;#34;: &amp;#34;-----BEGIN PRIVATE KEY-----\nABCDEFG=\n-----END PRIVATE KEY-----\n&amp;#34;, &amp;#34;client_email&amp;#34;: &amp;#34;auser@auser.</description></item><item><title>Creating Streams</title><link>/7.2/snippets/create-streams/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.2/snippets/create-streams/</guid><description>Monitor Target Refresh Event Options Several authentication schemes across multiple consumers are supported. For a detailed overview of all of the consumer-specific options, see the SQL documentation.
Monitor Target Data Sink Kafka (No Auth) Local Table HTTP HTTPS Data Sink 1 2 CREATE STREAM kin_stream ON example.order_stream WITH OPTIONS (DATASINK_NAME = &amp;#39;kin_dsink&amp;#39;) Kafka (No Auth) 1 2 3 4 5 6 CREATE STREAM kin_stream ON example.order_stream WITH OPTIONS ( DESTINATION = &amp;#39;kafka://kafka-test:9092&amp;#39;, KAFKA_TOPIC_NAME = &amp;#39;kafka-test&amp;#39; ) Local Table 1 2 CREATE STREAM kin_stream ON example.</description></item></channel></rss>