Skip to content

Added link to the Spark-Jupyter Notebook Getting Started from the main Getting Started Page #1453

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.

Sign up for GitHub

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

Merged
eric-maynard merged 4 commits into from
Apr 28, 2025
Merged

Added link to the Spark-Jupyter Notebook Getting Started from the main Getting Started Page #1453

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
991fbef
Added link to the Spark-Jupyter Notebook Getting Started from the mai…
adnanhemani Apr 24, 2025
477e525
Typo
adnanhemani Apr 25, 2025
3ee821b
Suggestions as per @eric-maynard's review
adnanhemani Apr 25, 2025
8571c07
Fix Typo
adnanhemani Apr 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions site/content/in-dev/unreleased/getting-started/using-polaris.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,6 +231,8 @@ INSERT INTO quickstart_table VALUES (1, 'some data');
org.apache.iceberg.exceptions.ForbiddenException: Forbidden: Principal 'quickstart_user' with activated PrincipalRoles '[]' and activated grants via '[quickstart_catalog_role, quickstart_user_role]' is not authorized for op LOAD_TABLE_WITH_READ_DELEGATION
```

Additionally, a Getting Started experience for using Spark with Jupyter Notebooks is documented [here](https://github.com/apache/polaris/blob/main/getting-started/spark/README.md).
Copy link
Contributor

@eric-maynard eric-maynard Apr 25, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

reviving a comment:

Also, this line looks kind of random more generally. This doesn't seem related to the above despite saying Additionally,.

Maybe we can break out a new header called like Beyond the Quickstart or Next Steps or whatever and put this (and other relevant links) there.

Copy link
Contributor Author

@adnanhemani adnanhemani Apr 25, 2025

Choose a reason for hiding this comment

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

Context: I was talking to @flyrain offline and he had mentioned that he'd like us to provide a link to the Jupyter Notebook experience from the main Quickstart experience where users can explore further.

The issue with the Jupyter Notebook Getting Started is that it does not have the same amount of feature-richness as this main Getting Started page (no support for Postgres DB or Cloud Blob Storage) - so we're referring to it as an example of how to append to the current Docker Compose file.

I'm not opposed to putting a Next Steps header at the end, but today I think we will only have two links: 1) this and 2) Deploying Polaris in Production. Additionally, @flyrain would like to separate out Spark, Trino, and eventually Flink into their own pages. Do you think it's worth it to create that section at the end for two links? And I'm also slightly worried that if we do separate the engines into their own children pages, then where would this new "Next Steps" page go?

Copy link
Contributor

@eric-maynard eric-maynard Apr 25, 2025

Choose a reason for hiding this comment

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

This is under the Sample Commands header where it just doesn't really belong.

I think it's fine if Next Steps is pretty thin

Copy link
Contributor Author

@adnanhemani adnanhemani Apr 25, 2025

Choose a reason for hiding this comment

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

Sounds good, will add the section and revise this PR.


### Connecting with Trino

Replace the credentials used in the Docker container using the following code:
Expand Down