-
Type: Task
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 5.9.5
-
Fix Version/s: Postponed
-
Component/s: Nuxeo Drive
-
Tags:
Since NXP-14826 the audit log query is based on a range delimited by auto-incremented event log ids instead of timestamps.
We kept the former API for backward compatibility, but will probably want to remove it at some point.
Need to take into account at least the following code.
- Server-side:
NuxeoDriveGetChangeSummary#run
NuxeoDriveManager#getChangeSummary(Principal principal, Map<String, Set<IdRef>> lastSyncRootRefs, long lastSuccessfulSync)
FileSystemChangeFinder#getFileSystemChanges(CoreSession session, Set<IdRef> lastActiveRootRefs, SynchronizationRoots activeRoots, long lastSuccessfulSyncDate, long syncDate, int limit) FileSystemChangeFinder#getCurrentDate()
AuditChangeFinder#getJPARangeClause
- Client-side:
BaseAutomationClient.fetch_api BaseAutomationClient.is_event_log_id_available RemoteFileSystemClient.get_changes Synchronizer._get_remote_changes Synchronizer._checkpoint Synchronizer.update_synchronize_server
- depends on
-
NXP-14826 Drive: change summary might miss some event if its logDate is not yet commited by the DB in the audit table when the query for changes is run
- Resolved
-
NXDRIVE-1402 Clean up usage of lastSyncActiveRootDefinitions parameter deprecated in NuxeoDrive.GetChangeSummary
- Open
-
NXDRIVE-1372 Remove some usages of deprecated server-side code
- Resolved
- is related to
-
NXP-25844 Remove usage of deprecated code and code deprecated since 7.10 or less in nuxeo-drive-server
- Resolved