Client Applications


Updated: April 16, 2021

Welcome to the Release Notes for Nuxeo Drive 5.1.0

Status: Release

Important Changes

Direct Transfer

Status Change

The Direct Transfer feature is now enabled by default.

 More on JIRA ticket NXDRIVE-2537

CSV Export Capability for Direct Transfer Sessions

It is now possible for the user to export a Direct Transfer session to a CSV file. When a session is completed, a link will appear, allowing the user to generate an export on demand. The created CSV file contains default filled fields that make it directly usable in the Nuxeo CSV importer.

 More on JIRA ticket NXDRIVE-2382


Usage Metrics

Usage metrics have been added using custom HTTP headers. Those metrics are only and exclusively sent to the platform when the application calls specifics operations or endpoints. Some of those metrics are sent in a specific process to avoid spamming the platform and can be disabled through the custom-metric parameter.

 More on JIRA ticket NXDRIVE-2476


Improved Stability of S3 Direct Uploads

We fixed a tricky issue when S3 direct upload was enabled for the synchronization. It was generating false conflicts and duplicates documents errors. The synchronization is now fully "safe", just as the synchronization using the default upload provider.

We also improved non-chunked S3 direct uploads by removing one HTTP call for each and every upload.

See NXPY-204 and NXPY-205 for additional details.

 More on JIRA ticket NXDRIVE-2479

Preventing Crashes

The issue was not visible quickly but when Drive was running a long time with a lot of synchronization actions. Each thread was opening multiple connections to the SQLite database, but they were never released. Resulting in an increase of the number of opened file descriptors and it was consuming more and more memory (RAM). Both situations were ending with a hard crash: the OS was killing the application in both cases.

 More on JIRA ticket NXDRIVE-2523

Preventing Server Deletions

In Nuxeo Drive 4.1.0 we introduced a "deletion behavior" to change the way file deletions are impacted on the server (cf NXDRIVE-1501). It appeared to be effective only when the application was running.

But it will not be taken into account when files were deleted while the application was not running. In that scenario, when the chosen deletion behavior was to simply unsynchronize documents, it would just delete files on the server.

That is now fixed and in such scenario, if the user did not choose any deletion behavior, then the default action will be to unsynchronize files to prevent unwanted remote deletions.

 More on JIRA ticket NXDRIVE-2538

We'd love to hear your thoughts!

All fields required