[jira] [Commented] (RANGER-1480) Implement plugin for Druid
[ https://issues.apache.org/jira/browse/RANGER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314807#comment-17314807 ] Bolke de Bruin commented on RANGER-1480: You are aware that Druid ships with a Ranger plugin for some time now right? > Implement plugin for Druid > -- > > Key: RANGER-1480 > URL: https://issues.apache.org/jira/browse/RANGER-1480 > Project: Ranger > Issue Type: New Feature > Components: admin, plugins >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Major > Attachments: > 0001-RANGER-1480-Second-version-of-the-druid-plugin.patch, Screen Shot > 2021-01-19 at 16.36.06.png > > > Druid is a high-performance, column-oriented, distributed data store, which > has an extension mechanism to incorporate various functionalities, for > example an external authorization system - just like ranger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-1480) Implement plugin for Druid
[ https://issues.apache.org/jira/browse/RANGER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17268142#comment-17268142 ] Bolke de Bruin commented on RANGER-1480: The official druid release has a ranger plugin nowadays > Implement plugin for Druid > -- > > Key: RANGER-1480 > URL: https://issues.apache.org/jira/browse/RANGER-1480 > Project: Ranger > Issue Type: New Feature > Components: admin, plugins >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Major > Attachments: 0001-RANGER-1480-Second-version-of-the-druid-plugin.patch > > > Druid is a high-performance, column-oriented, distributed data store, which > has an extension mechanism to incorporate various functionalities, for > example an external authorization system - just like ranger. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2850) Add javax.annotation to Presto plugin to ensure java 11 support
[ https://issues.apache.org/jira/browse/RANGER-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2850: --- External issue URL: https://reviews.apache.org/r/72572/ > Add javax.annotation to Presto plugin to ensure java 11 support > --- > > Key: RANGER-2850 > URL: https://issues.apache.org/jira/browse/RANGER-2850 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2850-Ensure-inclusion-of-javax.annotations-in.patch > > > Presto's assembly is missing the annotation jar which makes it not work with > Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127284#comment-17127284 ] Bolke de Bruin edited comment on RANGER-2754 at 6/6/20, 8:25 AM: - [~ppanda-beta] we run presto 332 with java 8. We havent tested java 11 yet and that might indeed require patches. Latest master was updated to support the additional controls that presto 332 required, which indeed checks for function and procedure execution rights. You will need to update your service definitions and policies to ensure it works. was (Author: bolke): [~ppanda-beta] we run presto 332 with java 8. We havent tested java 11 yet and that might indeed require patches. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127284#comment-17127284 ] Bolke de Bruin commented on RANGER-2754: [~ppanda-beta] we run presto 332 with java 8. We havent tested java 11 yet and that might indeed require patches. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2844) presto-server-333 can not show schemas/tables after integrated with Ranger master branch
[
https://issues.apache.org/jira/browse/RANGER-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127274#comment-17127274
]
Bolke de Bruin commented on RANGER-2844:
Please ensure you have applied the latest servicedefinition. ‘Show’ is in
master and if you do not have it in the UI you probably have an outdated
service definitiojn
> presto-server-333 can not show schemas/tables after integrated with Ranger
> master branch
>
>
> Key: RANGER-2844
> URL: https://issues.apache.org/jira/browse/RANGER-2844
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.1.0
> Environment: Amazon Linux
>Reporter: Jie Zhang
>Assignee: Pradeep Agrawal
>Priority: Major
> Fix For: 2.1.0
>
> Attachments: got access denied for show command.png, no show
> command.png
>
>
> Integrated presto-server-333 with Ranger master branch, able to run
> use/select queries, but got access denied when running *{color:#00875a}show
> schemas/tables{color}*.
> I saw there is no {color:#00875a}*show*{color} command on ranger-ui
> (screenshot attached), is that why presto can not show schemas/tables? Any
> workaround? Thanks a lot.
>
> Error:
> {code:java}
> presto:default> use default;
> USE
> presto:default> show schemas;
> Query 20200604_192311_00023_sa7kt failed: Access Denied: Cannot show schemas:
> hivepresto:default> show tables;
> Query 20200604_192319_00024_sa7kt failed: Access Denied: Cannot show tables
> of schema hive.default
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (RANGER-1784) Feature Request: Presto Ranger integration
[ https://issues.apache.org/jira/browse/RANGER-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-1784: --- Fix Version/s: 2.1 > Feature Request: Presto Ranger integration > -- > > Key: RANGER-1784 > URL: https://issues.apache.org/jira/browse/RANGER-1784 > Project: Ranger > Issue Type: New Feature > Components: admin, audit, plugins, Ranger >Affects Versions: 0.7.1 > Environment: HDP 2.6 + Kerberos + Presto >Reporter: Hari Sekhon >Priority: Critical > Fix For: 2.1 > > > Feature Request to add Presto authorization support to Ranger. > This could perhaps piggy back to use Hive policies in Ranger or else copy > what Hive has to a separately managed policy for Presto. There are trade-offs > to both styles, so perhaps make this a configurable user choice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2192) Implement Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-2192. Fix Version/s: 2.1.0 Resolution: Fixed > Implement Presto plugin > --- > > Key: RANGER-2192 > URL: https://issues.apache.org/jira/browse/RANGER-2192 > Project: Ranger > Issue Type: New Feature > Components: plugins, Ranger >Reporter: t oo >Priority: Major > Fix For: 2.1.0 > > > Implement Presto plugin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2816) Presto-ranger plugin has jersey error on presto server startup
[
https://issues.apache.org/jira/browse/RANGER-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bolke de Bruin resolved RANGER-2816.
Resolution: Won't Fix
Support for Presto was added in Ranger 2.
> Presto-ranger plugin has jersey error on presto server startup
> --
>
> Key: RANGER-2816
> URL: https://issues.apache.org/jira/browse/RANGER-2816
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 1.0.0
> Environment: amazonlinux1, java8 (OpenJDK Runtime Environment (build
> 1.8.0_242-b08)). Looking at what has changed in the environment:
> yum packages -->
> from
> file.x86_64 5.37-8.48.amzn1 installed
>
> file-libs.x86_64 5.37-8.48.amzn1 installed
> kernel.x86_64 4.14.165-102.185.amzn1 installed
>
> kernel.x86_64 4.14.171-105.231.amzn1
> @amzn-updates
> kernel-headers.x86_64 4.14.171-105.231.amzn1
> @amzn-updates
> libicu.x86_64 50.1.2-11.12.amzn1 installed
>
> libtirpc.x86_64 0.2.4-0.8.14.amzn1 installed
>
>
> to
> file.x86_64 5.37-8.49.amzn1 installed
> file-libs.x86_64 5.37-8.49.amzn1 installed
> kernel.x86_64 4.14.171-105.231.amzn1 installed
> kernel.x86_64 4.14.173-106.229.amzn1
> @amzn-updates
> kernel-headers.x86_64 4.14.173-106.229.amzn1
> @amzn-updates
> libicu.x86_64 50.2-4.0.amzn1
> @amzn-updates
> libtirpc.x86_64 0.2.4-0.16.15.amzn1
> @amzn-updates
> jersey jars:
> /home/ec2-user/presto-server-0.220/lib/jersey-media-jaxb-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-container-servlet-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-hk2-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-server-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-client-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-container-servlet-core-2.26.jar
> /home/ec2-user/presto-server-0.220/lib/jersey-common-2.26.jar
> /home/ec2-user/presto-server-0.220/plugin/ranger/ranger-presto-plugin-impl/jersey-server-1.9.jar
> /home/ec2-user/presto-server-0.220/plugin/ranger/ranger-presto-plugin-impl/jersey-bundle-1.19.3.jar
> /home/ec2-user/presto-server-0.220/plugin/ranger/ranger-presto-plugin-impl/jersey-json-1.9.jar
> /home/ec2-user/presto-server-0.220/plugin/ranger/ranger-presto-plugin-impl/jersey-core-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-usersync/lib/jersey-bundle-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-presto-plugin/lib/ranger-presto-plugin-impl/jersey-server-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-presto-plugin/lib/ranger-presto-plugin-impl/jersey-bundle-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-presto-plugin/lib/ranger-presto-plugin-impl/jersey-json-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-presto-plugin/lib/ranger-presto-plugin-impl/jersey-core-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-server-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-bundle-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-core-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-client-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-multipart-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-spring-1.19.3.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-json-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-guice-1.9.jar
> /usr/lib/apache-ranger-1.0.0/target/ranger-1.0.0-admin/ews/webapp/WEB-INF/lib/jersey-servlet-1.19.3.jar
>Reporter: t oo
>Priority: Major
> Attachments: patch2.diff
>
>
> I am using ranger 1.0.0 and prestodb 220, everything has been working for >
> 10 mths until today presto startup consistently gets this error:
> {code:java}
> 2020-05-04T18:50:26.036ZINFOmain
> org.apache.ranger.audit.queue.AuditFileSpoolStarting writerThread,
> queueName=presto.async.batch, consumer=presto.async.batch.solr
> 2020-05-04T18:50:26.038ZINFORanger async Audit cleanup
> org.apache.ranger.audit.provider.AuditProviderFactory
> RangerAsyncAuditCleanup: Waiting to audit cleanup
[jira] [Resolved] (RANGER-1784) Feature Request: Presto Ranger integration
[ https://issues.apache.org/jira/browse/RANGER-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-1784. Resolution: Fixed Ranger has support for PrestoSQL > Feature Request: Presto Ranger integration > -- > > Key: RANGER-1784 > URL: https://issues.apache.org/jira/browse/RANGER-1784 > Project: Ranger > Issue Type: New Feature > Components: admin, audit, plugins, Ranger >Affects Versions: 0.7.1 > Environment: HDP 2.6 + Kerberos + Presto >Reporter: Hari Sekhon >Priority: Critical > > Feature Request to add Presto authorization support to Ranger. > This could perhaps piggy back to use Hive policies in Ranger or else copy > what Hive has to a separately managed policy for Presto. There are trade-offs > to both styles, so perhaps make this a configurable user choice. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2850) Add javax.annotation to Presto plugin to ensure java 11 support
Bolke de Bruin created RANGER-2850: -- Summary: Add javax.annotation to Presto plugin to ensure java 11 support Key: RANGER-2850 URL: https://issues.apache.org/jira/browse/RANGER-2850 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Bolke de Bruin Assignee: Bolke de Bruin Presto's assembly is missing the annotation jar which makes it not work with Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2835) Presto plugin DROP TABLE or DELETE is always denied
[ https://issues.apache.org/jira/browse/RANGER-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17127350#comment-17127350 ] Bolke de Bruin commented on RANGER-2835: [~toopt4] I'm not seeing an issue here? You are getting an access denied on "drop table" which could be in your policy? Remember the default is to deny. Did you upgrade your service definition which is required when going to > 332. > Presto plugin DROP TABLE or DELETE is always denied > --- > > Key: RANGER-2835 > URL: https://issues.apache.org/jira/browse/RANGER-2835 > Project: Ranger > Issue Type: Bug > Components: plugins, Ranger >Reporter: t oo >Priority: Major > > DROP VIEW works, INSERT works but DROP TABLE does not work, DELETE does not > work > > > "com.facebook.presto.spi.security.AccessDeniedException.denyDropTable(AccessDeniedException.java:111)", > > "com.facebook.presto.spi.security.AccessDeniedException.denyDropTable(AccessDeniedException.java:106)", > > "com.facebook.presto.hive.security.LegacyAccessControl.checkCanDropTable(LegacyAccessControl.java:99)", > > "com.facebook.presto.hive.security.PartitionsAwareAccessControl.checkCanDropTable(PartitionsAwareAccessControl.java:88)", > > "com.facebook.presto.security.AccessControlManager.lambda$checkCanDropTable$19(AccessControlManager.java:283)", > > "com.facebook.presto.security.AccessControlManager.authorizationCheck(AccessControlManager.java:717)", > > "com.facebook.presto.security.AccessControlManager.checkCanDropTable(AccessControlManager.java:283)", > > "com.facebook.presto.execution.DropTableTask.execute(DropTableTask.java:57)", > "com.facebook.presto.execution.DropTableTask.execute(DropTableTask.java:34)", > "com.facebook.presto.execution.DataDefinitionExecution.start(DataDefinitionExecution.java:169)", > > "java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)", > > "java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)", > "java.lang.Thread.run(Thread.java:748)" > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2850) Add javax.annotation to Presto plugin to ensure java 11 support
[ https://issues.apache.org/jira/browse/RANGER-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2850: --- Attachment: 0001-RANGER-2850-Ensure-inclusion-of-javax.annotations-in.patch > Add javax.annotation to Presto plugin to ensure java 11 support > --- > > Key: RANGER-2850 > URL: https://issues.apache.org/jira/browse/RANGER-2850 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2850-Ensure-inclusion-of-javax.annotations-in.patch > > > Presto's assembly is missing the annotation jar which makes it not work with > Java 11. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2747) Ranger integration with presto works on "Release 317" but fails on versions later
[ https://issues.apache.org/jira/browse/RANGER-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-2747. Resolution: Fixed fixed in master > Ranger integration with presto works on "Release 317" but fails on versions > later > - > > Key: RANGER-2747 > URL: https://issues.apache.org/jira/browse/RANGER-2747 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: harsha >Priority: Blocker > Time Spent: 20m > Remaining Estimate: 0h > > Hi, > I am trying to integrate ranger with presto and its working on "Release 317" > I followed the following documentation : > [https://cwiki.apache.org/confluence/display/RANGER/Presto+Plugin] > But, when when I go with versions after that, It throws the following errors. > *query*: _SHOW CATALOGS_ > *error* : _[65536] Query failed (#20200303_063413_2_h5s89): Internal > error java.lang.RuntimeException: java.lang.IllegalStateException_ > *query*:_select * from hive.db_name.table_name limit 10_ > *error*:_[4] Query failed (#20200303_063836_0_x47vg): Access Denied: > Cannot access catalog hive java.lang.RuntimeException: > io.prestosql.spi.security.AccessDeniedException: Access Denied: Cannot access > catalog hive_ > I've tried versions 318,319,323,329 and i am facing similar errors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2472) Presto-plugin error upon setup
[
https://issues.apache.org/jira/browse/RANGER-2472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bolke de Bruin resolved RANGER-2472.
Resolution: Duplicate
> Presto-plugin error upon setup
> --
>
> Key: RANGER-2472
> URL: https://issues.apache.org/jira/browse/RANGER-2472
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.0.0
>Reporter: Pedro Rossi
>Priority: Major
>
> * The {{ranger-presto-*.xml}} files must be packed into a jar and added to
> {{/plugins/ranger/ranger-presto-impl}} in order to be recognized by the
> {{...getClassLoader().getResource("...")}} line, is there any other way to
> add these files without having to pack a jar?
> * After the {{*.xml}} files are added it gives an error about missing this
> lib ([https://github.com/mattsheppard/gethostname4j]) upon using reflection
> but after adding it to the same folder above it worked fine, shouldn't this
> lib be on added automatically upon building the project?
> Notes: I used the docker script to build the project and later moved the jars
> to my presto build docker container
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (RANGER-2716) Add catalogs/schemas/tables filter in presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-2716. Resolution: Duplicate > Add catalogs/schemas/tables filter in presto plugin > --- > > Key: RANGER-2716 > URL: https://issues.apache.org/jira/browse/RANGER-2716 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Attachments: 0001-RANGER-2716.patch, 0002-RANGER-2716.patch > > > Presto plugin returns the input set of catalogs/schemas/tables directly at > present. However, this causes a problem, that is, when the user uses show > catalogs/schemas/tables, all catalogs/schemas/tables are displayed, even > though the user does not have the permissions to display all > catalogs/schemas/tables. > We need to fix the filterCatalogs/Schemas/Tables functions to filter > catalogs/schemas/tables, so that the user can only see the > catalogs/schemas/tables in which the user has SELECT permission. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110094#comment-17110094 ] Bolke de Bruin commented on RANGER-2754: It's already fixed in master > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2826) Update Presto Plugin to support PrestoSql 333
[ https://issues.apache.org/jira/browse/RANGER-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2826: --- External issue URL: https://reviews.apache.org/r/72513/ > Update Presto Plugin to support PrestoSql 333 > - > > Key: RANGER-2826 > URL: https://issues.apache.org/jira/browse/RANGER-2826 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2826-Add-support-for-PrestoSQL-333.patch > > > PrestoSql has updated its security API again and made it backwards > incompatible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2826) Update Presto Plugin to support PrestoSql 333
[ https://issues.apache.org/jira/browse/RANGER-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107649#comment-17107649 ] Bolke de Bruin commented on RANGER-2826: cc [~mad...@apache.org] > Update Presto Plugin to support PrestoSql 333 > - > > Key: RANGER-2826 > URL: https://issues.apache.org/jira/browse/RANGER-2826 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2826-Add-support-for-PrestoSQL-333.patch > > > PrestoSql has updated its security API again and made it backwards > incompatible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2826) Update Presto Plugin to support PrestoSql 333
[ https://issues.apache.org/jira/browse/RANGER-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2826: --- Attachment: 0001-RANGER-2826-Add-support-for-PrestoSQL-333.patch > Update Presto Plugin to support PrestoSql 333 > - > > Key: RANGER-2826 > URL: https://issues.apache.org/jira/browse/RANGER-2826 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2826-Add-support-for-PrestoSQL-333.patch > > > PrestoSql has updated its security API again and made it backwards > incompatible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2826) Update Presto Plugin to support PrestoSql 333
[ https://issues.apache.org/jira/browse/RANGER-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2826: --- Summary: Update Presto Plugin to support PrestoSql 333 (was: Update Presto Plugin to support PresoSql 333) > Update Presto Plugin to support PrestoSql 333 > - > > Key: RANGER-2826 > URL: https://issues.apache.org/jira/browse/RANGER-2826 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Priority: Major > > PrestoSql has updated its security API again and made it backwards > incompatible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2826) Update Presto Plugin to support PresoSql 333
Bolke de Bruin created RANGER-2826: -- Summary: Update Presto Plugin to support PresoSql 333 Key: RANGER-2826 URL: https://issues.apache.org/jira/browse/RANGER-2826 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Bolke de Bruin PrestoSql has updated its security API again and made it backwards incompatible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2716) Add catalogs/schemas/tables filter in presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090539#comment-17090539 ] Bolke de Bruin commented on RANGER-2716: Awesome. I do wonder what those missing features are as I tried to be pretty comprehensive > Add catalogs/schemas/tables filter in presto plugin > --- > > Key: RANGER-2716 > URL: https://issues.apache.org/jira/browse/RANGER-2716 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Attachments: 0001-RANGER-2716.patch, 0002-RANGER-2716.patch > > > Presto plugin returns the input set of catalogs/schemas/tables directly at > present. However, this causes a problem, that is, when the user uses show > catalogs/schemas/tables, all catalogs/schemas/tables are displayed, even > though the user does not have the permissions to display all > catalogs/schemas/tables. > We need to fix the filterCatalogs/Schemas/Tables functions to filter > catalogs/schemas/tables, so that the user can only see the > catalogs/schemas/tables in which the user has SELECT permission. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2716) Add catalogs/schemas/tables filter in presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090473#comment-17090473 ] Bolke de Bruin commented on RANGER-2716: I suggest closing this as RANGER-2754 is now merged and addresses this. > Add catalogs/schemas/tables filter in presto plugin > --- > > Key: RANGER-2716 > URL: https://issues.apache.org/jira/browse/RANGER-2716 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Attachments: 0001-RANGER-2716.patch, 0002-RANGER-2716.patch > > > Presto plugin returns the input set of catalogs/schemas/tables directly at > present. However, this causes a problem, that is, when the user uses show > catalogs/schemas/tables, all catalogs/schemas/tables are displayed, even > though the user does not have the permissions to display all > catalogs/schemas/tables. > We need to fix the filterCatalogs/Schemas/Tables functions to filter > catalogs/schemas/tables, so that the user can only see the > catalogs/schemas/tables in which the user has SELECT permission. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088615#comment-17088615 ] Bolke de Bruin commented on RANGER-2754: Wildcard is set to true now for all items in the row/column policies. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088597#comment-17088597 ] Bolke de Bruin commented on RANGER-2754: [~ppanda-beta] updated the service definition for RowFiltering and Column Masking > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[
https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088528#comment-17088528
]
Bolke de Bruin commented on RANGER-2754:
[~ppanda-beta] I think the configuration is correct. wildcard=true and
ignorecase=true in the service definition. This results in
{code}
// If optWildcard is true
// If ('?' found or non-contiguous '*'s found in policyValue)
// needWildcardMatch = true
// End
//
// wildcardStartIdx is set to index of first '*' in
policyValue or -1 if '*' is not found in policyValue, and
// wildcardEndIdx is set to index of last '*' in
policyValue or -1 if '*' is not found in policyValue
// Else
// needWildcardMatch is set to false
// End
if (needWildcardMatch) { // test?, test*a*, test*a*b, *test*a
ret = optIgnoreCase ? new
CaseInsensitiveWildcardMatcher(policyValue) : new
CaseSensitiveWildcardMatcher(policyValue);
} else if (wildcardStartIdx == -1) { // test, testa, testab
ret = optIgnoreCase ? new
CaseInsensitiveStringMatcher(policyValue) : new
CaseSensitiveStringMatcher(policyValue);
{code}
So I think your value is probably incorrect.
> Update presto dependency and implement row/column level security
>
>
> Key: RANGER-2754
> URL: https://issues.apache.org/jira/browse/RANGER-2754
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: master
>Reporter: Bolke de Bruin
>Assignee: Bolke de Bruin
>Priority: Major
> Attachments:
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> RANGER-2754-v2.patch, RANGER-2754.patch
>
>
> 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped
> working for versions > ~321.
> 2. Presto master now has row/column level security support
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088384#comment-17088384 ] Bolke de Bruin commented on RANGER-2754: Ah shoot, I forgot about that one. Will have a look. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088326#comment-17088326 ] Bolke de Bruin commented on RANGER-2754: If java maintains binary compatibility then it should not be an issue. But why don't you try it? > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087865#comment-17087865 ] Bolke de Bruin commented on RANGER-2754: [~ppand-beta] updated. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[
https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087797#comment-17087797
]
Bolke de Bruin commented on RANGER-2754:
Thanks for reporting. I'll fix that tonight. Type is known to ranger by using
{type} which is Presto specific
> Update presto dependency and implement row/column level security
>
>
> Key: RANGER-2754
> URL: https://issues.apache.org/jira/browse/RANGER-2754
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: master
>Reporter: Bolke de Bruin
>Assignee: Bolke de Bruin
>Priority: Major
> Attachments:
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch,
> RANGER-2754-v2.patch, RANGER-2754.patch
>
>
> 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped
> working for versions > ~321.
> 2. Presto master now has row/column level security support
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087465#comment-17087465 ] Bolke de Bruin commented on RANGER-2754: Latest patch works. Your steps should work, ensure you have the latest service definition applied. That only works on a clean setup (e.g. no previous enabled presto service in ranger). The upgrade script i will create after this patch is accepted. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084087#comment-17084087 ] Bolke de Bruin commented on RANGER-2395: That will not work. The current plugin does not support presto >317 due to an api change on The side of presto > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 7.5h > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084085#comment-17084085 ] Bolke de Bruin commented on RANGER-2754: I suggest building master with this patch and push the service definition into Ranger 1.2 and start presto with the plugin you built. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082334#comment-17082334 ] Bolke de Bruin commented on RANGER-2395: This plugin is for PrestoSql. I haven't checked PrestoDB. If it exposes the same api it could be just a matter of implementing the interface. > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 7.5h > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080363#comment-17080363 ] Bolke de Bruin commented on RANGER-2754: [~liujiayi771] I have included your changes in the latest update to this patch. I hope you don't mind. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2782) Upgrade log4j dependency
[ https://issues.apache.org/jira/browse/RANGER-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080307#comment-17080307 ] Bolke de Bruin commented on RANGER-2782: Yes working on that. It will be much larger though. > Upgrade log4j dependency > > > Key: RANGER-2782 > URL: https://issues.apache.org/jira/browse/RANGER-2782 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Blocker > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2782-Upgrade-log4j-to-a-supported-version.patch > > > The current log4j version in ranger is end of life and contains critical > security Vulnerabilities > CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (RANGER-2787) Upgrade presto version to 331
[ https://issues.apache.org/jira/browse/RANGER-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin reopened RANGER-2787: > Upgrade presto version to 331 > - > > Key: RANGER-2787 > URL: https://issues.apache.org/jira/browse/RANGER-2787 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Fix For: 2.1 > > Attachments: 0001-RANGER-2787.patch > > > Upgrade presto dependency to version 331 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2787) Upgrade presto version to 331
[ https://issues.apache.org/jira/browse/RANGER-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-2787. Resolution: Duplicate > Upgrade presto version to 331 > - > > Key: RANGER-2787 > URL: https://issues.apache.org/jira/browse/RANGER-2787 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Fix For: 2.1 > > Attachments: 0001-RANGER-2787.patch > > > Upgrade presto dependency to version 331 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RANGER-2787) Upgrade presto version to 331
[ https://issues.apache.org/jira/browse/RANGER-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin resolved RANGER-2787. Resolution: Fixed > Upgrade presto version to 331 > - > > Key: RANGER-2787 > URL: https://issues.apache.org/jira/browse/RANGER-2787 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Jiayi Liu >Priority: Major > Fix For: 2.1 > > Attachments: 0001-RANGER-2787.patch > > > Upgrade presto dependency to version 331 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2782) Upgrade log4j dependency
[ https://issues.apache.org/jira/browse/RANGER-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2782: --- External issue URL: https://reviews.apache.org/r/72331/ > Upgrade log4j dependency > > > Key: RANGER-2782 > URL: https://issues.apache.org/jira/browse/RANGER-2782 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Blocker > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2782-Upgrade-log4j-to-a-supported-version.patch > > > The current log4j version in ranger is end of life and contains critical > security Vulnerabilities > CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2702) Upgrade Kafka Version in Ranger to 2.4
[ https://issues.apache.org/jira/browse/RANGER-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077167#comment-17077167 ] Bolke de Bruin commented on RANGER-2702: I know, this leaves the current release (2.0.0) vulnerable as this is only in master at the moment. Ie. I'm suggesting a back port to 2.0 or to release 2.1 > Upgrade Kafka Version in Ranger to 2.4 > -- > > Key: RANGER-2702 > URL: https://issues.apache.org/jira/browse/RANGER-2702 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Labels: security > Fix For: 2.1.0 > > > Upgrade Kafka Version in Ranger to 2.4. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (RANGER-2702) Upgrade Kafka Version in Ranger to 2.4
[ https://issues.apache.org/jira/browse/RANGER-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077167#comment-17077167 ] Bolke de Bruin edited comment on RANGER-2702 at 4/7/20, 12:15 PM: -- I know, this leaves the current release (Ranger 2.0.0) vulnerable as this is only in master at the moment. Ie. I'm suggesting a back port to 2.0 or to release 2.1 was (Author: bolke): I know, this leaves the current release (2.0.0) vulnerable as this is only in master at the moment. Ie. I'm suggesting a back port to 2.0 or to release 2.1 > Upgrade Kafka Version in Ranger to 2.4 > -- > > Key: RANGER-2702 > URL: https://issues.apache.org/jira/browse/RANGER-2702 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Labels: security > Fix For: 2.1.0 > > > Upgrade Kafka Version in Ranger to 2.4. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2782) Upgrade log4j dependency
[ https://issues.apache.org/jira/browse/RANGER-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2782: --- Attachment: 0001-RANGER-2782-Upgrade-log4j-to-a-supported-version.patch > Upgrade log4j dependency > > > Key: RANGER-2782 > URL: https://issues.apache.org/jira/browse/RANGER-2782 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Blocker > Fix For: 2.1.0 > > Attachments: > 0001-RANGER-2782-Upgrade-log4j-to-a-supported-version.patch > > > The current log4j version in ranger is end of life and contains critical > security Vulnerabilities > CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2782) Upgrade log4j dependency
[ https://issues.apache.org/jira/browse/RANGER-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin reassigned RANGER-2782: -- Assignee: Bolke de Bruin > Upgrade log4j dependency > > > Key: RANGER-2782 > URL: https://issues.apache.org/jira/browse/RANGER-2782 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Blocker > Fix For: 2.1.0 > > > The current log4j version in ranger is end of life and contains critical > security Vulnerabilities > CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2702) Upgrade Kafka Version in Ranger to 2.4
[ https://issues.apache.org/jira/browse/RANGER-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2702: --- Labels: security (was: ) > Upgrade Kafka Version in Ranger to 2.4 > -- > > Key: RANGER-2702 > URL: https://issues.apache.org/jira/browse/RANGER-2702 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Labels: security > Fix For: 2.1.0 > > > Upgrade Kafka Version in Ranger to 2.4. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2702) Upgrade Kafka Version in Ranger to 2.4
[ https://issues.apache.org/jira/browse/RANGER-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17077161#comment-17077161 ] Bolke de Bruin commented on RANGER-2702: Kafka 2.0.0 contains critical CVEs: CVE-2019-12399, CVE-2018-17196 is it possible to have a back port to 2.0 and have a minor release (2.0.1)? > Upgrade Kafka Version in Ranger to 2.4 > -- > > Key: RANGER-2702 > URL: https://issues.apache.org/jira/browse/RANGER-2702 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.1.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 2.1.0 > > > Upgrade Kafka Version in Ranger to 2.4. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RANGER-2782) Upgrade log4j dependency
Bolke de Bruin created RANGER-2782: -- Summary: Upgrade log4j dependency Key: RANGER-2782 URL: https://issues.apache.org/jira/browse/RANGER-2782 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.0.0 Reporter: Bolke de Bruin The current log4j version in ranger is end of life and contains critical security Vulnerabilities CVE-2019-17571 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17067700#comment-17067700 ] Bolke de Bruin commented on RANGER-2754: Patch ready for review > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: RANGER-2754-v2.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754-v2.patch, RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: RANGER-2754.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch, > RANGER-2754.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin reassigned RANGER-2754: -- Assignee: Bolke de Bruin > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061945#comment-17061945 ] Bolke de Bruin commented on RANGER-2754: The attached patch is for testing. It might still need some adjustments. This supports Presto 331 and above and includes row level filtering and column masking support. It requires updating the service definition. > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RANGER-2754) Update presto dependency and implement row/column level security
[ https://issues.apache.org/jira/browse/RANGER-2754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2754: --- Attachment: 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > Update presto dependency and implement row/column level security > > > Key: RANGER-2754 > URL: https://issues.apache.org/jira/browse/RANGER-2754 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: master >Reporter: Bolke de Bruin >Priority: Major > Attachments: > 0001-RANGER-2754-Upgrade-presto-dependency-and-improve-lo.patch > > > 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped > working for versions > ~321. > 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2751) SSL enabled Apache Ranger (2.1.0) not working with SSL enabled Presto (Prestosql 310) - Policy synch up not happening
[
https://issues.apache.org/jira/browse/RANGER-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053348#comment-17053348
]
Bolke de Bruin commented on RANGER-2751:
https://issues.apache.org/jira/browse/RANGER-2611
Check what the config file of the plugin actually says (your ranger-XXX.xml)
> SSL enabled Apache Ranger (2.1.0) not working with SSL enabled Presto
> (Prestosql 310) - Policy synch up not happening
> --
>
> Key: RANGER-2751
> URL: https://issues.apache.org/jira/browse/RANGER-2751
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 2.1.0
>Reporter: sajai
>Priority: Major
> Fix For: 2.1.0
>
>
> *Facing the below error when trying to integrate Apache Ranger with Prestosql
> (310 version).*
> *Both Ranger and Presto is working independently, but the Presto policies
> from Ranger are not downloading/refreshing. Couldn't find the policies
> downloaded in Ranger web ui in Audits/Plugin tab. Also if we remove SSL from
> Ranger side it starts working fine. Issue is only when SSL is enabled in
> Ranger, then Presto inot working with Ranger,*
> 2020-03-04T07:50:59.600-0600 ERROR Thread-91
> org.apache.ranger.plugin.util.PolicyRefresher
> PolicyRefresher(serviceName=presto-catalogs-dev): failed to refresh policies.
> Will continue to use last known version of policies (-1)
> java.lang.IllegalArgumentException: TrustManager is not specified
> *ranger-2.1.0-SNAPSHOT-admin/install.properties:-*
> db_root_user=root
> db_root_password=Sqlpwd@123
> db_host=localhost
> db_name=ranger
> db_user=rangeradmin
> db_password=Rangerpwd@123
> rangerAdmin_password=Rangerpwd@123
> rangerTagsync_password=Rangerpwd@123
> rangerUsersync_password=Rangerpwd@123
> keyadmin_password=Rangerpwd@123
> policymgr_external_url=https://hostname_ranger:6182
> policymgr_http_enabled=false
> policymgr_https_keystore_file=/opt/iss_cert/clientcert.jks
> policymgr_https_keystore_keyalias=
> policymgr_https_keystore_password=31b17532aeb4fb5ba3af2bae850567
> unix_user=ranger
> unix_user_pwd=Rangerpwd@123
> unix_group=ranger
> #LDAP|ACTIVE_DIRECTORY|UNIX|NONE
> authentication_method=LDAP
> xa_ldap_url=ldaps://hostname_ldapserver:636
> xa_ldap_userDNpattern=uid=\{0},OU=xxx,DC=xx,DC=,DC=COM
> xa_ldap_groupSearchBase=DC=xxx,DC=ccc,DC=COM
> xa_ldap_groupSearchFilter=(member=cn=\{0},OU=xxx,DC=xx,DC=,DC=COM)
> xa_ldap_groupRoleAttribute=cn
> xa_ldap_base_dn=DC=xx,DC=,DC=COM
> xa_ldap_bind_dn=CN=XXX,OU=XX,DC=xx,DC=,DC=COM
> xa_ldap_bind_password=uBLRzVJK
> xa_ldap_referral=follow
> xa_ldap_userSearchFilter=(uid=\{0})
> *With the above values,able to start ranger with SSL and LDAP enabled and
> also able to login succesfully with both unix admin credentials and also with
> ldap credentials.*
>
> *ranger-2.1.0-SNAPSHOT-presto-plugin/install.properties:-*
> POLICY_MGR_URL=https:/hostname_ranger:6182
> REPOSITORY_NAME=presto-catalogs-dev
> *# You do not need use SSL between agent and security admin tool, please
> leave these sample value as it is.*
> SSL_KEYSTORE_FILE_PATH=/etc/hadoop/conf/ranger-plugin-keystore.jks
> SSL_KEYSTORE_PASSWORD=none
> SSL_TRUSTSTORE_FILE_PATH=/etc/hadoop/conf/ranger-plugin-truststore.jks
> SSL_TRUSTSTORE_PASSWORD=none
> *keep blank if component user is default*
> CUSTOM_USER=
> *keep blank if component group is default*
> CUSTOM_GROUP=
>
> *presto-server-310/etc/config.properties:-*
> coordinator=true
> node-scheduler.include-coordinator=true
> http-server.http.enabled=false
> node.internal-address-source=FQDN
> node.internal-address=hostname_presto
> internal-communication.https.required=true
> internal-communication.https.keystore.path=/opt/iss_cert/clientcert.jks
> internal-communication.https.keystore.key=31b17532aeb4fb5ba3af2bae850567
> discovery-server.enabled=true
> discovery.uri=https://hostname_presto:8443
> http-server.authentication.type=PASSWORD,CERTIFICATE
> http-server.https.enabled=true
> http-server.https.port=8443
> http-server.https.keystore.path=/opt/iss_cert/clientcert.jks
> http-server.https.keystore.key=31b17532aeb4fb5ba3af2bae850567
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (RANGER-2754) Update presto dependency and implement row/column level security
Bolke de Bruin created RANGER-2754: -- Summary: Update presto dependency and implement row/column level security Key: RANGER-2754 URL: https://issues.apache.org/jira/browse/RANGER-2754 Project: Ranger Issue Type: Improvement Components: plugins Affects Versions: master Reporter: Bolke de Bruin 1. PrestoSql has changed its Security API hence the Ranger plugin has stopped working for versions > ~321. 2. Presto master now has row/column level security support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RANGER-2502) Presto plugin insert bug
[ https://issues.apache.org/jira/browse/RANGER-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883248#comment-16883248 ] Bolke de Bruin commented on RANGER-2502: [~abhayk] can you please merge the patch? > Presto plugin insert bug > > > Key: RANGER-2502 > URL: https://issues.apache.org/jira/browse/RANGER-2502 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Major > Attachments: > 0001-RANGER-2502-Correct-service-definition-for-presto.patch > > > I wasn't able to insert anything even with the admin user until I changed > from INSERT to UPDATE on the following line > [https://github.com/apache/ranger/blob/master/plugin-presto/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java#L458] > , I don't know if this is the admin fault because it is not showing the > INSERT permission or it really should use UPDATE instead of INSERT, but I > think it makes more sense to show INSERT instead of UPDATE since presto sql > syntax doesn't have an UPDATE statement > (https://prestosql.io/docs/current/sql.html) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880691#comment-16880691 ] Bolke de Bruin commented on RANGER-2489: Awesome! > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2502) Presto plugin insert bug
[ https://issues.apache.org/jira/browse/RANGER-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880682#comment-16880682 ] Bolke de Bruin commented on RANGER-2502: https://reviews.apache.org/r/71037/ > Presto plugin insert bug > > > Key: RANGER-2502 > URL: https://issues.apache.org/jira/browse/RANGER-2502 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Major > Attachments: > 0001-RANGER-2502-Correct-service-definition-for-presto.patch > > > I wasn't able to insert anything even with the admin user until I changed > from INSERT to UPDATE on the following line > [https://github.com/apache/ranger/blob/master/plugin-presto/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java#L458] > , I don't know if this is the admin fault because it is not showing the > INSERT permission or it really should use UPDATE instead of INSERT, but I > think it makes more sense to show INSERT instead of UPDATE since presto sql > syntax doesn't have an UPDATE statement > (https://prestosql.io/docs/current/sql.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2502) Presto plugin insert bug
[ https://issues.apache.org/jira/browse/RANGER-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880678#comment-16880678 ] Bolke de Bruin commented on RANGER-2502: cc [~abhayk] while you are at it ;) > Presto plugin insert bug > > > Key: RANGER-2502 > URL: https://issues.apache.org/jira/browse/RANGER-2502 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Major > Attachments: > 0001-RANGER-2502-Correct-service-definition-for-presto.patch > > > I wasn't able to insert anything even with the admin user until I changed > from INSERT to UPDATE on the following line > [https://github.com/apache/ranger/blob/master/plugin-presto/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java#L458] > , I don't know if this is the admin fault because it is not showing the > INSERT permission or it really should use UPDATE instead of INSERT, but I > think it makes more sense to show INSERT instead of UPDATE since presto sql > syntax doesn't have an UPDATE statement > (https://prestosql.io/docs/current/sql.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2502) Presto plugin insert bug
[ https://issues.apache.org/jira/browse/RANGER-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2502: --- Attachment: 0001-RANGER-2502-Correct-service-definition-for-presto.patch > Presto plugin insert bug > > > Key: RANGER-2502 > URL: https://issues.apache.org/jira/browse/RANGER-2502 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Major > Attachments: > 0001-RANGER-2502-Correct-service-definition-for-presto.patch > > > I wasn't able to insert anything even with the admin user until I changed > from INSERT to UPDATE on the following line > [https://github.com/apache/ranger/blob/master/plugin-presto/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java#L458] > , I don't know if this is the admin fault because it is not showing the > INSERT permission or it really should use UPDATE instead of INSERT, but I > think it makes more sense to show INSERT instead of UPDATE since presto sql > syntax doesn't have an UPDATE statement > (https://prestosql.io/docs/current/sql.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2502) Presto plugin insert bug
[ https://issues.apache.org/jira/browse/RANGER-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880675#comment-16880675 ] Bolke de Bruin commented on RANGER-2502: Good ctach. The service definition is incorrect. Will provide a fix. > Presto plugin insert bug > > > Key: RANGER-2502 > URL: https://issues.apache.org/jira/browse/RANGER-2502 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Major > > I wasn't able to insert anything even with the admin user until I changed > from INSERT to UPDATE on the following line > [https://github.com/apache/ranger/blob/master/plugin-presto/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java#L458] > , I don't know if this is the admin fault because it is not showing the > INSERT permission or it really should use UPDATE instead of INSERT, but I > think it makes more sense to show INSERT instead of UPDATE since presto sql > syntax doesn't have an UPDATE statement > (https://prestosql.io/docs/current/sql.html) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2501) Ranger-admin not showing presto columns
[ https://issues.apache.org/jira/browse/RANGER-2501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880671#comment-16880671 ] Bolke de Bruin commented on RANGER-2501: I'll check this, but I am pretty sure that we see columns in our setup. > Ranger-admin not showing presto columns > --- > > Key: RANGER-2501 > URL: https://issues.apache.org/jira/browse/RANGER-2501 > Project: Ranger > Issue Type: Bug > Components: admin, plugins >Affects Versions: 2.0.0 >Reporter: Pedro Gonçalves Rossi Rodrigues >Priority: Minor > > The RangerSystemAccessControl > (https://github.com/apache/ranger/blob/master/ranger-presto-plugin-shim/src/main/java/org/apache/ranger/authorization/presto/authorizer/RangerSystemAccessControl.java) > which Presto invokes doesn't have a fundamental method that its interfaces > defaults to deny *checkCanShowColumnsMetadata* > ([https://github.com/prestosql/presto/blob/master/presto-spi/src/main/java/io/prestosql/spi/security/SystemAccessControl.java#L209)] > resulting in the fact that the Ranger-Admin cannot list any columns in the > interface for the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880669#comment-16880669 ] Bolke de Bruin commented on RANGER-2489: Oh interesting the commit info does not retain my id. (not worried just surprised) [~abhayk] thanks for merging > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16878539#comment-16878539 ] Bolke de Bruin commented on RANGER-2489: cc [~rmani] , [~abhayk] > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875844#comment-16875844 ] Bolke de Bruin edited comment on RANGER-2489 at 6/30/19 6:52 PM: - [~mehul] please merge this minor patch, it will improve the user experience for the presto plugin. was (Author: bolke): [~mehul] please merge this, it will improve the user experience for the presto plugin > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875844#comment-16875844 ] Bolke de Bruin commented on RANGER-2489: [~mehul] please merge this, it will improve the user experience for the presto plugin > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2489: --- Attachment: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-RANGER-2489-Minor-updates-to-presto-plugin.patch > > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2489) Missing dependencies in assembly for Presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2489: --- Description: If invoking with hostnames rather than ips extra dependencies are required by the plugin for Presto. commons-codec commons-codec com.kstruct gethostname4j com.sun jna was: If invoking with hostnames rather than ips extra dependencies are required by the plugin for Presto. commons-codec commons-codec-1.12 com.kstruct gethostname4j-0.0.3 com.sun jna-3.0.9.jar > Missing dependencies in assembly for Presto plugin > -- > > Key: RANGER-2489 > URL: https://issues.apache.org/jira/browse/RANGER-2489 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > > If invoking with hostnames rather than ips extra dependencies are required by > the plugin for Presto. > commons-codec commons-codec > com.kstruct gethostname4j > com.sun jna -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2489) Missing dependencies in assembly for Presto plugin
Bolke de Bruin created RANGER-2489: -- Summary: Missing dependencies in assembly for Presto plugin Key: RANGER-2489 URL: https://issues.apache.org/jira/browse/RANGER-2489 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Bolke de Bruin Assignee: Bolke de Bruin If invoking with hostnames rather than ips extra dependencies are required by the plugin for Presto. commons-codec commons-codec-1.12 com.kstruct gethostname4j-0.0.3 com.sun jna-3.0.9.jar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845722#comment-16845722 ] Bolke de Bruin commented on RANGER-2395: [~mehul] Excellent. What about merging the patch? Anything left to do? > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: master > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16845200#comment-16845200 ] Bolke de Bruin commented on RANGER-2395: Ping > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: master > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843368#comment-16843368 ] Bolke de Bruin commented on RANGER-2395: Wiki page added at [https://cwiki.apache.org/confluence/display/RANGER/Presto+Plugin] I'm not entirely confident with the WIki structure (isn't documentation as part of the release a better idea?) > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: master > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843231#comment-16843231 ] Bolke de Bruin commented on RANGER-2395: [~mehul] sure, but I don't have access to Ranger's cwiki. Can you add me? > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: master > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2395: --- Attachment: 0001-Add-Presto-plugin.patch > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Fix For: master > > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 1h > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2395: --- Attachment: (was: 0001-Add-Presto-plugin.patch) > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830217#comment-16830217 ] Bolke de Bruin commented on RANGER-2395: We are gathering production stats at the moment. > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-Add-Presto-plugin.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2395) Add presto plugin
[ https://issues.apache.org/jira/browse/RANGER-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2395: --- Attachment: 0001-Add-Presto-plugin.patch > Add presto plugin > - > > Key: RANGER-2395 > URL: https://issues.apache.org/jira/browse/RANGER-2395 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Bolke de Bruin >Assignee: Bolke de Bruin >Priority: Major > Attachments: 0001-Add-Presto-plugin.patch > > > Presto (or PrestoDB) is an open source, distributed SQL query engine, > designed from the ground up for fast analytic queries against data of any > size. It supports both non-relational sources, such as the Hadoop Distributed > File System (HDFS), [Amazon S3|https://aws.amazon.com/s3/], Cassandra, > MongoDB, and [HBase|https://aws.amazon.com/emr/details/hbase/], and > relational data sources such as MySQL, PostgreSQL, [Amazon > Redshift|https://aws.amazon.com/redshift/], Microsoft SQL Server, and > Teradata. > This is to track a Ranger plugin for Presto -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2388) db_setup is not using counTries properly
[
https://issues.apache.org/jira/browse/RANGER-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810243#comment-16810243
]
Bolke de Bruin commented on RANGER-2388:
if the schema is *not* created (due to an error) the *isSchemaCreate* will not
be set and the script will enter an endless loop. Besides it will always try 2
times to create the schema as countTries starts at 0.
> db_setup is not using counTries properly
> -
>
> Key: RANGER-2388
> URL: https://issues.apache.org/jira/browse/RANGER-2388
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Bolke de Bruin
>Priority: Major
>
> line 300:
>
> {code:java}
> while(isSchemaCreated==False or countTries<2):
>
> {code}
>
> should read
>
> {code:java}
> while(isSchemaCreated==False and countTries<2):{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2352) Ranger installation is failing for Oracle and Postgres DB
[ https://issues.apache.org/jira/browse/RANGER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806453#comment-16806453 ] Bolke de Bruin commented on RANGER-2352: Thanks for that. It indeed now works. I think it is smart to document this or detect it cause this kind of deployments are often templated > Ranger installation is failing for Oracle and Postgres DB > - > > Key: RANGER-2352 > URL: https://issues.apache.org/jira/browse/RANGER-2352 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Blocker > Fix For: 2.0.0 > > Attachments: > 0002-RANGER-2352-Ranger-installation-is-failing-for-Oracl.patch > > > Ranger installation is failing for Oracle and Postgres DB after RANGER-2341 > [commit|https://github.com/apache/ranger/commit/0f229b01e23b12d0c9e0c4ee3de817ce80d68a17#diff-efb49ec629fa12d2e5c69d37527d2984] > > It seems RANGER-2327 commits are reverted by mistake while merging code of > RANGER-2341. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2352) Ranger installation is failing for Oracle and Postgres DB
[ https://issues.apache.org/jira/browse/RANGER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806443#comment-16806443 ] Bolke de Bruin commented on RANGER-2352: Ah let me check, I might have been using an older install.properties file Please note: Its been working up till now without any issues and we run it in production on 10. In addition, Postgres 9.4 was released on 2014-12-18, and I dont think anything before 9.4 (<9.4) is supported by Postgres anymore. So it might be time to up the requirements. > Ranger installation is failing for Oracle and Postgres DB > - > > Key: RANGER-2352 > URL: https://issues.apache.org/jira/browse/RANGER-2352 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Blocker > Fix For: 2.0.0 > > Attachments: > 0002-RANGER-2352-Ranger-installation-is-failing-for-Oracl.patch > > > Ranger installation is failing for Oracle and Postgres DB after RANGER-2341 > [commit|https://github.com/apache/ranger/commit/0f229b01e23b12d0c9e0c4ee3de817ce80d68a17#diff-efb49ec629fa12d2e5c69d37527d2984] > > It seems RANGER-2327 commits are reverted by mistake while merging code of > RANGER-2341. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2352) Ranger installation is failing for Oracle and Postgres DB
[
https://issues.apache.org/jira/browse/RANGER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806409#comment-16806409
]
Bolke de Bruin commented on RANGER-2352:
This is on a clean install on both Postgres 10.3 and Postgres 11. Manual (ie.
python dba_setup.py -q && python db_setup.py) and a docker build.
{code:java}
ranger=# select * from x_db_version_h;
id | version | inst_at | inst_by |
updated_at | updated_by | active
+++---++-+
1 | CORE_DB_SCHEMA | 2019-04-01 07:50:58.736859 | Ranger 2.0.0-SNAPSHOT |
2019-04-01 07:50:58.736859 | macbook-pro.localdomain | N
(1 row){code}
> Ranger installation is failing for Oracle and Postgres DB
> -
>
> Key: RANGER-2352
> URL: https://issues.apache.org/jira/browse/RANGER-2352
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments:
> 0002-RANGER-2352-Ranger-installation-is-failing-for-Oracl.patch
>
>
> Ranger installation is failing for Oracle and Postgres DB after RANGER-2341
> [commit|https://github.com/apache/ranger/commit/0f229b01e23b12d0c9e0c4ee3de817ce80d68a17#diff-efb49ec629fa12d2e5c69d37527d2984]
>
> It seems RANGER-2327 commits are reverted by mistake while merging code of
> RANGER-2341.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2388) db_setup is not using counTries properly
Bolke de Bruin created RANGER-2388:
--
Summary: db_setup is not using counTries properly
Key: RANGER-2388
URL: https://issues.apache.org/jira/browse/RANGER-2388
Project: Ranger
Issue Type: Bug
Components: admin
Affects Versions: master
Reporter: Bolke de Bruin
line 300:
{code:java}
while(isSchemaCreated==False or countTries<2):
{code}
should read
{code:java}
while(isSchemaCreated==False and countTries<2):{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-2352) Ranger installation is failing for Oracle and Postgres DB
[
https://issues.apache.org/jira/browse/RANGER-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806245#comment-16806245
]
Bolke de Bruin commented on RANGER-2352:
Is this really resolved [~pradeep.agrawal]? Trying to install Ranger from
master gives me an endless loop on Postgres:
{code:java}
2019-03-31 21:16:32,390 [I] Importing DB schema to database ranger from file:
xa_core_db_postgres.sql
2019-03-31 21:16:32,390 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -input
/private/tmp/ranger-2.0.0-SNAPSHOT-admin/db/postgres/xa_core_db_postgres.sql
2019-03-31 21:16:33,197 [I] xa_core_db_postgres.sql file imported successfully
2019-03-31 21:16:33,197 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -query "update x_db_version_h set inst_by='Ranger 2.0.0-SNAPSHOT' where
active='Y' and updated_by='localhost';"
2019-03-31 21:16:33,488 [I] Patches status entries updated from base ranger
version to current installed ranger version:Ranger 2.0.0-SNAPSHOT
2019-03-31 21:16:33,488 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -query "select * from (select table_name from information_schema.tables
where table_catalog='ranger' and table_name = 'x_portal_user') as temp;"
2019-03-31 21:16:33,739 [I] Table x_portal_user already exists in database
'ranger'
2019-03-31 21:16:33,740 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -query "select * from (select table_name from information_schema.tables
where table_catalog='ranger' and table_name = 'x_policy_ref_group') as temp;"
2019-03-31 21:16:34,022 [I] Table x_policy_ref_group does not exist in
database ranger
2019-03-31 21:16:34,023 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -query "select version from x_db_version_h where version = 'DB_PATCHES' and
active = 'Y';"
2019-03-31 21:16:34,296 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -query "select version from x_db_version_h where version = 'JAVA_PATCHES'
and active = 'Y';"
2019-03-31 21:16:34,611 [I] Importing DB schema to database ranger from file:
xa_core_db_postgres.sql
2019-03-31 21:16:34,612 [JISQL]
/Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/bin/java -cp
/tmp/postgresql-42.2.1.jar:/private/tmp/ranger-2.0.0-SNAPSHOT-admin/jisql/lib/*
org.apache.util.sql.Jisql -driver postgresql -cstring
jdbc:postgresql://localhost/ranger -u ranger -p '' -noheader -trim -c
\; -input
/private/tmp/ranger-2.0.0-SNAPSHOT-admin/db/postgres/xa_core_db_postgres.sql
2019-03-31 21:16:35,530 [I] xa_core_db_postgres.sql file imported
successfully{code}
> Ranger installation is failing for Oracle and Postgres DB
> -
>
> Key: RANGER-2352
> URL: https://issues.apache.org/jira/browse/RANGER-2352
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.0.0
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Blocker
> Fix For: 2.0.0
>
> Attachments:
> 0002-RANGER-2352-Ranger-installation-is-failing-for-Oracl.patch
>
>
> Ranger installation is failing for Oracle and Postgres DB after RANGER-2341
> [commit|https://github.com/apache/ranger/commit/0f229b01e23b12d0c9e0c4ee3de817ce80d68a17#diff-efb49ec629fa12d2e5c69d37527d2984]
>
> It seems RANGER-2327 commits are
[jira] [Commented] (RANGER-2370) Hadoop-common should be shaded in agents-common and agents-audit
[ https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16800979#comment-16800979 ] Bolke de Bruin commented on RANGER-2370: [~madhan.neethiraj] We still see issues that due to e.g. Guava being loaded by Presto on the classpath earlier than the ranger-plugin-classloader is instantiated it sill has conflicting libraries. Is the pattern with other implementations to load the classloader somehow earlier and thus making the presto patch more invasive? Do you have an example where that is done? > Hadoop-common should be shaded in agents-common and agents-audit > > > Key: RANGER-2370 > URL: https://issues.apache.org/jira/browse/RANGER-2370 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 1.2.0 >Reporter: Bolke de Bruin >Priority: Critical > > Hadoop-common pulls in a lot of dependencies, particularly Guava, Jersey that > are also often used in other projects. Guava and Jersey are particularly > notorious for being 'tough' dependencies as they are not backwards compatible. > As 'ranger-plugin-common' and 'ranger-plugins-audit' are to be integrated > with 3rd party services this poses serious challenges. For example the Presto > plugin (see linked issue) is currently blocked due to the reliance of Presto > on Jersey 2, while Hadoop/Ranger use Jersey 1.X. > An example of how to shade Hadoop Common can be found here: > [https://github.com/gchq/hadoop-common-shaded/] . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2370) Hadoop-common should be shaded in agents-common and agents-audit
[ https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794363#comment-16794363 ] Bolke de Bruin commented on RANGER-2370: Good point. Will have a look and report back. > Hadoop-common should be shaded in agents-common and agents-audit > > > Key: RANGER-2370 > URL: https://issues.apache.org/jira/browse/RANGER-2370 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 1.2.0 >Reporter: Bolke de Bruin >Priority: Critical > > Hadoop-common pulls in a lot of dependencies, particularly Guava, Jersey that > are also often used in other projects. Guava and Jersey are particularly > notorious for being 'tough' dependencies as they are not backwards compatible. > As 'ranger-plugin-common' and 'ranger-plugins-audit' are to be integrated > with 3rd party services this poses serious challenges. For example the Presto > plugin (see linked issue) is currently blocked due to the reliance of Presto > on Jersey 2, while Hadoop/Ranger use Jersey 1.X. > An example of how to shade Hadoop Common can be found here: > [https://github.com/gchq/hadoop-common-shaded/] . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2370) Hadoop-common should be shaded in agents-common and agents-audit
[ https://issues.apache.org/jira/browse/RANGER-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bolke de Bruin updated RANGER-2370: --- Issue Type: Improvement (was: Bug) > Hadoop-common should be shaded in agents-common and agents-audit > > > Key: RANGER-2370 > URL: https://issues.apache.org/jira/browse/RANGER-2370 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 1.2.0 >Reporter: Bolke de Bruin >Priority: Critical > > Hadoop-common pulls in a lot of dependencies, particularly Guava, Jersey that > are also often used in other projects. Guava and Jersey are particularly > notorious for being 'tough' dependencies as they are not backwards compatible. > As 'ranger-plugin-common' and 'ranger-plugins-audit' are to be integrated > with 3rd party services this poses serious challenges. For example the Presto > plugin (see linked issue) is currently blocked due to the reliance of Presto > on Jersey 2, while Hadoop/Ranger use Jersey 1.X. > An example of how to shade Hadoop Common can be found here: > [https://github.com/gchq/hadoop-common-shaded/] . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2370) Hadoop-common should be shaded in agents-common and agents-audit
Bolke de Bruin created RANGER-2370: -- Summary: Hadoop-common should be shaded in agents-common and agents-audit Key: RANGER-2370 URL: https://issues.apache.org/jira/browse/RANGER-2370 Project: Ranger Issue Type: Bug Components: plugins Affects Versions: 1.2.0 Reporter: Bolke de Bruin Hadoop-common pulls in a lot of dependencies, particularly Guava, Jersey that are also often used in other projects. Guava and Jersey are particularly notorious for being 'tough' dependencies as they are not backwards compatible. As 'ranger-plugin-common' and 'ranger-plugins-audit' are to be integrated with 3rd party services this poses serious challenges. For example the Presto plugin (see linked issue) is currently blocked due to the reliance of Presto on Jersey 2, while Hadoop/Ranger use Jersey 1.X. An example of how to shade Hadoop Common can be found here: [https://github.com/gchq/hadoop-common-shaded/] . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2302) Clients should be able to add tag information to access requests
[
https://issues.apache.org/jira/browse/RANGER-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bolke de Bruin updated RANGER-2302:
---
Flags: Patch
> Clients should be able to add tag information to access requests
>
>
> Key: RANGER-2302
> URL: https://issues.apache.org/jira/browse/RANGER-2302
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
>Affects Versions: 1.2.0
>Reporter: Bolke de Bruin
>Priority: Major
> Labels: tags
> Attachments: 0001-RANGER-2302-Add-client-tags.patch
>
>
> Ranger currently assumes that clients are tag unaware. It, for example, syncs
> tag information with Atlas. This has several issues:
> # It assumes Ranger is the single source of truth connecting resource and
> tag information
> # As the tagsync is not happening realtime (either due to Kafka delay or due
> to caching) security issues can pop up. E.g. copy a file with PII info to
> different location has a time window that Ranger is unaware of the tag.
> If the client is tag aware it could supply the tags that it knows of as part
> of the request. This ensures immediate availability and propagation of tags.
> A backward compatible implementation could be to use
> {color:#9876aa}KEY_USER_TAGS {color}with a delimiter as part of the
> RangerAccessResource request and have RangerTagEnricher pick up these tags
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2302) Clients should be able to add tag information to access requests
[
https://issues.apache.org/jira/browse/RANGER-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bolke de Bruin updated RANGER-2302:
---
Attachment: 0001-RANGER-2302-Add-client-tags.patch
> Clients should be able to add tag information to access requests
>
>
> Key: RANGER-2302
> URL: https://issues.apache.org/jira/browse/RANGER-2302
> Project: Ranger
> Issue Type: Bug
> Components: tagsync
>Affects Versions: 1.2.0
>Reporter: Bolke de Bruin
>Priority: Major
> Labels: tags
> Attachments: 0001-RANGER-2302-Add-client-tags.patch
>
>
> Ranger currently assumes that clients are tag unaware. It, for example, syncs
> tag information with Atlas. This has several issues:
> # It assumes Ranger is the single source of truth connecting resource and
> tag information
> # As the tagsync is not happening realtime (either due to Kafka delay or due
> to caching) security issues can pop up. E.g. copy a file with PII info to
> different location has a time window that Ranger is unaware of the tag.
> If the client is tag aware it could supply the tags that it knows of as part
> of the request. This ensures immediate availability and propagation of tags.
> A backward compatible implementation could be to use
> {color:#9876aa}KEY_USER_TAGS {color}with a delimiter as part of the
> RangerAccessResource request and have RangerTagEnricher pick up these tags
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2302) Clients should be able to add tag information to access requests
Bolke de Bruin created RANGER-2302:
--
Summary: Clients should be able to add tag information to access
requests
Key: RANGER-2302
URL: https://issues.apache.org/jira/browse/RANGER-2302
Project: Ranger
Issue Type: Bug
Components: tagsync
Affects Versions: 1.2.0
Reporter: Bolke de Bruin
Ranger currently assumes that clients are tag unaware. It, for example, syncs
tag information with Atlas. This has several issues:
# It assumes Ranger is the single source of truth connecting resource and tag
information
# As the tagsync is not happening realtime (either due to Kafka delay or due
to caching) security issues can pop up. E.g. copy a file with PII info to
different location has a time window that Ranger is unaware of the tag.
If the client is tag aware it could supply the tags that it knows of as part of
the request. This ensures immediate availability and propagation of tags.
A backward compatible implementation could be to use
{color:#9876aa}KEY_USER_TAGS {color}with a delimiter as part of the
RangerAccessResource request and have RangerTagEnricher pick up these tags
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-1480) Implement plugin for Druid
[ https://issues.apache.org/jira/browse/RANGER-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668285#comment-16668285 ] Bolke de Bruin commented on RANGER-1480: Where are we with this patch? Not much progress has been made over a year, but it would be very welcome to have this in. Druid is now also an Apache project. > Implement plugin for Druid > -- > > Key: RANGER-1480 > URL: https://issues.apache.org/jira/browse/RANGER-1480 > Project: Ranger > Issue Type: New Feature > Components: admin, plugins >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-1480-Second-version-of-the-druid-plugin.patch > > > Druid is a high-performance, column-oriented, distributed data store, which > has an extension mechanism to incorporate various functionalities, for > example an external authorization system - just like ranger. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1300) S3 support
[ https://issues.apache.org/jira/browse/RANGER-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16658309#comment-16658309 ] Bolke de Bruin commented on RANGER-1300: Update we have set a team to work at this. We have created a S3 proxy that is now MVP. It works for on prem situations in front of Ceph/RadosGW or (with some modifications) in case you can assure a proxy in front of Amazon S3. We have created 2 different services to support this. * [https://github.com/ing-bank/airlock-sts] which implements a subset of Amazon's STS * [https://github.com/ing-bank/airlock] the actual proxy Lineage is recorded in Atlas if configured to do so. We probably split this off when Airlock starts supporting bucket notifications per S3 bucket notifications. Both are Apache 2 licensed and we do accept pull requests. Have a look at the architecture and try it out. P.S. It obviously does not sync Ranger policies with S3 policies. We dont have such a need (yet). We will accept changes to support this if required. > S3 support > -- > > Key: RANGER-1300 > URL: https://issues.apache.org/jira/browse/RANGER-1300 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Jose >Priority: Major > Attachments: ranger-servicedef-aws-s3.json > > > As more and more people are deploying hadoop into AWS and as S3 is used in > lots of application. It'd be nice to have S3 support built into Ranger. > It's not a trivial task. Right now Ranger Storage support (only hdfs) runs > directly in the Namenode -- This message was sent by Atlassian JIRA (v7.6.3#76005)
