Corrected READMEs (embulk-output-jdbc operations are not resumable)

Author: hito4t

embulk-output-db2/README.md

@@ -42,15 +42,15 @@ DB2 output plugins for Embulk loads records to DB2.
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: No. If fails, the target table could be dropped (because DB2 can't rollback DDL).

embulk-output-jdbc/README.md

@@ -41,23 +41,23 @@ Generic JDBC output plugin for Embulk loads records to a database using a JDBC d
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: No. If fails, the target table could be dropped.
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, merges the intermediate tables into the target table. Namely, if primary keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **merge_direct**:
   * Behavior: This mode merges rows to the target table directly. Namely, if primary keys of an input record already exist in the target table, the target record is updated by the input record, otherwise the input record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: No.

embulk-output-mysql/README.md

@@ -43,23 +43,23 @@ MySQL output plugin for Embulk loads records to MySQL.
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: No. If fails, the target table could be dropped (because MySQL can't rollback DDL).
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ... ON DUPLICATE KEY UPDATE ...` query. Namely, if primary keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **merge_direct**:
   * Behavior: This mode inserts rows to the target table directly using `INSERT INTO ... ON DUPLICATE KEY UPDATE ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: No.

embulk-output-oracle/README.md

@@ -46,23 +46,23 @@ Oracle output plugin for Embulk loads records to Oracle.
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: Yes.
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `MERGE INTO ... WHEN MATCHED THEN UPDATE ...  WHEN NOT MATCHED THEN INSERT ...` query. Namely, if merge keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 
 ### Insert methods
 

embulk-output-postgresql/README.md

@@ -45,23 +45,23 @@ PostgreSQL output plugin for Embulk loads records to PostgreSQL.
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: Yes.
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `WITH updated AS (UPDATE .... RETURNING ...) INSERT INTO ....` query. Namely, if merge keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **merge_direct**:
   * Behavior: This mode inserts rows to the target table directly using `WITH S AS (SELECT ...), updated AS (UPDATE .... RETURNING ...) INSERT INTO ....` query. If the target table doesn't exist, it is created automatically.
   * Transactional: No.

embulk-output-redshift/README.md

@@ -97,23 +97,23 @@ Redshift output plugin for Embulk loads records to Redshift.
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: Yes.
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, inserts new records from intermediate tables after updating records whose keys exist in intermediate tables. Namely, if merge keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically. NOTE: Merge does not work correctly if merge keys contain `NULL`s.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 
 ### Supported types
 

embulk-output-sqlserver/README.md

@@ -56,23 +56,23 @@ embulk "-J-Djava.library.path=C:\drivers" run input-sqlserver.yml
 * **insert**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `INSERT INTO <target_table> SELECT * FROM <intermediate_table_1> UNION ALL SELECT * FROM <intermediate_table_2> UNION ALL ...` query. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes. This mode successfully writes all rows, or fails with writing zero rows.
-  * Resumable: Yes.
+  * Resumable: No.
 * **insert_direct**:
   * Behavior: This mode inserts rows to the target table directly. If the target table doesn't exist, it is created automatically.
   * Transactional: No. If fails, the target table could have some rows inserted.
   * Resumable: No.
 * **truncate_insert**:
   * Behavior: Same with `insert` mode excepting that it truncates the target table right before the last `INSERT ...` query.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 * **replace**:
   * Behavior: This mode writes rows to an intermediate table first. If all those tasks run correctly, drops the target table and alters the name of the intermediate table into the target table name.
   * Transactional: No. If fails, the target table could be dropped (because SQL Server can't rollback DDL).
   * Resumable: No.
 * **merge**:
   * Behavior: This mode writes rows to some intermediate tables first. If all those tasks run correctly, runs `MERGE INTO ... WHEN MATCHED THEN UPDATE ...  WHEN NOT MATCHED THEN INSERT ...` query. Namely, if merge keys of a record in the intermediate tables already exist in the target table, the target record is updated by the intermediate record, otherwise the intermediate record is inserted. If the target table doesn't exist, it is created automatically.
   * Transactional: Yes.
-  * Resumable: Yes.
+  * Resumable: No.
 
 ### Insert methods