-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js connection idle sockets timeout rework, logger improvements #242
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,7 +14,7 @@ export interface ConnectionParams { | |
password: string | ||
database: string | ||
clickhouse_settings: ClickHouseSettings | ||
logWriter: LogWriter | ||
log_writer: LogWriter | ||
application_id?: string | ||
additional_headers?: Record<string, string> | ||
} | ||
|
@@ -51,6 +51,8 @@ export type ConnPingResult = | |
} | ||
| { success: false; error: Error } | ||
|
||
export type ConnOperation = 'Ping' | 'Query' | 'Insert' | 'Exec' | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: I'd rather use the fullname There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I will rename all of these types in 1.0.0, then. They are all prefixed with just |
||
|
||
export interface Connection<Stream> { | ||
ping(): Promise<ConnPingResult> | ||
close(): Promise<void> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
21 is not LTS and might be unstable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's worth keeping if it does not bring any flakiness to the CI run. If it starts to do so, we will remove it.