[
https://issues.apache.org/jira/browse/RANGER-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522133#comment-17522133
]
rujia commented on RANGER-3182:
---
[~aakashnand] i can't find any define for commons.lang3.v
[
https://issues.apache.org/jira/browse/RANGER-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460530#comment-17460530
]
rujia commented on RANGER-2892:
---
[~bpatel] Yes, Other plugins are able to write.
> NoClas
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271153#comment-17271153
]
rujia commented on RANGER-3155:
---
Thanks [~maheshbandal]. About case2, i think the the resp
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3155:
--
Attachment: screenshot-3.png
> Roles are not accessible for Admin User through REST API
>
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3155:
--
Attachment: screenshot-2.png
> Roles are not accessible for Admin User through REST API
>
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3155:
--
Attachment: screenshot-1.png
> Roles are not accessible for Admin User through REST API
>
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269758#comment-17269758
]
rujia commented on RANGER-3155:
---
[~maheshbandal] So, follow your code, can you recheck the
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269280#comment-17269280
]
rujia edited comment on RANGER-3155 at 1/21/21, 1:05 PM:
-
Hi [~m
[
https://issues.apache.org/jira/browse/RANGER-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269280#comment-17269280
]
rujia commented on RANGER-3155:
---
Hi [~maheshbandal] there is a main point that none-admin
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269267#comment-17269267
]
rujia commented on RANGER-3136:
---
[~maheshbandal] I got your point, but i think apply resou
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269167#comment-17269167
]
rujia edited comment on RANGER-3135 at 1/21/21, 9:26 AM:
-
Hi [~m
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269167#comment-17269167
]
rujia commented on RANGER-3135:
---
Hi [~maheshbandal], i have submit
https://issues.apache.
[
https://issues.apache.org/jira/browse/RANGER-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3154:
--
Attachment: 0001-fix-rest-API-result-of-getRoleByName-admin-user-can-.patch
> Admin user cann't get role info
rujia created RANGER-3154:
-
Summary: Admin user cann't get role info throught rest API
Key: RANGER-3154
URL: https://issues.apache.org/jira/browse/RANGER-3154
Project: Ranger
Issue Type: Bug
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269062#comment-17269062
]
rujia commented on RANGER-3136:
---
so the main point now is: Whether to add "Service Name" t
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269058#comment-17269058
]
rujia commented on RANGER-3136:
---
[~maheshbandal] Oh, https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269010#comment-17269010
]
rujia commented on RANGER-3136:
---
[~maheshbandal] Maybe the different is my ranger is witho
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269008#comment-17269008
]
rujia edited comment on RANGER-3136 at 1/21/21, 3:27 AM:
-
[~mahe
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269008#comment-17269008
]
rujia edited comment on RANGER-3136 at 1/21/21, 3:27 AM:
-
[~mahe
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269008#comment-17269008
]
rujia edited comment on RANGER-3136 at 1/21/21, 3:27 AM:
-
[~mahe
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269008#comment-17269008
]
rujia edited comment on RANGER-3136 at 1/21/21, 3:26 AM:
-
[~mahe
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269008#comment-17269008
]
rujia commented on RANGER-3136:
---
[~maheshbandal] The similar procedure as you i do, but i
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268343#comment-17268343
]
rujia commented on RANGER-3135:
---
[~maheshbandal] Thanks for your reply. I will recheck th
[
https://issues.apache.org/jira/browse/RANGER-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3137:
--
Attachment: 0001-add-select-permission-for-lookup-user-in-hive-agent.patch
> Lookup user should has 'Select' p
rujia created RANGER-3137:
-
Summary: Lookup user should has 'Select' permission for all
resource in hive-agent
Key: RANGER-3137
URL: https://issues.apache.org/jira/browse/RANGER-3137
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3136:
--
Attachment: 0001-NUllPointException-occur-when-import-polices-anf-isO.patch
> NullPointException found when im
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3135:
--
Attachment: 0001-optimze-log-print-for-querying-roles.patch
> Ranger always ponit out "User does not have perm
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3135:
--
Attachment: (was: 0001-optimze-log-print-for-querying-roles.patch)
> Ranger always ponit out "User does no
[
https://issues.apache.org/jira/browse/RANGER-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3136:
--
Description: i got NullPointException when i imported policies json file
from rangeradmin web, i selected "isO
rujia created RANGER-3136:
-
Summary: NullPointException found when import policies form web
side and "isOverride" is selected
Key: RANGER-3136
URL: https://issues.apache.org/jira/browse/RANGER-3136
Project: R
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3135:
--
Attachment: 0001-optimze-log-print-for-querying-roles.patch
> Ranger always ponit out "User does not have perm
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3135:
--
Description:
when i access /role/name/{name}, a Exception "User does not have permission for
this operation"
[
https://issues.apache.org/jira/browse/RANGER-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3135:
--
Description:
when i access /role/name/{name} , a Exception "User does not have permission
for this operation"
rujia created RANGER-3135:
-
Summary: Ranger always ponit out "User does not have permission
for this operation" when user try to query a none-exist role
Key: RANGER-3135
URL: https://issues.apache.org/jira/browse/RANGER-3
[
https://issues.apache.org/jira/browse/RANGER-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3113:
--
Attachment: (was:
0001-plugin-kafka-use-alter-instead-of-configure.patch)
> AccessType 'configure' should
rujia created RANGER-3113:
-
Summary: AccessType 'configure' should be replaced by 'alter' in
plugin-kafka
Key: RANGER-3113
URL: https://issues.apache.org/jira/browse/RANGER-3113
Project: Ranger
Issu
[
https://issues.apache.org/jira/browse/RANGER-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3113:
--
Attachment: 0001-plugin-kafka-use-alter-instead-of-configure.patch
> AccessType 'configure' should be replaced
[
https://issues.apache.org/jira/browse/RANGER-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247107#comment-17247107
]
rujia edited comment on RANGER-2640 at 12/10/20, 9:10 AM:
--
this
[
https://issues.apache.org/jira/browse/RANGER-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247107#comment-17247107
]
rujia commented on RANGER-2640:
---
this patch will be good, can u update the patch based on
[
https://issues.apache.org/jira/browse/RANGER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3092:
--
Comment: was deleted
(was: yes，i'm planning to repair it soon:))
> KMS fails to start with NullPointerExcepti
[
https://issues.apache.org/jira/browse/RANGER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242838#comment-17242838
]
rujia commented on RANGER-3092:
---
yes，i'm planning to repair it soon:)
> KMS fails to star
[
https://issues.apache.org/jira/browse/RANGER-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241225#comment-17241225
]
rujia commented on RANGER-3092:
---
it seems kms server doesn't contains log4j.properties par
[
https://issues.apache.org/jira/browse/RANGER-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3042:
--
Attachment: 0001-plugin-presto-some-log-mistake-fix.patch
> plugin-presto: some log issues should be fixed
> -
[
https://issues.apache.org/jira/browse/RANGER-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3042:
--
Description:
some log issues should be fixed about log or exception about presto plugin
{code:java}
@Over
[
https://issues.apache.org/jira/browse/RANGER-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3042:
--
Description:
some log issues should be fixed about log or exception about presto plugin
{code:java}
@Over
rujia created RANGER-3042:
-
Summary: plugin-presto: some log issues should be fixed
Key: RANGER-3042
URL: https://issues.apache.org/jira/browse/RANGER-3042
Project: Ranger
Issue Type: Bug
C
[
https://issues.apache.org/jira/browse/RANGER-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3041:
--
Attachment: 0001-default-database-policy-update-for-hive-pulgin.patch
> hive-plugin: default policy 'default d
rujia created RANGER-3041:
-
Summary: hive-plugin: default policy 'default database tables
columns' should contains permission of lookupuser and {OWNER}
Key: RANGER-3041
URL: https://issues.apache.org/jira/browse/RANGER-30
[
https://issues.apache.org/jira/browse/RANGER-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3040:
--
Attachment: 0001-add-read-permission-for-lookupuser-on-default-polici.patch
> There is no read permission for
[
https://issues.apache.org/jira/browse/RANGER-3040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3040:
--
Description: lookupuser should has read permission for all components by
default, otherwise the function of lo
rujia created RANGER-3040:
-
Summary: There is no read permission for lookupuser on
presto/storm/es by default
Key: RANGER-3040
URL: https://issues.apache.org/jira/browse/RANGER-3040
Project: Ranger
rujia created RANGER-3039:
-
Summary: plugin-hive: user belongs to role 'admin' should has
access to execute dfs command
Key: RANGER-3039
URL: https://issues.apache.org/jira/browse/RANGER-3039
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3039:
--
Attachment: 0001-user-belongs-to-role-admin-should-has-access-to-exec.patch
> plugin-hive: user belongs to rol
[
https://issues.apache.org/jira/browse/RANGER-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3035:
--
Attachment: 0001-plugin-presto-M-M-user-can-not-access.patch
> Ranger Presto Plugin: Machine-Machine user can
rujia created RANGER-3035:
-
Summary: Ranger Presto Plugin: Machine-Machine user can not access
presto with right permission
Key: RANGER-3035
URL: https://issues.apache.org/jira/browse/RANGER-3035
Project: Ran
[
https://issues.apache.org/jira/browse/RANGER-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3033:
--
Attachment: 0001-hive-authorizer-should-impl-getRoleGrantInfoForPrinc.patch
> Ranger hive authorizer should im
rujia created RANGER-3033:
-
Summary: Ranger hive authorizer should impl
'getRoleGrantInfoForPrincipal' interface
Key: RANGER-3033
URL: https://issues.apache.org/jira/browse/RANGER-3033
Project: Ranger
[
https://issues.apache.org/jira/browse/RANGER-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-3032:
--
Attachment: 0001-make-rangeradmin-log4j-dynamically.patch
> The log4j properties of rangeradmin cannot take ef
rujia created RANGER-3032:
-
Summary: The log4j properties of rangeradmin cannot take effect
dynamically
Key: RANGER-3032
URL: https://issues.apache.org/jira/browse/RANGER-3032
Project: Ranger
Issue
[
https://issues.apache.org/jira/browse/RANGER-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2912:
--
Attachment: 0001-issue-fix-for-es-audit.patch
> ranger and plugins will throw GSSAPI error when write audit lo
rujia created RANGER-2912:
-
Summary: ranger and plugins will throw GSSAPI error when write
audit log to ElasticSearch when cluster running on none security mode
Key: RANGER-2912
URL: https://issues.apache.org/jira/browse/
[
https://issues.apache.org/jira/browse/RANGER-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17158015#comment-17158015
]
rujia commented on RANGER-2911:
---
review link : [https://reviews.apache.org/r/72684/]
> ES
[
https://issues.apache.org/jira/browse/RANGER-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2911:
--
Attachment: 0001-Add-ES-Plugin-Request-support.patch
> ES plugin missing implemention for some ES request
>
rujia created RANGER-2911:
-
Summary: ES plugin missing implemention for some ES request
Key: RANGER-2911
URL: https://issues.apache.org/jira/browse/RANGER-2911
Project: Ranger
Issue Type: Bug
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156685#comment-17156685
]
rujia commented on RANGER-2891:
---
this interface has been deleted since presto version 331,
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia resolved RANGER-2891.
---
Resolution: Won't Fix
> Add checkCanShowColumnsMetadata for presto plugin
>
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2891:
--
Attachment: 0002-Add-checkCanShowColumnsMetadata-for-presto-plugin.patch
> Add checkCanShowColumnsMetadata for
[
https://issues.apache.org/jira/browse/RANGER-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2892:
--
Attachment: (was:
0001-ElasticSearch-plugin-NullPointException-fix.patch)
> NoClassDeFoundError occur whe
[
https://issues.apache.org/jira/browse/RANGER-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2892:
--
Attachment: 0001-ElasticSearch-plugin-NullPointException-fix.patch
> NoClassDeFoundError occur when HDFS write
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2891:
--
Description: plugin-presto does not support
> Add checkCanShowColumnsMetadata for presto plugin
> ---
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2891:
--
Description: plugin-presto does not support 'checkCanShowColumnsMetadata'
API now, i think it should be implem
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150893#comment-17150893
]
rujia commented on RANGER-2890:
---
[~rmani] thanks for your reminder， i have created review
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2890:
--
Description: Currently, plugins missing log4j properties in their audit
conf, it need be added for plugins and
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150848#comment-17150848
]
rujia commented on RANGER-2890:
---
Thanks for your reminder，i have created review request:
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2891:
--
Attachment: 0001-Add-checkCanShowColumnsMetadata-for-presto-plugin.patch
> Add checkCanShowColumnsMetadata for
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2890:
--
Comment: was deleted
(was: Thanks for your reminder，i have created review request:
[https://reviews.apache.or
rujia created RANGER-2892:
-
Summary: NoClassDeFoundError occur when HDFS write audit to ES
Key: RANGER-2892
URL: https://issues.apache.org/jira/browse/RANGER-2892
Project: Ranger
Issue Type: Bug
[
https://issues.apache.org/jira/browse/RANGER-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150895#comment-17150895
]
rujia commented on RANGER-2891:
---
[~rmani] thanks, pls see : [https://reviews.apache.org
rujia created RANGER-2891:
-
Summary: Add checkCanShowColumnsMetadata for presto plugin
Key: RANGER-2891
URL: https://issues.apache.org/jira/browse/RANGER-2891
Project: Ranger
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2890:
--
Summary: Add missing log4j properties for audit log (was: Add missing
log4j propertis for audit log)
> Add m
[
https://issues.apache.org/jira/browse/RANGER-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2890:
--
Attachment: 0001-aduit-for-log4j.patch
> Add missing log4j propertis for audit log
> -
rujia created RANGER-2890:
-
Summary: Add missing log4j propertis for audit log
Key: RANGER-2890
URL: https://issues.apache.org/jira/browse/RANGER-2890
Project: Ranger
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/RANGER-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2810:
--
Attachment: 0001-kafka-authorizer-ticket-expired-fix.patch
> Kafka with Ranger plugin will fail
>
[
https://issues.apache.org/jira/browse/RANGER-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2877:
--
Attachment: 0001-ElasticSearch-plugin-NullPointException-fix.patch
> ElasticSearch-Plugin throws NullPointExce
[
https://issues.apache.org/jira/browse/RANGER-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147519#comment-17147519
]
rujia edited comment on RANGER-2810 at 6/29/20, 7:03 AM:
-
this p
[
https://issues.apache.org/jira/browse/RANGER-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147519#comment-17147519
]
rujia edited comment on RANGER-2810 at 6/29/20, 7:02 AM:
-
this p
[
https://issues.apache.org/jira/browse/RANGER-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147519#comment-17147519
]
rujia edited comment on RANGER-2810 at 6/29/20, 3:36 AM:
-
this p
[
https://issues.apache.org/jira/browse/RANGER-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147519#comment-17147519
]
rujia commented on RANGER-2810:
---
this problem is caused by kafka run witout core-site.xml,
[
https://issues.apache.org/jira/browse/RANGER-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2877:
--
Attachment: ES Processing logic.png
> ElasticSearch-Plugin throws NullPointException when the type of request
[
https://issues.apache.org/jira/browse/RANGER-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rujia updated RANGER-2877:
--
Attachment: NullPointException.png
> ElasticSearch-Plugin throws NullPointException when the type of request i
rujia created RANGER-2877:
-
Summary: ElasticSearch-Plugin throws NullPointException when the
type of request is 'PutMappingRequest'
Key: RANGER-2877
URL: https://issues.apache.org/jira/browse/RANGER-2877
Proj
91 matches
Mail list logo
