@@ -127,14 +127,14 @@ Here is the list:
127
127
128
128
|==========================================================
129
129
|sql_last_value | The value used to calculate which rows to query. Before any query is run,
130
- this is set to Thursday, 1 January 1970, or 0 if `use_column_value` is true and
130
+ this is set to Thursday, 1 January 1970, 0, or 00000000-0000-0000-0000-000000000000 if `use_column_value` is true and
131
131
`tracking_column` is set. It is updated accordingly after subsequent queries are run.
132
132
|offset, size| Values used with manual paging mode to explicitly implement the paging.
133
133
Supported only if <<plugins-{type}s-{plugin}-jdbc_paging_enabled>> is enabled and
134
134
<<plugins-{type}s-{plugin}-jdbc_paging_mode>> has the `explicit` value.
135
135
|==========================================================
136
136
137
- Example :
137
+ Examples :
138
138
[source,ruby]
139
139
---------------------------------------------------------------------------------------------------
140
140
input {
@@ -240,7 +240,7 @@ This plugin supports the following configuration options plus the <<plugins-{typ
240
240
| <<plugins-{type}s-{plugin}-statement_filepath>> |a valid filesystem path|No
241
241
| <<plugins-{type}s-{plugin}-target>> | {logstash-ref}/field-references-deepdive.html[field reference] | No
242
242
| <<plugins-{type}s-{plugin}-tracking_column>> |<<string,string>>|No
243
- | <<plugins-{type}s-{plugin}-tracking_column_type>> |<<string,string>>, one of `["numeric", "timestamp"]`|No
243
+ | <<plugins-{type}s-{plugin}-tracking_column_type>> |<<string,string>>, one of `["numeric", "timestamp", "uuid" ]`|No
244
244
| <<plugins-{type}s-{plugin}-use_column_value>> |<<boolean,boolean>>|No
245
245
| <<plugins-{type}s-{plugin}-use_prepared_statements>> |<<boolean,boolean>>|No
246
246
|=======================================================================
@@ -645,10 +645,24 @@ The column whose value is to be tracked if `use_column_value` is set to `true`
645
645
[id="plugins-{type}s-{plugin}-tracking_column_type"]
646
646
===== `tracking_column_type`
647
647
648
- * Value can be any of: `numeric`, `timestamp`
648
+ * Value can be any of: `numeric`, `timestamp`, `uuid`
649
649
* Default value is `"numeric"`
650
650
651
- Type of tracking column. Currently only "numeric" and "timestamp"
651
+ Type of tracking column. Currently only "numeric", "timestamp" and "uuid"
652
+
653
+ NOTE: Example of uuid type usage in PostgreSQL.
654
+ [source,ruby]
655
+ ---------------------------------------------------------------------------------------------------
656
+ input {
657
+ jdbc {
658
+ statement => "SELECT id, mycolumn1, mycolumn2 FROM my_table WHERE id > :sql_last_value::uuid"
659
+ use_column_value => true
660
+ tracking_column => "id"
661
+ tracking_column_type => "uuid"
662
+ # ... other configuration bits
663
+ }
664
+ }
665
+ ---------------------------------------------------------------------------------------------------
652
666
653
667
[id="plugins-{type}s-{plugin}-use_column_value"]
654
668
===== `use_column_value`
0 commit comments