Skip to content

Ngram classify#50247

Closed
AntonGorokhov wants to merge 16 commits intoClickHouse:masterfrom
AntonGorokhov:NgramClassify
Closed

Ngram classify#50247
AntonGorokhov wants to merge 16 commits intoClickHouse:masterfrom
AntonGorokhov:NgramClassify

Conversation

@AntonGorokhov
Copy link
Copy Markdown

Changelog category:

  • New Feature

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

Ngram Classification function added, so that user can SELECT smth with it

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@AntonGorokhov
Copy link
Copy Markdown
Author

Hello, this is my pull request. Not everything is done yet.
I am about to finish it in couple of days

Copy link
Copy Markdown
Member

@qoega qoega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it still work in progress? Do you plan to add perf and stateless tests?

.zshrc Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added accidentally?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, added accidentally

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also not needed if you don't use it in test? If needed in test, maybe put it in contrib and add LICENSE file?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These files are going to be used as Ngram Models inside ClickHouse. What should I do to register them?

@AntonGorokhov
Copy link
Copy Markdown
Author

Yes, work is still in progress

@alexey-milovidov alexey-milovidov added the can be tested Allows running workflows for external contributors label May 27, 2023
@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-feature Pull request with new product feature label May 27, 2023
@robot-ch-test-poll2
Copy link
Copy Markdown
Contributor

robot-ch-test-poll2 commented May 27, 2023

This is an automated comment for commit 4ccc0ad with description of existing statuses. It's updated for the latest CI running
The full report is available here
The overall status of the commit is 🔴 failure

Check nameDescriptionStatus
AST fuzzerRuns randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help🟢 success
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR🟡 pending
ClickHouse build checkBuilds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process🟢 success
Compatibility checkChecks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help🟢 success
Docker image for serversThe check to build and optionally push the mentioned image to docker hub🟢 success
Docs CheckBuilds and tests the documentation🟡 pending
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here🟢 success
Flaky testsChecks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc🔴 failure
Install packagesChecks that the built packages are installable in a clear environment🟢 success
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests🟢 success
Mergeable CheckChecks if all other necessary checks are successful🔴 failure
Performance ComparisonMeasure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests🟢 success
Push to DockerhubThe check for building and pushing the CI related docker images to docker hub🟢 success
SQLancerFuzzing tests that detect logical bugs with SQLancer tool🟢 success
SqllogicRun clickhouse on the sqllogic test set against sqlite and checks that all statements are passed🟢 success
Stateful testsRuns stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🟢 success
Stateless testsRuns stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc🔴 failure
Stress testRuns stateless functional tests concurrently from several clients to detect concurrency-related errors🟢 success
Style CheckRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report🟢 success
Upgrade checkRuns stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts🟢 success

@AntonGorokhov AntonGorokhov force-pushed the NgramClassify branch 3 times, most recently from 33e5a60 to 4a66f71 Compare May 29, 2023 16:47
@AntonGorokhov
Copy link
Copy Markdown
Author

Please explain me how to declare /opt directory with models that I added in a proper way

@AntonGorokhov AntonGorokhov force-pushed the NgramClassify branch 3 times, most recently from f973a37 to 6842a88 Compare May 29, 2023 20:34
@AntonGorokhov AntonGorokhov force-pushed the NgramClassify branch 2 times, most recently from 66df0a5 to ec19e7a Compare May 29, 2023 21:02
@@ -0,0 +1,72 @@
Дон ли, Волга ли течёт котомку на плечо
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's probably copyrighted, and I don't think it's fair use.

@rschu1ze rschu1ze self-assigned this Jun 27, 2023
@alexey-milovidov
Copy link
Copy Markdown
Member

This is not as discussed. The model file should contain (class_id, ngram, count) triples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

can be tested Allows running workflows for external contributors pr-feature Pull request with new product feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants