Repository navigation
Release 3.3.0 #2403
kmcginnes
announced in
Announcements
Release 3.3.0
#2403
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Connecting to your database should be the easy part, and for a long time it wasn't. You had to tell Graph Explorer where its own server lived, tick a "Using Proxy-Server" checkbox that never explained itself, and make sure two different URLs lined up. Release 3.3.0 removes all of that. Graph Explorer now finds its own server, so a new connection is just a name, a database URL, and a query language.
The rest of the release builds on that. Other tools can now send you a link that opens Graph Explorer already pointed at your data. One Docker image serves every deployment, SageMaker notebooks included. Edge discovery finishes on the largest Neptune graphs, and error messages now tell you what went wrong and what to do about it.
Simpler Connections
Connection Links
If you build tools around your graph, you can now hand people a link that opens Graph Explorer already pointed at the right database. Nobody has to copy URLs or walk through the connection form.
See Connection Links for the parameters and matching rules.
One Docker Image
There used to be two Docker images, one for SageMaker notebooks and one for everything else. Now there's one.
sagemaker-*tags are still published as aliases of the standard image.NEPTUNE_NOTEBOOK=truenow sets port 9250, CloudWatch logs, and HTTP when the container starts./explorerwithout a trailing slash no longer redirects you to the proxy's root.Large Graphs
Release 3.2.2 was about scale, and this release keeps going.
Layouts Per Tab
Release 3.2.0 gave each browser tab its own connection. Layouts now follow the same rule.
Proxy Server Safeguards
The proxy server sits between your browser and your database, so it checks where it sends requests and says what it's doing.
PROXY_SERVER_ALLOWED_DB_ORIGINSis set, it logs a warning. A request to an origin outside the allowlist now gets an error that names the setting.NEPTUNE_NOTEBOOKandPROXY_SERVER_HTTPS_CONNECTIONare both true, or when it can't write to its configuration folder. Before, these failed with a misleading error.Clearer Error Messages
An error message is only useful if it points you toward the fix.
Bug Fixes
Error.isError(thanks @mjuarros!).Documentation
Graph Explorer has no sign-in of its own, so the docs now put access control up front.
Upgrade Notes
Existing deployments need no configuration change.
PUBLIC_OR_PROXY_ENDPOINTandUSING_PROXY_SERVERare still honored. A few things do behave differently:/explorerpath, so hosting the UI on a different origin from the proxy server no longer works. A reverse proxy must forward the/explorersegment intact; renaming it shows "Reverse proxy misconfigured".sagemaker-*tags no longer bake in notebook defaults. PassNEPTUNE_NOTEBOOK=trueto keep port 9250 and CloudWatch logs. The SageMaker lifecycle script already does. On the standard image,NEPTUNE_NOTEBOOK=truenow applies the same preset, so setPROXY_SERVER_HTTP_PORTif you want a different port./gremlinroute readsgremlinfrom the request body instead ofquery. Reload any browser tab left open across the upgrade. Anything else that posts to this route needs the same change.All Changes
New Contributors
Welcome and thank you to our first-time contributors!
Full Changelog: v3.2.2...v3.3.0
This discussion was created from the release Release 3.3.0.
All reactions