You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* update changelog for version 1.20.0
* update changelog
* update changelog
* new changes in 1.20.0
* removing feature of PR 260
* reformat
* add release date
Copy file name to clipboardExpand all lines: CHANGELOG.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,36 @@ position: 103
8
8
Since v1.17.1, chproxy follows [semantic versioning](https://semver.org/).
9
9
Don't expect breaking changes between 2 releases if they have the same major version.
10
10
11
+
### <aid="229"></a> release 1.20.0, 2022-11-29
12
+
13
+
#### Release note
14
+
* Until chproxy 1.19.0, the same cache was shared for all the users.
15
+
Since 1.20.0, each user has his own cache but you can override this behavior by setting `shared_with_all_users = true` in the config file.
16
+
* Since 1.20.0, if you're using docker images from [contentsquareplatform docker hub](https://hub.docker.com/r/contentsquareplatform/chproxy), the way to run them was simplified (cf `Improvment`)
17
+
* For security reason, since 1.20.0, only the clients using at least TLS 1.2 (released in 2008) can use chproxy with https.
18
+
19
+
#### New Feature
20
+
* Ability to decide whether the cache is specific per user or shared with all users (specific per user by default) [#258](https://github.com/ContentSquare/chproxy/pull/258)
21
+
* Ability to retry a failed query up to `retrynumber` times [#242](https://github.com/ContentSquare/chproxy/pull/242)[#269](https://github.com/ContentSquare/chproxy/pull/269)[#270](https://github.com/ContentSquare/chproxy/pull/270)
* Since 1.20.0, the BINARY argument is not needed to run docker images from [contentsquareplatform docker hub](https://hub.docker.com/r/contentsquareplatform/chproxy)
26
+
```
27
+
#new way:
28
+
docker run -d -v $(PWD)/testdata:/opt/testdata/ contentsquareplatform/chproxy:v1.20.0-arm64v8 -config /opt/testdata/config.yml
29
+
#old way:
30
+
docker run -d -v $(PWD)/testdata:/opt/testdata/ -e BINARY=chproxy contentsquareplatform/chproxy:v1.19.0-arm64v8 -config /opt/testdata/config.yml
Since 1.20.0, only the clients using at least TLS 1.2 (released in 2008) will be able to connect with chproxy in https [#276](https://github.com/ContentSquare/chproxy/pull/276)
34
+
35
+
#### Bug Fix
36
+
* By default the cache was shared with all users, which could led to situations where a user could access data he wasn't allowed to see (according to clickhouse rules). Now the cache is specific for each user [#258](https://github.com/ContentSquare/chproxy/pull/258)
0 commit comments