Skip to main content
nx1-deployer image 1.17.0
The October 2026 release for web portal users introduces Data APIs v2. You can now publish a deployed semantic model or a table as a versioned API from a new catalogue at Connect > APIs. Its contract and context travel with it. This release also lets NexusOne draft a Ranger masking policy for a sensitive column automatically, instead of you writing one by hand. It also embeds Grafana dashboards in the portal, adds Keycloak sign-in for Airflow and the Kyuubi Web UI, and lets an administrator turn on Elyra per tenant. Finally, this release stops portal-generated Airflow DAGs from overwriting manually deployed ones, and tightens the Ranger permission check for deleting objects in the JupyterHub S3 browser.

New features

This section contains new features recently added to the NexusOne platform.

Data APIs v2

Data APIs are now published, versioned APIs. You build one from a deployed semantic model or a table, never from free-form SQL. Each version freezes a contract, so an API doesn’t change underneath the people and agents that call it. A contract covers:
  • Grain and keys, meaning what one row represents
  • Columns and what each one means
  • Filters, sorts, and page limits
  • Worked examples of calling the API
  • An optional pinned context pack
The following sections cover how agents reach an API, what ships alongside its data, how you publish and manage one, and how it handles access.

Agent access

Agents can reach Data APIs through three new read-only MCP tools:
  • dataapi_list
  • dataapi_context
  • dataapi_query
See Data APIs v2 for how Data APIs work when you call them outside the portal.

Context ships with the data

Every API ships its context alongside its data, so whoever calls it knows what they’re looking at. This context envelope holds two kinds of information:
  • Pinned at publish: The contract, plus DataHub owners, terms, lineage, links, and properties.
  • Live state: Freshness, incidents, deprecations, profile, and data quality.
The context envelope is available as JSON, as markdown for agents, and as the Open Data Contract Standard (ODCS) v3. Each version also has its own OpenAPI spec.

Publish and manage an API

You can reach the feature at Connect > APIs. It’s a catalogue of every published API, with a publish flow for creating a new one. Opening an API takes you to its workspace, which has these tabs:
  • Overview
  • Contract editor
  • Context
  • Try it
  • Usage
The previous view-based API moves to Connect > Legacy, unchanged.

Secure by default

Every call runs as the user who made it, so Ranger decides what that user can see. In practice, this means:
  • The response drops columns the caller can’t select from both the results and the context.
  • The response names masked columns, so the caller knows they’re masked.
  • You can’t filter or sort sensitive columns.
Because every call needs to identify one user, a Data API refuses the shared platform PSK.

Bug fixes

This section contains fixes for issues affecting apps or features on the NexusOne platform.

JupyterHub S3 now checks for delete permission

Deleting or moving an object in the JupyterHub S3 browser, or deleting one with s3Cli rm, only checked for Ranger write permission. A user who could write to a bucket could also delete from it. This release requires delete permission for those actions instead.
If you could delete or move objects before with only write permission, then you can’t after this release. Ask your administrator for delete permission on the buckets you need.

Portal-generated Airflow DAGs no longer overwrite manually deployed ones

Airflow DAGs on NexusOne come from two sources:
  • Portal-generated: The NexusOne portal creates some DAGs for you automatically.
  • Manually deployed: You write and deploy your own DAGs in either of these ways:
    • Upload DAG files to the Airflow DAGs folder in S3.
    • Publish a pipeline’s DAG from Elyra.
Portal-generated and manually deployed DAGs used to share the same storage location, called a DAG bundle. Redeploying one with the same name could silently overwrite the other. In this release, portal-generated DAGs now live in their own bundle, separate from anything you deploy manually.

Other fixes

  • Airflow sign-in: Fixed failed sign-ins after Keycloak’s signing key changed. Airflow now retrieves the key on each login.
  • Spark history UI: Fixed the link to OpenLineage.
  • DataHub: Fixed a startup crash.

Enhancements

This section contains enhancements to existing app features on the NexusOne platform.

AI-assisted policy generation

Sensitive columns, like ones tagged PII or Payment Card Industry (PCI), need a Ranger policy to mask or restrict them. Writing one by hand for every column doesn’t scale. NexusOne can now draft that policy for you automatically. However, nothing reaches Ranger until you review and accept a suggestion. You can reach the feature at Govern > Data access. Request suggestions for a table or a whole schema, then accept or reject them at the batch or individual level.

Connect Claude through your AWS account

The AI Control Plane’s Endpoints editor now lets you add an endpoint for Claude Platform on AWS, instead of only the public Anthropic API. This matters if your AI traffic needs to stay inside your own cloud for compliance reasons. You can reach it at AI > AI Control Plane > Admin > Add endpoint, using the new Claude Platform on AWS preset. See Connect existing Claude integrations through AWS for how an administrator sets the initial Claude on AWS endpoint at deploy time.

DataHub

DataHub is now on 1.7.0.1, and it turns on two features that were previously off:
  • Business attributes
  • Metrics

Elyra access by role

The Elyra pipeline editor in JupyterHub is now configured per tenant. An administrator turns it on for a tenant’s users by assigning the new nx1_jupyterhub_elyra Keycloak role.

Grafana dashboards in the portal

Grafana dashboards now embed directly in the portal, so you can view a tenant’s dashboards without leaving it.

JupyterHub session timeout and notebook images

An administrator can now set the following per tenant:
  • How long an idle notebook server and its kernel run before NexusOne shuts them down. The default is one hour.
  • Which notebook image tags are available to a tenant’s users. See JupyterHub for how an administrator sets both.

Keycloak sign-in for Airflow and the Kyuubi Web UI

You can now sign in to both of these directly through Keycloak:
  • Airflow
  • Kyuubi Web UI

Platform component upgrades

This release upgrades several components you work with in the portal, including Trino to nx1-483.1.6, Kyuubi to 1.12.16, and Airflow to 3.3.11. See Image versions for every image that changed in this release.