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

Presto Chart missing? #27

Closed
ckdarby opened this issue May 8, 2020 · 3 comments
Closed

Presto Chart missing? #27

ckdarby opened this issue May 8, 2020 · 3 comments

Comments

@ckdarby
Copy link

ckdarby commented May 8, 2020

@cgiraldo Came across on helm hub a repo for prestosql by you but went to fetch and got a nice little error that the release is missing :(?

helm fetch gradiant/prestosql --version 0.1.0
Error: failed to fetch https://github.com/Gradiant/charts/releases/download/prestosql-0.1.0/prestosql-0.1.0.tgz : 404 Not Found
@cgiraldo
Copy link
Member

cgiraldo commented May 9, 2020

Yes. The prestosql chart is a WIP that was released by mistake. It was removed by helmhub does not refresh the repository index.

I have added a prestosql branch with the prestosql chart source. You caninstall it from source and test it. Comments are welcome!

@cgiraldo cgiraldo closed this as completed May 9, 2020
@ckdarby
Copy link
Author

ckdarby commented May 12, 2020

Any reason why there isn't a catalog directory with just a basic blackhole or memory one? Is it just because the base docker container doesn't define either of these?

Were your plans to stop here mostly with what you're putting in the public chart or...?

Things I'd be interested in contributing to the chart:

  • Push the metastore to AWS glue & use hadoop2 for s3 access
  • Spill to disk enable option that sets up a lot of the volume kind of stuff

@cgiraldo
Copy link
Member

There is no reason to not add a catalog directory.

We are exploring presto and begin with the presto chart, but we should discuss how to configure connectors, through external configmap? parameters in values.yaml? both? other options?

So our plans are to continue chart development yo make a functional presto chart generic enough to be useful for the community. We are interested in hive-mestastore and want to make some tests with presto+hive-metastore+hdfs before releasing the helm chart.

And of course, contributions and discussions on how to arrange the chart are very welcome.

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

No branches or pull requests

2 participants