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

Decide on sharding function for distribbuted table #35

Open
pavolloffay opened this issue Jul 27, 2021 · 2 comments
Open

Decide on sharding function for distribbuted table #35

pavolloffay opened this issue Jul 27, 2021 · 2 comments

Comments

@pavolloffay
Copy link
Member

The distributed table could be created with multiple sharding functions: rand(), cityHash64(traceID) - see https://clickhouse.tech/docs/en/sql-reference/functions/hash-functions/.

The hash functions take an argument, we should consider using traceID to keep data from a single trace in the same location.

CREATE TABLE IF NOT EXISTS jaeger_spans AS jaeger_spans_local ENGINE = Distributed('{cluster}', default, jaeger_spans_local, cityHash64(traceID));
@pavolloffay
Copy link
Member Author

@chhetripradeep would you like to take this on and run some tests on your deployment?

@chhetripradeep
Copy link
Contributor

Sure.

@pavolloffay pavolloffay changed the title Decine on sharding function for distribbuted table Decide on sharding function for distribbuted table Jul 27, 2021
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

No branches or pull requests

2 participants