Bump @clickhouse/client from 0.2.10 to 1.1.0 in /relay-worker
Bumps @clickhouse/client from 0.2.10 to 1.1.0.
Release notes
Sourced from @clickhouse/client's releases.
1.1.0
New features
- Added an option to override the credentials for a particular
query/command/exec/insertrequest via theBaseQueryParams.authsetting; when set, the credentials will be taken from there instead of the username/password provided during the client instantiation (#278).- Added an option to override the
session_idfor a particularquery/command/exec/insertrequest via theBaseQueryParams.session_idsetting; when set, it will be used instead of the session id provided during the client instantiation (@holi0317, #271).Bug fixes
- Fixed the incorrect
ResponseJSON<T>.totalsTypeScript type. Now it correctly matches the shape of the data (T, default =unknown) instead of the formerRecord<string, number>definition (#274).1.0.2
Bug fixes
- The
commandmethod now drains the response stream properly, as the previous implementation could cause theKeep-Alivesocket to close after each request.- (Node.js) Removed an unnecessary error log in the
ResultSet.streammethod if the request was aborted or the result set was closed (#263).Improvements
- (Node.js)
ResultSet.streamlogs an error via theLoggerinstance if the stream emits an error event instead of a simpleconsole.errorcall.- Minor adjustments to the formatting of the
DefaultLoggerlog messages.- Added missing
rows_before_limit_at_leastto the ResponseJSON type (@0237h, #267).1.0.1
A hotfix for both Node.js and Web packages. See the 1.0.0 entry that contains the entire 1.0.x changelog.
Bug fixes
- Fixed the regression where the default HTTP/HTTPS port numbers (80/443) could not be used with the URL configuration (#258).
1.0.0
Formal stable release milestone with many improvements and some breaking changes.
Major new features overview:
- Advanced TypeScript support for
query+ResultSet- URL configuration
From now on, the client will follow the official semantic versioning guidelines.
Deprecated API
The following configuration parameters are marked as deprecated:
- The
hostconfiguration parameter is deprecated; useurlinstead.additional_headersconfiguration parameter is deprecated; usehttp_headersinstead.The client will log a warning if any of these parameters are used. However, it is still allowed to use
hostinstead ofurlandadditional_headersinstead ofhttp_headersfor now; this deprecation is not supposed to break the existing code.These parameters will be removed in the next major release (2.0.0).
... (truncated)
Changelog
Sourced from @clickhouse/client's changelog.
1.1.0 (Common, Node.js, Web)
New features
- Added an option to override the credentials for a particular
query/command/exec/insertrequest via theBaseQueryParams.authsetting; when set, the credentials will be taken from there instead of the username/password provided during the client instantiation (#278).- Added an option to override the
session_idfor a particularquery/command/exec/insertrequest via theBaseQueryParams.session_idsetting; when set, it will be used instead of the session id provided during the client instantiation (@holi0317, #271).Bug fixes
- Fixed the incorrect
ResponseJSON<T>.totalsTypeScript type. Now it correctly matches the shape of the data (T, default =unknown) instead of the formerRecord<string, number>definition (#274).1.0.2 (Common, Node.js, Web)
Bug fixes
- The
commandmethod now drains the response stream properly, as the previous implementation could cause theKeep-Alivesocket to close after each request.- Removed an unnecessary error log in the
ResultSet.streammethod if the request was aborted or the result set was closed (#263).Improvements
ResultSet.streamlogs an error via theLoggerinstance, if the stream emits an error event instead of a simpleconsole.errorcall.- Minor adjustments to the
DefaultLoggerlog messages formatting.- Added missing
rows_before_limit_at_leastto the ResponseJSON type (@0237h, #267).1.0.1 (Common, Node.js, Web)
Bug fixes
- Fixed the regression where the default HTTP/HTTPS port numbers (80/443) could not be used with the URL configuration (#258).
1.0.0 (Common, Node.js, Web)
Formal stable release milestone with a lot of improvements and some breaking changes.
Major new features overview:
From now on, the client will follow the official semantic versioning guidelines.
Deprecated API
The following configuration parameters are marked as deprecated:
hostconfiguration parameter is deprecated; useurlinstead.additional_headersconfiguration parameter is deprecated; usehttp_headersinstead.The client will log a warning if any of these parameters are used. However, it is still allowed to use
hostinstead ofurlandadditional_headersinstead ofhttp_headersfor now; this deprecation is not supposed to break the existing code.
... (truncated)
Commits
9bdea17Change incorrect totals TS type (#280)37aa43dAllow to override session id for a particular request (#281)bd262b9Allow credentials override for a particular request (#279)ad8611eAdd Logger to the ResultSet in the Node.js implementation (#265)21a828cUpdate CHANGELOG and the JSON result testscd19c8bAdd missing property forResponseJSON\<T>type (#268)a357f28Bump version to 1.0.2ddcc741Drain the response stream in the command method (#264)c5ba385Add JSONEachRow + Decimals example800a337Fix flaky query_id test- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)