[
https://issues.apache.org/jira/browse/SENTRY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952735#comment-14952735
]
Hadoop QA commented on SENTRY-904:
----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12766070/SENTRY-904-1.patch
against master.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/884/console
This message is automatically generated.
> Set max message size for thrift messages
> ----------------------------------------
>
> Key: SENTRY-904
> URL: https://issues.apache.org/jira/browse/SENTRY-904
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.3.0
> Reporter: Sravya Tirukkovalur
> Assignee: Li Li
> Priority: Minor
> Attachments: SENTRY-904-0.patch, SENTRY-904-1.patch
>
>
> THRIFT-2572 can cause a service crash. Size of message can be out of range
> for two reasons: 1. Security scans 2. Malformatted message.
> We can fix this by using max message size configuration provided by
> TBinaryProtocol like how Hive handled it
> [here|https://issues.apache.org/jira/browse/HIVE-8680]
> And we should add a test to make sure scans are not bringing down the Sentry
> service.
> Example test:
> curl http://$(hostname -f):8038
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
