<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS Snippets on Kinetica Docs</title><link>/7.1/aws/snippets/</link><description>Recent content in AWS Snippets on Kinetica Docs</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="/7.1/aws/snippets/index.xml" rel="self" type="application/rss+xml"/><item><title>Exporting Data</title><link>/7.1/aws/snippets/export-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/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>Geohashing</title><link>/7.1/aws/snippets/geohash/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/geohash/</guid><description>Enrich a Point-Based Table with Geohashes Create an Aggregated View with WKT Geometries Enrich a Point-Based Table with Geohashes Create a geohash for pickup locations in the NYC taxi data set.
Lat/Lon-Based Table WKT-Based Table Lat/Lon-Based Table 1 2 3 4 5 6 7 8 CREATE OR REPLACE TABLE example_geospatial.nyctaxi_geohash AS ( SELECT pickup_latitude, pickup_longitude, STXY_GEOHASH(pickup_longitude, pickup_latitude, 6) AS geohash FROM example_geospatial.nyctaxi_xy ) WKT-Based Table 1 2 3 4 5 6 7 CREATE OR REPLACE TABLE example_geospatial.</description></item><item><title>H3 Geohashing</title><link>/7.1/aws/snippets/geohash-h3/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/geohash-h3/</guid><description>Enrich a Point-Based Table with H3 Indexes Create an Aggregated View with WKT Geometries Enrich a Point-Based Table with H3 Indexes Create an H3 index for pickup locations in the NYC taxi data set.
Lat/Lon-Based Table WKT-Based Table Lat/Lon-Based Table 1 2 3 4 5 6 7 8 CREATE OR REPLACE TABLE example_geospatial.nyctaxi_h3 AS ( SELECT pickup_latitude, pickup_longitude, H3_XYTOCELL(pickup_longitude, pickup_latitude, 8) AS h3_index FROM example_geospatial.nyctaxi_xy ) WKT-Based Table 1 2 3 4 5 6 7 CREATE OR REPLACE TABLE example_geospatial.</description></item><item><title>JSON Egress</title><link>/7.1/aws/snippets/json-egress/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/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=https://abcdefg.cloud.kinetica.com/hijklmn/gpudb-0 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>JSON Ingest</title><link>/7.1/aws/snippets/json-ingest/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/json-ingest/</guid><description>Basic Ingest from File Ingest from File with Options Ingest from JSON String The /insert/records/json REST endpoint can be called directly, or with a convenient wrapper in the Java API.
See Overview for call details and Responses for return values.
Basic Ingest from File cURL Python Java Java (Distributed Ingest) JavaScript Node.js cURL 1 2 3 4 5 6 7 8 9 10 KINETICA_URL=https://abcdefg.cloud.kinetica.com/hijklmn/gpudb-0 USERNAME=auser PASSWORD=apassword TABLE_NAME=product JSON_FILE_NAME=products.json curl -sS -X POST --header &amp;#34;Content-Type: application/json&amp;#34; \ --user &amp;#34;${USERNAME}:${PASSWORD}&amp;#34; \ -d @${JSON_FILE_NAME} \ ${KINETICA_URL}/insert/records/json?</description></item><item><title>Loading Data</title><link>/7.1/aws/snippets/load-data/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/load-data/</guid><description>LOAD INTO Single &amp;amp; Multiple KiFS Files Data Sources File/Queue-Based Query-Based File Types Delimited Text Files JSON/GeoJSON Files Parquet Files Shapefiles Avro Files Primary/Shard Keys Query Partitioning Options Other Options External Tables LOAD INTO Single &amp;amp; Multiple KiFS Files Single File Multiple Files by List Single File 1 2 LOAD DATA INTO example.product FROM FILE PATHS &amp;#39;kifs://data/products.csv&amp;#39; Multiple Files by List 1 2 LOAD DATA INTO example.product FROM FILE PATHS &amp;#39;kifs://data/products.</description></item><item><title>Create Credentials</title><link>/7.1/aws/snippets/create-credentials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/create-credentials/</guid><description>Azure GCS HDFS JDBC Kafka (Apache) Kafka (Confluent) S3 (Amazon) Several authentication schemes across multiple providers are supported. For a detailed overview of all of the provider-specific options, see the SQL documentation.
Azure Password SAS Token Active Directory Password 1 2 3 4 CREATE CREDENTIAL azure_cred TYPE = &amp;#39;azure_storage_key&amp;#39;, IDENTITY = &amp;#39;sampleacc&amp;#39;, SECRET = &amp;#39;foobaz123&amp;#39; SAS Token 1 2 3 4 CREATE CREDENTIAL azure_cred TYPE = &amp;#39;azure_sas&amp;#39;, IDENTITY = &amp;#39;sampleacc&amp;#39;, SECRET = &amp;#39;sv=2015-07-08&amp;amp;sr=b&amp;amp;sig=39Up0JzHkxhUlhFEjEH9673DJxe7w6.</description></item><item><title>Create Data Sinks</title><link>/7.1/aws/snippets/create-data-sinks/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/create-data-sinks/</guid><description>Amazon S3 Azure BLOB CData Google Cloud Storage HDFS JDBC Apache Kafka Web Hook Several authentication schemes across multiple providers are supported. For a detailed overview of all of the provider-specific options, see the SQL documentation.
Note
Creating an authenticated data sink requires creating a corresponding credential object to store the authentication information and then referencing that object when creating the data sink. See Create Credentials for examples.
Amazon S3 Credential 1 2 3 4 5 6 7 8 CREATE DATA SINK s3_dsink LOCATION = &amp;#39;S3&amp;#39; WITH OPTIONS ( CREDENTIAL = &amp;#39;s3_cred&amp;#39;, BUCKET NAME = &amp;#39;samplebucket&amp;#39;, REGION = &amp;#39;us-east-2&amp;#39; ) Azure BLOB 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; ) CData Credential Password in URL Credential 1 2 3 CREATE DATA SINK cdata_dsink LOCATION = &amp;#39;jdbc:postgresql:Server=localhost;Port=5432;Database=ki_home&amp;#39; WITH OPTIONS (CREDENTIAL = &amp;#39;cdata_cred&amp;#39;) Password in URL 1 2 CREATE DATA SINK cdata_dsink LOCATION = &amp;#39;jdbc:postgresql:Server=localhost;Port=5432;Database=ki_home;User=dsink_user;Password=dsink_pass&amp;#39; Google Cloud Storage 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; ) HDFS Credential 1 2 3 CREATE DATA SINK hdfs_dsink LOCATION = &amp;#39;HDFS://example.</description></item><item><title>Create Data Sources</title><link>/7.1/aws/snippets/create-data-sources/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/7.1/aws/snippets/create-data-sources/</guid><description>Azure BLOB CData Google Cloud Storage HDFS JDBC Kafka (Apache) Kafka (Confluent) S3 (Amazon) Several authentication schemes across multiple providers are supported. For a detailed overview of all of the provider-specific options, see the SQL documentation.
Azure BLOB Credential Public (No Auth) Password SAS Token Active Directory Credential 1 2 3 4 5 6 7 CREATE DATA SOURCE azure_ds LOCATION = &amp;#39;AZURE&amp;#39; WITH OPTIONS ( CREDENTIAL = &amp;#39;azure_cred&amp;#39;, CONTAINER NAME = &amp;#39;samplecontainer&amp;#39; ) Public (No Auth) 1 2 3 4 5 6 7 CREATE DATA SOURCE azure_ds LOCATION = &amp;#39;AZURE&amp;#39; USER = &amp;#39;sampleacc&amp;#39; WITH OPTIONS ( CONTAINER NAME = &amp;#39;samplecontainer&amp;#39; ) Password 1 2 3 4 5 6 7 8 CREATE DATA SOURCE azure_ds LOCATION = &amp;#39;AZURE&amp;#39; USER = &amp;#39;sampleacc&amp;#39; PASSWORD = &amp;#39;foobaz123&amp;#39; WITH OPTIONS ( CONTAINER NAME = &amp;#39;samplecontainer&amp;#39; ) SAS Token 1 2 3 4 5 6 7 8 CREATE DATA SOURCE azure_ds LOCATION = &amp;#39;AZURE&amp;#39; USER = &amp;#39;sampleacc&amp;#39; WITH OPTIONS ( CONTAINER NAME = &amp;#39;samplecontainer&amp;#39;, SAS TOKEN = &amp;#39;sv=2015-07-08&amp;amp;sr=b&amp;amp;sig=39Up0JzHkxhUlhFEjEH9673DJxe7w6clRCg0V6lCgSo%3D&amp;amp;se=2016-10-18T21%A51%A337Z&amp;amp;sp=rcw&amp;#39; ) Active Directory 1 2 3 4 5 6 7 8 9 10 CREATE DATA SOURCE azure_ds LOCATION = &amp;#39;AZURE&amp;#39; USER = &amp;#39;jdoe&amp;#39; PASSWORD = &amp;#39;foobaz123&amp;#39; WITH OPTIONS ( STORAGE ACCOUNT NAME = &amp;#39;sampelacc&amp;#39;, CONTAINER NAME = &amp;#39;samplecontainer&amp;#39;, TENANT ID = &amp;#39;x0xxx10-00x0-0x01-0xxx-x0x0x01xx100&amp;#39; ) CData Credential Password in URL Password as Parameter Credential 1 2 3 CREATE DATA SOURCE cdata_ds LOCATION = &amp;#39;jdbc:postgresql:Server=my.</description></item></channel></rss>