Skip to content
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

[RFC] Do not require settings declaration if server support setting-as-string #142

Merged
merged 1 commit into from
Jun 18, 2020

Conversation

azat
Copy link
Contributor

@azat azat commented Jun 15, 2020

New settings are added frequently, more then clickhouse-driver has new
release.

The downside is that bool type detection now depends from the server,
and it does not recognize 'yes'/'2', but recognize 'true'/'1', but I
guess it is ok.
(plus I'm not sure that it was a good idea to ignore case for char
settings, if the string has more then 1 char)

History of syncing settings with upstream:

New settings are added frequently, more then clickhouse-driver has new
release.

The downside is that bool type detection now depends from the server,
and it does not recognize 'yes'/'2', but recognize 'true'/'1', but I
guess it is ok.
(plus I'm not sure that it was a good idea to ignore case for char
settings, if the string has more then 1 char)
@azat
Copy link
Contributor Author

azat commented Jun 15, 2020

P.S. Looks like travis-ci does not work anymore? (Anyway all tests passed for upstream clickhouse-server)

@xzkostyan xzkostyan merged commit d625efa into mymarilyn:master Jun 18, 2020
xzkostyan added a commit that referenced this pull request Jun 18, 2020
@azat azat deleted the any-settings branch June 18, 2020 12:05
azat added a commit to azat-ch/clickhouse-driver that referenced this pull request Nov 25, 2020
azat added a commit to azat-ch/clickhouse-driver that referenced this pull request Nov 25, 2020
Skipping unknown settings is not always the required behaviour, and most
of the time you want the opposite - fail on unknown setting.

Image that you pass some new setting, i.e. max_insert_threads, and you
assume that the INSERT will be parallel, however due to you server was
too old the setting is silently ignored.

Refs: mymarilyn#142
azat added a commit to azat-ch/clickhouse-driver that referenced this pull request Nov 25, 2020
Skipping unknown settings is not always the required behaviour, and most
of the time you want the opposite - fail on unknown setting.

Image that you pass some new setting, i.e. max_insert_threads, and you
assume that the INSERT will be parallel, however due to you server was
too old the setting is silently ignored.

Refs: mymarilyn#142
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants