embulk-input-redshift 0.9.3 → 0.10.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 6e8c344685265804a7323eab781eaf7bf87653bf
-  data.tar.gz: 95dd684c86cbc4fd44a10839a1949e7c44245053
+SHA256:
+  metadata.gz: 9c54964bbf0155adb050eeb74010c7623121ed3c01e4cd61a7bb61924c9fdcd2
+  data.tar.gz: 6a8cda4203c69b5c5ff3045c75e833c06111cfacb419c257676c4fdc7f67fb4b
 SHA512:
-  metadata.gz: c18d9405bbfb2609223c193679704bfcf6cfbc594d948603b9609b321a9b06e7710daf0e677287c9f972a1216790de77d6713b5d50158177531e558150762d4a
-  data.tar.gz: 71011ae9e8f7077807a73b3c3d72785c624a4336fae8a5e33e9a2695ea2ba87cd9f71f1ea4a74e549ec32444956ac6e6f49a99e079f9884044d1c2b1750d4397
+  metadata.gz: 4882f793a635c81330746bab77fec9467cd3c250fd6c64107f2d0826cff2a7a37e31912dbeb9fcdac4d5dcf32cfcb64ad83b26b80deb72693361bdd5f8ed29fa
+  data.tar.gz: 518f1f94e44b5606251afe4616bf964b90b5e6be83760668c9e2237f344922de8f40e495dfffd663412e1232011d89f16323d079a5dfa36d37b3762786d88014

data/README.md

@@ -33,7 +33,8 @@ Redshift input plugin for Embulk loads records from Redshift.
 - **incremental_columns**: column names for incremental loading (array of strings, default: use primary keys)
 - **last_record**: values of the last record for incremental loading (array of objects, default: load all records)
 - **default_timezone**: If the sql type of a column is `date`/`time`/`datetime` and the embulk type is `string`, column values are formatted int this default_timezone. You can overwrite timezone for each columns using column_options option. (string, default: `UTC`)
-- **column_options**: advanced: a key-value pairs where key is a column name and value is options for the column.
+- **default_column_options**: advanced: column_options for each JDBC type as default. key-value pairs where key is a JDBC type (e.g. 'DATE', 'BIGINT') and value is same as column_options's value.
+- **column_options**: advanced: key-value pairs where key is a column name and value is options for the column.
   - **value_type**: embulk get values from database as this value_type. Typically, the value_type determines `getXXX` method of `java.sql.PreparedStatement`.
   (string, default: depends on the sql type of the column. Available values options are: `long`, `double`, `float`, `decimal`, `boolean`, `string`, `json`, `date`, `time`, `timestamp`)
   - **type**: Column values are converted to this embulk type.
@@ -42,6 +43,8 @@ Redshift input plugin for Embulk loads records from Redshift.
   - **timestamp_format**: If the sql type of the column is `date`/`time`/`datetime` and the embulk type is `string`, column values are formatted by this timestamp_format. And if the embulk type is `timestamp`, this timestamp_format may be used in the output plugin. For example, stdout plugin use the timestamp_format, but *csv formatter plugin doesn't use*. (string, default : `%Y-%m-%d` for `date`, `%H:%M:%S` for `time`, `%Y-%m-%d %H:%M:%S` for `timestamp`)
   - **timezone**: If the sql type of the column is `date`/`time`/`datetime` and the embulk type is `string`, column values are formatted in this timezone.
 (string, value of default_timezone option is used by default)
+- **before_setup**: if set, this SQL will be executed before setup. You can prepare table for input by this option.
+- **before_select**: if set, this SQL will be executed before the SELECT query in the same transaction.
 - **after_select**: if set, this SQL will be executed after the SELECT query in the same transaction.
 
 
@@ -78,7 +81,7 @@ Then, it updates `last_record: ` so that next execution uses the updated last_re
 CREATE INDEX embulk_incremental_loading_index ON table (updated_at, id);
 ```
 
-Recommended usage is to leave `incremental_columns` unset and let this plugin automatically finds an auto-increment (IDENTITY) primary key. Currently, only strings and integers are supported as incremental_columns.
+Recommended usage is to leave `incremental_columns` unset and let this plugin automatically finds an auto-increment (IDENTITY) primary key. Currently, only strings, integers, TIMESTAMP and TIMESTAMPTZ are supported as incremental_columns.
 
 ### Use incremental loading with raw query
 
@@ -165,6 +168,9 @@ in:
   table: "my_table"
   select: "col1, col2, col3"
   where: "col4 != 'a'"
+  default_column_options:
+    TIMESTAMP: { type: string, timestamp_format: "%Y/%m/%d %H:%M:%S", timezone: "+0900"}
+    BIGINT: { type: string }
   column_options:
     col1: {type: long}
     col3: {type: string, timestamp_format: "%Y/%m/%d", timezone: "+0900"}

data/build.gradle

@@ -4,5 +4,5 @@ dependencies {
 
     testCompile project(':embulk-input-jdbc').sourceSets.test.output
 
-    testCompile 'org.embulk:embulk-standards:0.8.15'
+    testCompile 'org.embulk:embulk-standards:0.9.12'
 }

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: embulk-input-redshift
 version: !ruby/object:Gem::Version
-  version: 0.9.3
+  version: 0.10.0
 platform: ruby
 authors:
 - Sadayuki Furuhashi
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2018-08-10 00:00:00.000000000 Z
+date: 2019-05-23 00:00:00.000000000 Z
 dependencies: []
 description: Selects records from a table.
 email:
@@ -19,9 +19,9 @@ extra_rdoc_files: []
 files:
 - README.md
 - build.gradle
-- classpath/embulk-input-jdbc-0.9.3.jar
-- classpath/embulk-input-postgresql-0.9.3.jar
-- classpath/embulk-input-redshift-0.9.3.jar
+- classpath/embulk-input-jdbc-0.10.0.jar
+- classpath/embulk-input-postgresql-0.10.0.jar
+- classpath/embulk-input-redshift-0.10.0.jar
 - classpath/postgresql-9.4-1205-jdbc41.jar
 - lib/embulk/input/redshift.rb
 - src/main/java/org/embulk/input/RedshiftInputPlugin.java
@@ -86,7 +86,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project:
-rubygems_version: 2.4.8
+rubygems_version: 2.6.13
 signing_key:
 specification_version: 4
 summary: JDBC input plugin for Embulk