You are browsing the docs for Nexus v1.6.x, the latest release is available here
Releases
This section of the documentation lists the significant BlueBrain Nexus releases across all services and web applications.
The latest stable release is v1.6.1 released on 29.10.2021.
v1.6.1
This release contains bugfixes and minor improvements:
- Graph-analytics returns edges for non-existing nodes #2871
- Graph analytics is trying to resolve every link to all types of resources #2852
- Composite key values cache is not distributed across nodes #2909
- Shortcut Acl permission check (project -> org -> root) when address matches early #2916
- Resource-view opens up as a side panel #2617
- User can see all data, when the search query is empty #2875
- A loading spinner shows up when there is a delay in fetching search results #2880
- Label ‘none of’ in filter was previously mis labelled as ‘any of’ #2872
- The behaviour of ‘none of’ filter has been fixed to avoid confusion with other filters #2898
- Preview plugin big fix to prevent it from crashing for certain file paths #2884
- Search bar matches query content #2874
Full Changelogs:
- Delta: v1.6.0…v1.6.1
- Fusion: v1.6.0…v1.6.1
v1.6.0 (13.10.2021)
Deprecations
New features / enhancements
- Introduced a plugin to search among different projects
- Introduced PDF, CSV, TSV and Youtube Viewer Fusion Plugins
- Add basic authentication to access a secured Elasticsearch cluster
- Handle user-defined queries to Blazegraph with a dedicated client
- Introduced a plugin to analyze properties and relationships of resources within a project
- Synchronous indexing
- Listing of resources outside the project scope
- The RDF parser to validate resources is now configurable
- Automatic project provisioning
- Introduced quotas on projects
- Project deletion (on demand and automatic)
- Tagging resources after deprecation
- View passivation
A detailed list of changes included in the release can be found in the release notes.
v1.5.1 (04.06.2021)
This release contains bugfixes and minor improvements:
- File paths now respect tar spec, added n-quads format option to archives #2459
- Use service account to unset previous default storage #2465
- Support type query exclusion on listings #2468
- Added organization events to SSEs #2477
- Allow the deletion of some persistence ids at startup #2480
- Prevent creating schemas starting with
schemas.base
#2481 - Updated the default number of shards value to 50 (prev => 1000) #2490
- Expose indexing metrics #2485
- Clean up error messages #2497
- Allow plugins to be disabled via configuration #2498
- Consume the entire base URI path in the routes #2502
- Update progress cache on stream start. #2505
- Fetch org/project events from their creation time if none is provided #2500
- Count view statistics deterministically. #2509
- Add SHACL context to resource/schemas errors including SHACL report #2508
v1.5.0 (19.05.2021)
The release is backwards compatible with v1.x.y releases in terms of API (except for some issues that were corrected - please see the release notes for the exact changes). If you’re upgrading from v1.4.x please visit the migration instructions.
Summary of the significant changes:
- Introduced the ability to define workflows in Fusion;
- Introduced support for plugins in Delta;
- Remote context and
owl:imports
resolution is executed during creation and update providing full resource immutability; - Consistent JSON-LD support across all endpoints and resource types;
- Support for named graphs;
- Specific SSE endpoints for Delta managed resource types (schemas, resolvers, storages, files and views);
- Views can be configured with the required permission for querying;
- CrossProject resolvers can be configured with
useCurrentCaller
that enables resource resolution with the caller identities instead of a fixed identity set; - ElasticSearch views can be configured with
settings
(this allows the customization of ElasticSearch index with number of shards and replicas, tokenizers, filters etc.).
A detailed list of changes included in the release can be found in the release notes.
v1.4.2 (20.10.2020)
This is a bugfix release, addressing the following issues related to views lifecycle:
- Persist project statistics to avoid starting from NoOffset when service restarts or view collapses.
- Prevent a deprecated organization/project from starting its views.
v1.4.1 (24.08.2020)
This is a bugfix release, addressing the following issues:
- Project tag reported as a metric with Kamon is inconsistent
- File Attribute computation is no longer exposed as a metric
- The path prefix read from the app.http.public-uri is applied twice for KG specific routes
- Parallelize the v1.3.x to v1.4.x migration script
- Support a retry mechanism for the v1.3.x to v1.4.x migration
- Add email address in footer
- Add CONP and SWITCH logos on product page
- Add SEO metadata to product pages
- Add SEO headers
v1.4.0 (14.08.2020)
The release is backwards compatible with v1.x.y releases in terms of API. If you’re upgrading from v1.3.x please visit the migration instructions.
Summary of the significant changes:
- Merged iam, admin and kg services into a single service, called
delta
; - Listings API now shows - besides resources metadata - the following predicates, when present: sko:prefLabel, schema:name, rdfs:label;
- Nexus Web has evolved into Nexus Fusion, supporting multiple subapps and making the different sections clear for our users;
- Greatly improved design for the way Nexus Fusion manages plugins;
- Introduction of Nexus Forge in the ecosystem. Nexus Forge is currently at version 0.3.3.
A detailed list of changes included in the release can be found in the release notes.
v1.3.0 (25.02.2020)
The release is backwards compatible with v1.x.y releases in terms of API. If you’re upgrading from v1.2.x please visit the migration instructions.
Summary of the significant changes:
- Introduced a new type of view (_CompositeView_, currently as a Beta feature) that expands on the indexing capabilities of the system through the ability to consume multiple sources (multiple projects in the same Nexus deployment and projects in different Nexus deployments);
- Added the ability to generate tabular views on the data available to a specific project (using any SparqlView defined in the project - default SparqlView or AggregateSparqlViews) by means of Studios and Dashboards in Nexus Web;
- Allow querying SparqlViews using the GET http method;
- Exposed a new view subresource
.../offset
that presents the current view offset, or collection of offsets in case of CompositeViews. The offset has the same value used with Server Sent Events as means of keeping track of the current event replay progress. Deleting this resource with instruct the system to rebuild the indices of the selected view; - Ordering results when doing listings can now be controlled with the repeated
sort
query param that accepts ElasticSearch document field names (...?sort=_createdAt&sort=-_createdBy
). The ordering defaults to ascending, but can be switched for descending by prefixing the-
character to the field name. - New ElasticSearch indices are automatically configured to perform word split and properly handle UUIDs. The new configuration yields better full text search results.
- Nexus Web - Adds the ability to have persistent customisable queries and data visualizations for your data via the new Studios feature
A detailed list of changes included in the release can be found in the release notes.
v1.2.1 (07.10.2019)
This is a bugfix release, addressing two specific issues:
- Fix
FileAttributesUpdated
event deserialization which was causing indexing problems for situations where the deployment included a remote storage service to handle files. - Removed
kamon-akka-remote
dependency which was causing problems in clustered deployments due to binary compatibility issues.
v1.2.0 (04.10.2019)
The release adds two major features:
- endpoint to fetch the original payload of a resource.
- ability to retrieve multiple resources in one request as an archive.
The API is backwards compatible with v1.1.
Summary of the significant changes:
Storage service related updates:
- Updated async computation of to return not only the digest information but all the attributes (bytes, digest, mediaType and location).
KG updates:
- Added archives resources.
- Added /source sub-resource.
- Fixed issue with resource retrieval when linked context changes.
- Updated
DigestViewCoordinator
toAttributesViewCoordinator
. This async process now updates all the FileAttributes.
Dependency updates:
- SHACL validator, akka-http, cats, cats-effects amongst others
v1.1.2 (24.09.2019)
The release addresses bug fixing and is backwards compatible with v1.0 in terms of API. If you’re upgrading from v1.0 please visit the migration instructions.
Summary of the significant changes:
Storage service related updates:
- Added async computation of the file digest.
- Before an action gets executed against the storage, checks that the resource created is valid (is not deprecated, has the correct revision, etc…)
KG Fixes:
- When project is not present in the cache but it is present in the underlying admin service, adds it directly to the cache (before the cache was populated from the SSE, which can be very slow).
ProjectViewCoordinator
andDigestViewCoordinator
actors now create child actors (better management of actors lifecycle).- Prevented from creating unnecessary indices/namespaces.
Fixed library dependency issues:
- Corrected Iri to Akka.Uri conversion
- Corrected pct encoding (Iri.asString and Iri.asUri)
- Bumped akka and kamon dependencies, amongst others
v1.1.1 (24.07.2019)
The release addresses bug fixing and is backwards compatible with v1.0 in terms of API. If you’re upgrading from v1.0 please visit the migration instructions.
Summary of the significant changes:
- Migration script correctly updates views with the expected defaults
- Migration script jumps over event deserialization errors
- Metric tag value fix for elasticsearch indexer
- Kamon disabled by default
- Kamon agent is loaded as a JVM argument
- Updated library dependencies
v1.1 (19.07.2019)
The release is backwards compatible with v1.0 in terms of API. If you’re upgrading from v1.0 please visit the migration instructions.
Summary of the significant changes:
- Exposed the service event logs over a stable API via Server Sent Events.
- Introduced configurable storage backends for files with local, remote and S3 implementations.
- ElasticSearchView | AggregateElasticSearchView have been promoted to stable.
- Introduced a new SPARQL view, AggregateSparqlView, that dispatches SPARQL queries to the appropriate namespaces and aggregates the results.
- ElasticSearchView and SparqlView support additional configuration options: resourceSchemas, resourceTypes, resourceTag, includeDeprecated, includeMetadata.
- API improvements:
- Support for additional filtering criteria when listing resources via query params: rev, deprecated, createdBy, updatedBy.
- The organization and project segments when exercising the API now accept their unique ids (UUID).
- Content negotiation for resources, supporting: dot, ntriples, json-ld expanded and compacted formats.
- Ability to resolve resource ids via configured project resolvers.
- Pagination of resources over 10,000 using the ’‘_next’’ link in the listing response.
- Resource metadata includes ’‘_incoming’‘ and ’‘_outgoing’’ links and the API now includes their respective endpoints.
- View indexing progress as a ‘‘statistics’’ sub-resource of each view.
- Nexus Web improvements:
- Better OpenIdConnect integration, ability to authenticate to multiple configured realms.
- Ability to discriminate between Nexus specific resources and user managed resources.
- Display the current ACLs and their source for the logged in user.
- Ability to query user defined views.
- Display the indexing progress for the active view.
- Exposed view indexing progress metrics for Prometheus.
- Bumped ElasticSearch compatibility to 7.x.
A detailed list of changes included in the release can be found in the release notes.
v1.0 (25.01.2019)
This is the first major release of Blue Brain Nexus after almost two years of development.
Also referred to as “Nexus V1”, this initial release is our first big milestone in our quest to build a Knowledge Graph platform uniquely combining flexible graph database, powerful search engine and scalable data store to enable:
- Easy unification and integration of fragmented and disparate data from heterogeneous domains to break data and metadata silos
- Better data governance with the ability to specify and enforce organization’s best practices for data collection, storage and description through high quality metadata
- Data lineage and provenance recording and description
- FAIR (Findable, Accessible, Interoperable, Re-usable) data and metadata management
A detailed list of changes included in the release can be found in the release notes.