Skip to content
This repository was archived by the owner on Sep 17, 2019. It is now read-only.

Commit 1920ca3

Browse files
Update README.md
1 parent 8eddd46 commit 1920ca3

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

README.md

+6-1
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,11 @@ If you do find this works for a JDBC driver without an example, let me know and
1414
This plugin does not bundle any JDBC jar files, and does expect them to be in a
1515
particular location. Please ensure you read the 4 installation lines below.
1616

17+
## Support & release schedule
18+
I no longer have time at work to maintain this plugin in step with Logstash's releases, and I am not completely immersed in the Logstash ecosystem. If something is broken for you I will do my best to help, but I cannot guarantee timeframes.
19+
20+
Pull requests are always welcome.
21+
1722
## Changelog
1823
See CHANGELOG.md
1924

@@ -50,7 +55,7 @@ For development:
5055
| statement | Array | An array of strings representing the SQL statement to run. Index 0 is the SQL statement that is prepared, all other array entries are passed in as parameters (in order). A parameter may either be a property of the event (i.e. "@timestamp", or "host") or a formatted string (i.e. "%{host} - %{message}" or "%{message}"). If a key is passed then it will be automatically converted as required for insertion into SQL. If it's a formatted string then it will be passed in verbatim. | Yes | |
5156
| unsafe_statement | Boolean | If yes, the statement is evaluated for event fields - this allows you to use dynamic table names, etc. **This is highly dangerous** and you should **not** use this unless you are 100% sure that the field(s) you are passing in are 100% safe. Failure to do so will result in possible SQL injections. Example statement: [ "insert into %{table_name_field} (column) values(?)", "fieldname" ] | No | False |
5257
| max_pool_size | Number | Maximum number of connections to open to the SQL server at any 1 time | No | 5 |
53-
| connection_timeout | Number | Number of seconds before a SQL connection is closed | No | 2800 |
58+
| connection_timeout | Number | Number of milliseconds before a SQL connection is closed | No | 10000 |
5459
| flush_size | Number | Maximum number of entries to buffer before sending to SQL - if this is reached before idle_flush_time | No | 1000 |
5560
| max_flush_exceptions | Number | Number of sequential flushes which cause an exception, before the set of events are discarded. Set to a value less than 1 if you never want it to stop. This should be carefully configured with respect to retry_initial_interval and retry_max_interval, if your SQL server is not highly available | No | 10 |
5661
| retry_initial_interval | Number | Number of seconds before the initial retry in the event of a failure. On each failure it will be doubled until it reaches retry_max_interval | No | 2 |

0 commit comments

Comments
 (0)