Incoming reports clustering by similarity #86
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ksy36
force-pushed
the
incoming_clustering
branch
from
9984818 to
1ce7f27
Compare
ksy36
force-pushed
the
incoming_clustering
branch
from
1ce7f27 to
c515179
Compare
Collaborator
Author
|
I need to find a way to run |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes in this PR:
import_reports_from_bigquerycommand assigns only low quality reports to a default by domain bucket, the rest of reports are saved to db without cluster_id or bucket_idtriage_new_reportscommand gets reports that don't have bucket_id and attempts to cluster and bucket them (runs every hour at the moment)I think once we import live reports the frequency of triaging can be increased.