You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sentry.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/04/25 07:16:04 UTC

[jira] [Updated] (SENTRY-1493) Evaluate performance impact of using repeatable-read vs read-committed for Sentry

     [ https://issues.apache.org/jira/browse/SENTRY-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Kolbasov updated SENTRY-1493:
---------------------------------------
    Affects Version/s:     (was: sentry-ha-redesign)

> Evaluate performance impact of using repeatable-read vs read-committed for Sentry
> ---------------------------------------------------------------------------------
>
>                 Key: SENTRY-1493
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1493
>             Project: Sentry
>          Issue Type: Task
>          Components: Sentry
>    Affects Versions: 1.7.0
>            Reporter: Alexander Kolbasov
>            Priority: Minor
>
> SENTRY-1486 changes the isolation level from read-committed to repeatable read. This task is about evaluating perf impact for different databases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)