Skip to content

add Apache Comet #557

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

Draft
wants to merge 19 commits into
base: main
Choose a base branch
from

Conversation

Iskander14yo
Copy link

This PR adds Apache Comet as a backend for Spark in analytical workloads. Base issue - #517.

Notes:

  • I did not rewrite the queries as initially proposed in the issue. This can be done later — for now, I’d like to focus on verifying setup correctness.
  • I tried to reuse existing Spark code in the form of copy-paste-document.

Also I consider creating issue in Comet repo for devs to double-check my configuration. This is especially important since there are 1 query that failed and other questionable moments. Meanwhile, I'd glad to hear comments from interested.

@CLAassistant
Copy link

CLAassistant commented Jul 17, 2025

CLA assistant check
All committers have signed the CLA.

@@ -0,0 +1,236 @@
{
Copy link
Member

Choose a reason for hiding this comment

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

These machine types were measured for Spark: c6a.2xlarge.json c6a.4xlarge.json c6a.xlarge.json c8g.4xlarge.json

Do you plan to add them as well or do you like me to do this?

Copy link
Author

Choose a reason for hiding this comment

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

I can probably run that too after we finalize discussion on the PR.

@Iskander14yo

This comment was marked as resolved.

@Iskander14yo
Copy link
Author

@rschu1ze Currently I'm solving AWS issues related to my account and I don't know how long this will take. If you have an opportunity to run bench yourself I'd appreciate it. Otherwise I'll run it myself as soon as possible.

@rschu1ze
Copy link
Member

The PR LGTM. It will be hard for me to capture measurements on c6a.2xlarge.json, c6a.4xlarge.json, c6a.xlarge.json, and c8g.4xlarge.json in the next 1.5 weeks but if you find some time, please go ahead. Otherwise or if this is urgent, I can also merge this PR (just lmk).

@alexey-milovidov
Copy link
Member

@rschu1ze, we have the automation - please go ahead and merge. Then we can run on any machines in a matter of a single command.

@Iskander14yo
Copy link
Author

@alexey-milovidov current VM's (c6a.4xlarge) results should be re-run too since last changes.

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.

4 participants