[
https://issues.apache.org/jira/browse/SENTRY-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543971#comment-15543971
]
Hadoop QA commented on SENTRY-1486:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12831434/SENTRY-1486.001.patch
against master.
{color:red}Overall:{color} -1 due to 2 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.generic.tools.TestSentryShellKafka
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2038/console
This message is automatically generated.
> Sentry should use repeatable-read consistency level
> ---------------------------------------------------
>
> Key: SENTRY-1486
> URL: https://issues.apache.org/jira/browse/SENTRY-1486
> Project: Sentry
> Issue Type: Bug
> Components: Sentry
> Affects Versions: 1.7.0, sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Attachments: SENTRY-1486.001.patch
>
>
> Currently Sentry uses the "read-committed" consistency level which is the
> default for the Datanucleus JDO library. This causes potential problems since
> the state visible to each transaction can actually see updates from another
> transactions, so it is very difficult to reason about any code that reads
> multiple pieces of data.
> Instead it should use repeatable read" consistency which guarantees that any
> transaction only sees the state at the beginning of a transaction plus any
> updates done within a transaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
