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

feat: add noop ceramic-olap binary #482

Merged
merged 3 commits into from
Aug 19, 2024
Merged

feat: add noop ceramic-olap binary #482

merged 3 commits into from
Aug 19, 2024

Conversation

nathanielc
Copy link
Collaborator

The ceramic-olap binary copies verbatim some setup code from ceramic-one re tracing/logging/metrics. Eventually this may move back into the ceramic-one binary or we can find a way to make it generic and reuse. Given this is only the first copy of the code I don't think we should work to make it generic yet. Not until we either decide this is the long term home for the ceramic-olap binary or have a third binary we want to have a similar setup.

This binary does nothing yet except start tracing/logging/metrics and then wait for a signal to shutdown gracefully.

The ceramic-olap binary copies verbatim some setup code from ceramic-one
re tracing/logging/metrics. Eventually this may move back into the
ceramic-one binary or we can find a way to make it generic and reuse.
Given this is only the first copy of the code I don't think we should
work to make it generic yet. Not until we either decide this is the long
term home for the ceramic-olap binary or have a third binary we want to
have a similar setup.

This binary does nothing yet except start tracing/logging/metrics and
then wait for a signal to shutdown gracefully.
@nathanielc nathanielc requested a review from a team as a code owner August 15, 2024 19:26
@nathanielc nathanielc requested review from dav1do and removed request for a team August 15, 2024 19:26
@AaronGoldman
Copy link
Contributor

A lot of metrics for a no-op but looks good.

#[arg(
short,
long,
default_value = "127.0.0.1:9464",
Copy link
Contributor

Choose a reason for hiding this comment

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

I know this is standard, but wondering if we want a different default if we expect c1 and olap to run on one machine?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good point, its easy to change later and there might be a few things like that to change.

@nathanielc nathanielc added this pull request to the merge queue Aug 19, 2024
Merged via the queue into main with commit 92b9c44 Aug 19, 2024
5 checks passed
@nathanielc nathanielc deleted the feat/olap-shell branch August 19, 2024 16:05
@smrz2001 smrz2001 mentioned this pull request Aug 19, 2024
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.

3 participants