markhoerth opened a new pull request, #158:
URL: https://github.com/apache/gravitino-playground/pull/158
Add a Gravitino MCP server surface and broadly improve the playground's
reliability, notebooks, and documentation.
Infrastructure and startup:
- Fix a Gravitino container startup race on cold first run, where the
entrypoint tailed a log file before the JVM created it and exited, taking the
container down with it.
- Add hdfs-site.xml so HDFS clients resolve the datanode by hostname, fixing
cross-container Spark and Gravitino access to filesets.
- Add the Gravitino MCP server as an HTTP service on port 8000 with a health
check, on by default, opt out with --disable-mcp.
- Give playground.sh separate stop and down verbs with a fast resume path,
and persist the Ranger database in a named volume.
- Pass ANTHROPIC_API_KEY and OPENAI_API_KEY through to Jupyter, and ignore
.env and gv-logs.
Notebooks:
- Add gravitino-mcp-demo.ipynb (connect, list tools, governed agentic query)
and gravitino-gvfs-example.ipynb (governed unstructured-data access through
GVFS).
- Rework the access control notebook to demonstrate real Ranger denial in a
single Spark session with no kernel restart, using a table ownership transfer
so role changes are enforced.
- Make the existing notebooks idempotent and reliable: quiet installs,
pinned dependencies, fully-qualified table names, cleaner output.
Documentation:
- Rewrite README.md around a value-first structure: overview, getting
started, notebooks, then tool sections each teaching a Gravitino capability,
with reference material at the end and links to the docs.
<!--
1. Title: [#<issue>] <type>(<scope>): <subject>
Examples:
- "[#123] feat(operator): support xxx"
- "[#233] fix: check null before access result in xxx"
- "[MINOR] refactor: fix typo in variable name"
- "[MINOR] docs: fix typo in README"
- "[#255] test: fix flaky test NameOfTheTest"
Reference: https://www.conventionalcommits.org/en/v1.0.0/
2. If the PR is unfinished, please mark this PR as draft.
-->
### What changes were proposed in this pull request?
(Please outline the changes and how this PR fixes the issue.)
### Why are the changes needed?
(Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, describe the bug.)
Fix: #(issue)
### Does this PR introduce _any_ user-facing change?
(Please list the user-facing changes introduced by your change, including
1. Change in user-facing APIs.
2. Addition or removal of property keys.)
### How was this patch tested?
(Please test your changes, and provide instructions on how to test it:
1. If you add a feature or fix a bug, add a test to cover your changes.
2. If you fix a flaky test, repeat it for many times to prove it works.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
