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

Allowed space between number and unit in time span #387

Open
wants to merge 591 commits into
base: Kusto-phase3
Choose a base branch
from

Conversation

bhavnajindal
Copy link

Issue: https://github.ibm.com/ClickHouse/issue-repo/issues/3149

Changelog category (leave one):

  • Bug Fix (user-visible misbehavior in an official stable release)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Allowed space between number and unit in time span

  • Example use: A query or command.
    print time(1 h)
    SELECT toIntervalNanosecond(3600000000000) AS print_0

bhavnajindal and others added 24 commits August 3, 2023 10:30
* check for accepted values for accuracy in dcount,dcountif

* Added functional Testacse and fixed the error msg
…edoc

Kusto-phase3: support arbitrary heredoc for kql table function
…382)

* fix-3091 added simple mapping for constatnt expressions

* fixed unit tests

* added testcase for negetive array index
* I2527: Fixed NaN issue in variance functions

* Fixed 2518
* Added meaningful exception

* check datetime year in range

* Moved Date out of range check to Kql_datetime native function

* Added try-ctach block for DateTime conversion to be within range
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.

7 participants