[ 
https://issues.apache.org/jira/browse/IMPALA-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059126#comment-17059126
 ] 

Joe McDonnell commented on IMPALA-9191:
---------------------------------------

I think it makes sense to split this up into multiple parts. The first part is 
to make it possible to run tests without Sentry. Here is what I think would be 
needed for that:
 # Add an environment variable (something like DISABLE_SENTRY)
 # Only start up Sentry (in testdata/bin/run-all.sh) if DISABLE_SENTRY is false
 # Only run Sentry tests if DISABLE_SENTRY is false (through pytest skips and 
frontend test equivalents)
 # Set DISABLE_SENTRY to true for USE_CDP_HIVE=true.

This would still build against Sentry. A second part of this would be to be 
able to build without Sentry. That is harder, so it can be postponed.

> Provide a way to build Impala with only one of Sentry / Ranger
> --------------------------------------------------------------
>
>                 Key: IMPALA-9191
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9191
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 3.4.0
>            Reporter: Joe McDonnell
>            Assignee: Fang-Yu Rao
>            Priority: Critical
>
> Deployments of Impala will use either Ranger or Sentry, and deployments would 
> not switch back and forth between the two. It makes sense to provide a way to 
> pick at compile time which one to include. This allows packagers of Impala to 
> avoid a dependency for whichever authorization provider they don't need.
> In particular, compilation of the USE_CDP_HIVE=true side of Impala currently 
> needs only a few things from the CDH_BUILD_NUMBER and one them is Sentry. In 
> the other direction, the only thing a USE_CDP_HIVE=false configuration uses 
> from the CDP_BUILD_NUMBER is Ranger.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to