Bug #16155

materialized_permission_view has got to go

Added by Stanislaw Adaszewski almost 2 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Dear Team, On our Arvados instance with hundreds of users and projects and hundreds thousands of collections permission refreshes have become truly a burden. While I understand that this approach is easier and more robust than incremental permission updates, I assume that only rows corresponding to newly created/deleted objects could be added/removed from the permission view. Are there any plans to switch to a table rather than a view and perform incremental updates when necessary? Thank you in advance. Kind regards, -- Stanislaw


Related issues

Related to Arvados Epics - Story #16443: Redesign permission table updatesResolved04/01/202006/17/2020

History

#2 Updated by Peter Amstutz almost 2 years ago

Hi Stanislaw, thanks for the feedback, we've scheduled #16007 for the next sprint so we'll be taking a look into it.

#3 Updated by Stanislaw Adaszewski almost 2 years ago

Sounds great. Many thanks.

#4 Updated by Peter Amstutz over 1 year ago

  • Related to Story #16443: Redesign permission table updates added

Also available in: Atom PDF