[jira] [Updated] (RANGER-5098) Release Apache Ranger 2.6.0
[ https://issues.apache.org/jira/browse/RANGER-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5098: --- Affects Version/s: (was: 2.5.0) > Release Apache Ranger 2.6.0 > --- > > Key: RANGER-5098 > URL: https://issues.apache.org/jira/browse/RANGER-5098 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.6.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > To track tasks for the ranger 2.6 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5098) Release Apache Ranger 2.6.0
[ https://issues.apache.org/jira/browse/RANGER-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5098: --- Affects Version/s: 2.6.0 > Release Apache Ranger 2.6.0 > --- > > Key: RANGER-5098 > URL: https://issues.apache.org/jira/browse/RANGER-5098 > Project: Ranger > Issue Type: Task > Components: Ranger >Affects Versions: 2.5.0, 2.6.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > To track tasks for the ranger 2.6 release. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5100) Update Apache Ranger website with 2.6.0
[ https://issues.apache.org/jira/browse/RANGER-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927009#comment-17927009 ] Abhishek Kumar commented on RANGER-5100: PR available: [https://github.com/apache/ranger/pull/532] > Update Apache Ranger website with 2.6.0 > --- > > Key: RANGER-5100 > URL: https://issues.apache.org/jira/browse/RANGER-5100 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5101) Publish Apache Ranger release 2.6.0 artifacts
[ https://issues.apache.org/jira/browse/RANGER-5101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927008#comment-17927008 ] Abhishek Kumar commented on RANGER-5101: Source and checksum artifacts are now available at: https://dist.apache.org/repos/dist/release/ranger/2.6.0/ > Publish Apache Ranger release 2.6.0 artifacts > - > > Key: RANGER-5101 > URL: https://issues.apache.org/jira/browse/RANGER-5101 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.6.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4991) GDS policy evaluation to support data masking and row filtering
[ https://issues.apache.org/jira/browse/RANGER-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4991: --- Fix Version/s: (was: 2.6.0) > GDS policy evaluation to support data masking and row filtering > --- > > Key: RANGER-4991 > URL: https://issues.apache.org/jira/browse/RANGER-4991 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4991.patch > > > GDS model support specifying data masking and row filtering to be specified > while adding resources to data shares. GDS policy engine should be updated to > process data masking and row filtering while evaluating access requests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5063) tagsync module: update for code readability improvement
[ https://issues.apache.org/jira/browse/RANGER-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5063: --- Fix Version/s: 3.0.0 > tagsync module: update for code readability improvement > --- > > Key: RANGER-5063 > URL: https://issues.apache.org/jira/browse/RANGER-5063 > Project: Ranger > Issue Type: Sub-task > Components: tagsync >Reporter: Madhan Neethiraj >Assignee: Fateh Singh >Priority: Major > Fix For: 3.0.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5054) ranger-authn module: update for code readability improvement
[ https://issues.apache.org/jira/browse/RANGER-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5054: --- Fix Version/s: 3.0.0 > ranger-authn module: update for code readability improvement > > > Key: RANGER-5054 > URL: https://issues.apache.org/jira/browse/RANGER-5054 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5047) plugin-presto module: update for code readability improvement
[ https://issues.apache.org/jira/browse/RANGER-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5047: --- Fix Version/s: 3.0.0 > plugin-presto module: update for code readability improvement > - > > Key: RANGER-5047 > URL: https://issues.apache.org/jira/browse/RANGER-5047 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4980) Delete permissions on directory is denied which has hierarchy of files/directory rooted at the argument passed to the HDFS command
[ https://issues.apache.org/jira/browse/RANGER-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4980: --- Fix Version/s: 2.6.0 > Delete permissions on directory is denied which has hierarchy of > files/directory rooted at the argument passed to the HDFS command > -- > > Key: RANGER-4980 > URL: https://issues.apache.org/jira/browse/RANGER-4980 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 3.0.0, 2.5.0 >Reporter: Mahesh Bandal >Assignee: Mahesh Bandal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > > when chained plugin is enabled and all access is provided to a directory > which has multiple files and directories under it and if a user tries to > delete a that directory then access is denied. > Steps to repro: > * create a policy which will grant all access to systest user on a directory. > * Try performing write access. It should allow. > * hdfs dfs -mkdir /user/data/part_default1/state=98/dir1 > * Now, remove default ACL's on hdfs path > * hdfs dfs -chmod -R +000 /user/data/part_default1/ > * Now, try delete operation. Access will be denied. > * hdfs dfs -rm -r -skipTrash /user/data/part_default1/state=98 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4984) Ranger "Federated User" enum order should be correct to avoid potential failure in Ranger Admin
[ https://issues.apache.org/jira/browse/RANGER-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4984: --- Fix Version/s: 2.6.0 > Ranger "Federated User" enum order should be correct to avoid potential > failure in Ranger Admin > > > Key: RANGER-4984 > URL: https://issues.apache.org/jira/browse/RANGER-4984 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: > 0001-RANGER-4984-Ranger-Federated-User-enum-order-should-.patch > > > Ranger "Federated User" enum order should be correct to avoid potential > failure in Ranger Admin . Currently the enum USER_FEDERATED is replaced the > USER_AD enum. Even though USER_AD not used any where in Ranger is better to > avoid replacing and have a new Enum for Federated User. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4990) Rationalize processing of match-types for policy and tag evaluation
[ https://issues.apache.org/jira/browse/RANGER-4990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4990: --- Fix Version/s: 2.6.0 > Rationalize processing of match-types for policy and tag evaluation > --- > > Key: RANGER-4990 > URL: https://issues.apache.org/jira/browse/RANGER-4990 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Major > Fix For: 2.6.0 > > > Policies/tags are selected for processing based on how the they match the > accessed resource. The logic for the selection of policies/tags depends on > # resourceMatchingScope specified in the access request, and > # if the type of access desired is of type 'any'. > The logic for the selection is inconsistent and hard to reason about. > Additionally, code referencing the resourceMatchingScope does not check for > null-ness. This may cause NullPointerExceptions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4925) Cache downloaded archives during CI docker build
[ https://issues.apache.org/jira/browse/RANGER-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4925: --- Fix Version/s: 2.6.0 > Cache downloaded archives during CI docker build > > > Key: RANGER-4925 > URL: https://issues.apache.org/jira/browse/RANGER-4925 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0, 2.6.0 > > > Cache downloaded archives (as part of docker build) in CI runs to optimize > docker build times. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4991) GDS policy evaluation to support data masking and row filtering
[ https://issues.apache.org/jira/browse/RANGER-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4991: --- Fix Version/s: 2.6.0 > GDS policy evaluation to support data masking and row filtering > --- > > Key: RANGER-4991 > URL: https://issues.apache.org/jira/browse/RANGER-4991 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: RANGER-4991.patch > > > GDS model support specifying data masking and row filtering to be specified > while adding resources to data shares. GDS policy engine should be updated to > process data masking and row filtering while evaluating access requests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4988) Add syncSource and userRole queryParams to ranger searchUsers rest api for swagger
[
https://issues.apache.org/jira/browse/RANGER-4988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4988:
---
Fix Version/s: 2.6.0
> Add syncSource and userRole queryParams to ranger searchUsers rest api for
> swagger
> --
>
> Key: RANGER-4988
> URL: https://issues.apache.org/jira/browse/RANGER-4988
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Reporter: Guru Thejus
>Assignee: Guru Thejus
>Priority: Minor
> Fix For: 3.0.0, 2.6.0
>
>
> The ask is to add the following optional parameters to the
> /service/xusers/users method in the swagger API:
> {code:java|bgColor=#f4f5f7}
> syncSource
> userRole {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4963) Unescaped spaces with disjunctive matching in solr ranger_auth
[ https://issues.apache.org/jira/browse/RANGER-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4963: --- Fix Version/s: 2.6.0 > Unescaped spaces with disjunctive matching in solr ranger_auth > -- > > Key: RANGER-4963 > URL: https://issues.apache.org/jira/browse/RANGER-4963 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Guru Thejus >Assignee: Guru Thejus >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4982) Reduce Ranger plugin logging spew
[ https://issues.apache.org/jira/browse/RANGER-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4982: --- Fix Version/s: 2.6.0 > Reduce Ranger plugin logging spew > - > > Key: RANGER-4982 > URL: https://issues.apache.org/jira/browse/RANGER-4982 > Project: Ranger > Issue Type: Task > Components: Ranger >Reporter: Guru Thejus >Assignee: Guru Thejus >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4967) Refactor RangerTagEnricher class for reusability
[ https://issues.apache.org/jira/browse/RANGER-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4967: --- Fix Version/s: 2.6.0 > Refactor RangerTagEnricher class for reusability > > > Key: RANGER-4967 > URL: https://issues.apache.org/jira/browse/RANGER-4967 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Major > Fix For: 2.6.0 > > > RANGER-4922 improves performance of tag-lookup module. This patch modularizes > the approach so that it may be used for other look-up/search situations. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4981) Log LDAP auth failures at error level in ranger admin
[
https://issues.apache.org/jira/browse/RANGER-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4981:
---
Fix Version/s: 2.6.0
> Log LDAP auth failures at error level in ranger admin
> -
>
> Key: RANGER-4981
> URL: https://issues.apache.org/jira/browse/RANGER-4981
> Project: Ranger
> Issue Type: Task
> Components: Ranger
>Reporter: Guru Thejus
>Assignee: Guru Thejus
>Priority: Minor
> Fix For: 3.0.0, 2.6.0
>
>
> Currently o{color:#172b4d}nly way we can identify LDAP failures is by
> enabling debug level logging and so make ldap/ad auth failures to be logged
> at error level{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4983) Ranger Audit Filter for the HBase service is not working as expected
[
https://issues.apache.org/jira/browse/RANGER-4983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4983:
---
Fix Version/s: 2.6.0
> Ranger Audit Filter for the HBase service is not working as expected
>
>
> Key: RANGER-4983
> URL: https://issues.apache.org/jira/browse/RANGER-4983
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 3.0.0, 2.6.0
>Reporter: Rakesh Gupta
>Assignee: Dhaval Rajpara
>Priority: Major
> Fix For: 2.6.0
>
>
> Steps to repro
> # Login to hbase shell via hbase user and create below tables
> {code:java}
> create 'RitTable1', 'personal', 'medical','finance'
> put 'RitTable1', '1', 'personal:fname', 'Mike' {code}
> # create allow policy in Ranger for above resources to user systest
> (attached screenshot)
> # add audit filter in hbase service for above resource and user (attached
> screenshot)
> # login to hbase shell via systest user and run below command
> {code:java}
> scan 'RitTable1' {code}
> # Ranger audits are getting generated for the above command.
> Expected result : No audit is expected to be generated for the above command.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4966) Remove self node from the resourceTrie only if it has no children, no evaluators and no wildcard-evaluators
[ https://issues.apache.org/jira/browse/RANGER-4966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4966: --- Fix Version/s: 2.6.0 > Remove self node from the resourceTrie only if it has no children, no > evaluators and no wildcard-evaluators > --- > > Key: RANGER-4966 > URL: https://issues.apache.org/jira/browse/RANGER-4966 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Major > Fix For: 2.6.0 > > > If the policy-deltas are enabled, then when two policies have a common subset > of resources and are defined on same user (or subset of users, through groups > or direct users), if one of these policies is modified (on anything: name, > resource, user), it is the only one in effect during access evaluation. Until > a restart of the underlying service. > The underlying cause is a ResourceTrie node referring to modified > policy-evaluator is removed even when it contains wildcard-evaluator(s). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5135) CI: Add workflow to publish docker images to DockerHub on demand
Abhishek Kumar created RANGER-5135: -- Summary: CI: Add workflow to publish docker images to DockerHub on demand Key: RANGER-5135 URL: https://issues.apache.org/jira/browse/RANGER-5135 Project: Ranger Issue Type: Improvement Components: docker Reporter: Abhishek Kumar Assignee: Abhishek Kumar Add a GitHub Actions workflow that can be used on demand to publish ranger images to DockerHub, mainly to be used to publish images for released ranger versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5134) Fix processing of tasks scheduled to run after current transaction is complete
Abhishek Kumar created RANGER-5134: -- Summary: Fix processing of tasks scheduled to run after current transaction is complete Key: RANGER-5134 URL: https://issues.apache.org/jira/browse/RANGER-5134 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.5.0 Reporter: Abhishek Kumar Assignee: Abhishek Kumar Certain tasks like policy label updates, role version updates, tag version updates, etc. happen in a separate subsequent transaction after the current transaction to create/update policy/role/tag is complete. This happens in RangerTransactionSynchronizationAdapter. Fix the processing of tasks in runRunnables where unhandled TransactionExceptions could lead to an infinite do while loop. Here are test scenarios which capture this: # Update a policy in one session and delete the same policy in another session # Add a label for a policy in one session and remove an existing label for the same policy in another session. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4951) CI Build: GitHub Runner is running out of disk space
[
https://issues.apache.org/jira/browse/RANGER-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar resolved RANGER-4951.
Assignee: Abhishek Kumar
Resolution: Fixed
Commit link:
[https://github.com/apache/ranger/commit/c16dd8aaa8bf8cfe52ca3e13bc91980a27452b2d]
> CI Build: GitHub Runner is running out of disk space
> -
>
> Key: RANGER-4951
> URL: https://issues.apache.org/jira/browse/RANGER-4951
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Environment: Github Runner: ubuntu-latest
>Reporter: Abhishek Kumar
>Assignee: Abhishek Kumar
>Priority: Major
> Fix For: 2.6.0
>
> Attachments: Screenshot 2024-10-05 at 10.13.50 PM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While running docker-build on master, recent builds are encountering no space
> left on device error.
>
> {code:java}
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Common.Tracing.Error(Exception exception)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> Unhandled exception. System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at System.Diagnostics.TraceSource.Flush()
>at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
>at GitHub.Runner.Common.TraceManager.Dispose()
>at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
>at GitHub.Runner.Common.HostContext.Dispose()
>at GitHub.Runner.Worker.Program.Main(String[] args) {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-5127) Automate Apache Ranger Release Candidate Validation
Abhishek Kumar created RANGER-5127: -- Summary: Automate Apache Ranger Release Candidate Validation Key: RANGER-5127 URL: https://issues.apache.org/jira/browse/RANGER-5127 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar The process of generating a release candidate is an integral part of release management process. There are various tests run before a release candidate is published to ensure release candidate is a good fit for a certified release. Add a GitHub Actions workflow to help validate release candidates. Scope: * Build ranger with tests. * Test ranger installation with multiple databases in docker. * Test ranger upgrade with multiple databases and multiple previous releases in docker. * Test ranger-plugin installation in service containers. * Test ranger services are running in containers. * Test a few functionalities of ranger services with REST API calls (leveraging ranger PyPI client). * Validate no errors in logs for ranger-services. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5126) CI: Add coverage for testing ranger upgrades
[ https://issues.apache.org/jira/browse/RANGER-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5126: --- Description: Add a GitHub Actions workflow to test ranger upgrades from prior releases to the latest release. This will be useful in validating upgrades during release activities. Scope: * test upgrades with these ranger databases: postgres, mysql, oracle. * test with at-least 2 prior releases to the latest release being tested for upgrade. was:Add a GitHub Actions workflow to test ranger upgrades from prior releases to the latest release. This will be useful in validating upgrades during release activities. > CI: Add coverage for testing ranger upgrades > > > Key: RANGER-5126 > URL: https://issues.apache.org/jira/browse/RANGER-5126 > Project: Ranger > Issue Type: Improvement > Components: docker, Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > Add a GitHub Actions workflow to test ranger upgrades from prior releases to > the latest release. This will be useful in validating upgrades during release > activities. > > Scope: > * test upgrades with these ranger databases: postgres, mysql, oracle. > * test with at-least 2 prior releases to the latest release being tested for > upgrade. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5126) CI: Add coverage for testing ranger upgrades
Abhishek Kumar created RANGER-5126: -- Summary: CI: Add coverage for testing ranger upgrades Key: RANGER-5126 URL: https://issues.apache.org/jira/browse/RANGER-5126 Project: Ranger Issue Type: Improvement Components: docker, Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar Add a GitHub Actions workflow to test ranger upgrades from prior releases to the latest release. This will be useful in validating upgrades during release activities. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5099) Change pom version from 2.6.0-SNAPSHOT to 2.6.0
[ https://issues.apache.org/jira/browse/RANGER-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922886#comment-17922886 ] Abhishek Kumar commented on RANGER-5099: Update NOTICE.txt: [https://github.com/apache/ranger/commit/a1786ac] > Change pom version from 2.6.0-SNAPSHOT to 2.6.0 > --- > > Key: RANGER-5099 > URL: https://issues.apache.org/jira/browse/RANGER-5099 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.6.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > > Change pom version from 2.6.0-SNAPSHOT to 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-5099) Change pom version from 2.6.0-SNAPSHOT to 2.6.0
[ https://issues.apache.org/jira/browse/RANGER-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-5099. Resolution: Fixed Merged in [ranger-2.6|https://github.com/apache/ranger/commit/81f3d2f] > Change pom version from 2.6.0-SNAPSHOT to 2.6.0 > --- > > Key: RANGER-5099 > URL: https://issues.apache.org/jira/browse/RANGER-5099 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Affects Versions: 2.6.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > > Change pom version from 2.6.0-SNAPSHOT to 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4942) Fix Dockerfiles of ./build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4942. Resolution: Fixed Merged in [master|https://github.com/apache/ranger/commit/21b8ca9]: [PR #416|https://github.com/apache/ranger/pull/416] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/13fea84] > Fix Dockerfiles of ./build_ranger_using_docker.sh > - > > Key: RANGER-4942 > URL: https://issues.apache.org/jira/browse/RANGER-4942 > Project: Ranger > Issue Type: Bug > Components: build-infra >Reporter: Marco Luzzara >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The current Dockerfiles are syntactically wrong and blocks the Ranger build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (RANGER-4942) Fix Dockerfiles of ./build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar reassigned RANGER-4942: -- Assignee: Abhishek Kumar > Fix Dockerfiles of ./build_ranger_using_docker.sh > - > > Key: RANGER-4942 > URL: https://issues.apache.org/jira/browse/RANGER-4942 > Project: Ranger > Issue Type: Bug > Components: build-infra >Reporter: Marco Luzzara >Assignee: Abhishek Kumar >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > The current Dockerfiles are syntactically wrong and blocks the Ranger build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4942) Fix Dockerfiles of ./build_ranger_using_docker.sh
[ https://issues.apache.org/jira/browse/RANGER-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4942: --- Fix Version/s: 2.6.0 > Fix Dockerfiles of ./build_ranger_using_docker.sh > - > > Key: RANGER-4942 > URL: https://issues.apache.org/jira/browse/RANGER-4942 > Project: Ranger > Issue Type: Bug > Components: build-infra >Reporter: Marco Luzzara >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > The current Dockerfiles are syntactically wrong and blocks the Ranger build -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5106) Remove redundant mvn calls in README
[ https://issues.apache.org/jira/browse/RANGER-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5106: --- Issue Type: Bug (was: Task) > Remove redundant mvn calls in README > > > Key: RANGER-5106 > URL: https://issues.apache.org/jira/browse/RANGER-5106 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Update README in root dir. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5107) Update README.md in plugin-nestedstructure
[ https://issues.apache.org/jira/browse/RANGER-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5107: --- Issue Type: Bug (was: Task) > Update README.md in plugin-nestedstructure > -- > > Key: RANGER-5107 > URL: https://issues.apache.org/jira/browse/RANGER-5107 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Barbara Eckman >Priority: Major > Fix For: 2.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5006) User name column in Ranger audit not rendering properly when it is of larger length
[ https://issues.apache.org/jira/browse/RANGER-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5006: --- Issue Type: Bug (was: Improvement) > User name column in Ranger audit not rendering properly when it is of larger > length > --- > > Key: RANGER-5006 > URL: https://issues.apache.org/jira/browse/RANGER-5006 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: 0001-RANGER-5006.patch > > > User name column in Ranger audit not rendering properly when it is of larger > length. This scenario occurs in DataSharing where client_id is a lengthly > string and causing the audit field to overlap. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5021) Add timeouts to job stages in CI
[ https://issues.apache.org/jira/browse/RANGER-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5021: --- Issue Type: Improvement (was: Bug) > Add timeouts to job stages in CI > > > Key: RANGER-5021 > URL: https://issues.apache.org/jira/browse/RANGER-5021 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Introduce timeouts to stages in the CI pipeline supported in GitHub Actions > to: > * avoid infinite/long running processes. > * improved resource utilization for GitHub runners. > * detect problems early -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5068) Bump rat plugin to 0.16.1
[ https://issues.apache.org/jira/browse/RANGER-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5068: --- Issue Type: Improvement (was: Bug) > Bump rat plugin to 0.16.1 > - > > Key: RANGER-5068 > URL: https://issues.apache.org/jira/browse/RANGER-5068 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This version of rat plugin is thread safe. > for more details: > [https://creadur.apache.org/rat/apache-rat-plugin/rat-mojo.html] > It will help in CI as well since multi-threaded builds are running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4951) CI Build: GitHub Runner is running out of disk space
[
https://issues.apache.org/jira/browse/RANGER-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4951:
---
Fix Version/s: 2.6.0
> CI Build: GitHub Runner is running out of disk space
> -
>
> Key: RANGER-4951
> URL: https://issues.apache.org/jira/browse/RANGER-4951
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Environment: Github Runner: ubuntu-latest
>Reporter: Abhishek Kumar
>Priority: Major
> Fix For: 2.6.0
>
> Attachments: Screenshot 2024-10-05 at 10.13.50 PM.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While running docker-build on master, recent builds are encountering no space
> left on device error.
>
> {code:java}
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source,
> TraceEventType eventType, Int32 id)
>at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache
> eventCache, String source, TraceEventType eventType, Int32 id, String message)
>at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType,
> Int32 id, String message)
>at GitHub.Runner.Common.Tracing.Error(Exception exception)
>at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[]
> args)
> Unhandled exception. System.IO.IOException: No space left on device :
> '/home/runner/runners/2.319.1/_diag/Worker_20241006-025515-utc.log'
>at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle,
> ReadOnlySpan`1 buffer, Int64 fileOffset)
>at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
>at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
>at System.Diagnostics.TextWriterTraceListener.Flush()
>at System.Diagnostics.TraceSource.Flush()
>at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
>at GitHub.Runner.Common.TraceManager.Dispose()
>at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
>at GitHub.Runner.Common.HostContext.Dispose()
>at GitHub.Runner.Worker.Program.Main(String[] args) {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4307) Allow the synchronization time interval of LDAP users to exceed the one hour limit, and users can customize the time interval
[ https://issues.apache.org/jira/browse/RANGER-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4307: --- Issue Type: Improvement (was: New Feature) > Allow the synchronization time interval of LDAP users to exceed the one > hour limit, and users can customize the time interval > --- > > Key: RANGER-4307 > URL: https://issues.apache.org/jira/browse/RANGER-4307 > Project: Ranger > Issue Type: Improvement > Components: usersync >Affects Versions: 2.4.0 > Environment: Linux Ranger2.4 >Reporter: Tongtong Zhu >Priority: Blocker > Fix For: 3.0.0, 2.6.0 > > Attachments: RANGER-4307.patch > > Original Estimate: 48h > Time Spent: 3h > Remaining Estimate: 45h > > Allow the synchronization time interval of LDAP users to exceed the one hour > limit, and users can customize the time interval because this requirement is > very urgent in actual production environments. The vast majority of users are > unwilling to wait at least one hour to verify the user's permissions after > creating an LDAP user. In order to improve development efficiency, it is > recommended to add a new configuration option. By enabling this configuration > option, you can customize the time interval. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4925) Cache downloaded archives during CI docker build
[ https://issues.apache.org/jira/browse/RANGER-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4925: --- Issue Type: Improvement (was: Bug) > Cache downloaded archives during CI docker build > > > Key: RANGER-4925 > URL: https://issues.apache.org/jira/browse/RANGER-4925 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.5.0 > > > Cache downloaded archives (as part of docker build) in CI runs to optimize > docker build times. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877898#comment-17877898 ] Abhishek Kumar edited comment on RANGER-4919 at 1/31/25 11:26 PM: -- Commit: [https://github.com/apache/ranger/commit/8bb2053] ranger-2.6 commit: [https://github.com/apache/ranger/commit/9a8e46d72d00cb53e8ca1c043ae9e6458f951b59] was (Author: abhi_2110): Commit: [https://github.com/apache/ranger/commit/8bb2053] > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4919) maven build fails after knox-gateway-version bump to 2.0.0
[ https://issues.apache.org/jira/browse/RANGER-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4919: --- Fix Version/s: 2.6.0 > maven build fails after knox-gateway-version bump to 2.0.0 > --- > > Key: RANGER-4919 > URL: https://issues.apache.org/jira/browse/RANGER-4919 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Attachments: build.log > > Time Spent: 10m > Remaining Estimate: 0h > > knox-gateway-version bump from 1.4.0 to 2.0.0 causes these librares to be > included in the build: > org.jetbrains.pty4j:pty4j:jar:0.11.4, > org.jetbrains.pty4j:purejavacomm:jar:0.0.11.1 > These libraries are not found in apache snapshot mirror, the exact versions > are also not present in: > - [https://repo.maven.apache.org/] > - [https://repo1.maven.org/] > Although an upgraded version is available above. > [https://mvnrepository.com/artifact/org.jetbrains.pty4j/pty4j/0.11.4] > suggests a repo which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4892) Upgrade Ranger Tomcat from 8.5.x to 9.x
[ https://issues.apache.org/jira/browse/RANGER-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922534#comment-17922534 ] Abhishek Kumar commented on RANGER-4892: Follow-up commit[ranger-2.6]: https://github.com/apache/ranger/commit/91c5402e8fcec77db3faec3ae09b34b433738a54 > Upgrade Ranger Tomcat from 8.5.x to 9.x > --- > > Key: RANGER-4892 > URL: https://issues.apache.org/jira/browse/RANGER-4892 > Project: Ranger > Issue Type: Improvement > Components: kms, Ranger >Affects Versions: 3.0.0, 2.6.0 >Reporter: Bhavik Patel >Assignee: Sanket Shelar >Priority: Major > Fix For: 2.6.0 > > Attachments: 0001-RANGER-4892.patch, 0002-RANGER-4892.patch, > 0003-RANGER-4892.patch, 0004-RANGER-4892.patch > > Time Spent: 20m > Remaining Estimate: 0h > > Upgrade Ranger Tomcat from 8.5.x to 9.x as latest version of tomcat 8.5.100 > is impacted with critical vulnerability -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4939) Upgrade Elasticsearch version to 7.17.24
[ https://issues.apache.org/jira/browse/RANGER-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4939: --- Fix Version/s: (was: 2.5.0) (was: 2.6.0) > Upgrade Elasticsearch version to 7.17.24 > > > Key: RANGER-4939 > URL: https://issues.apache.org/jira/browse/RANGER-4939 > Project: Ranger > Issue Type: Improvement > Components: audit >Affects Versions: 2.5.0 >Reporter: FerArribas >Assignee: FerArribas >Priority: Major > Labels: security > Fix For: 3.0.0 > > Attachments: > 0001-RANGER-4939-Upgrade-Elasticsearch-version-to-7.17.24.patch > > Original Estimate: 336h > Time Spent: 40m > Remaining Estimate: 335h 20m > > Elasticsearch version 7.10.2 is affected by a high vulnerability > CVE-2023-31418. You must upgrade to version 7.17.22 to fix this > vulnerability. > For the moment, it is not easy to upgrade to a more current version than > 7.17.22 since the Elastic API is not backwards compatible and changes the > implementation a lot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4939) Upgrade Elasticsearch version to 7.17.24
[ https://issues.apache.org/jira/browse/RANGER-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921998#comment-17921998 ] Abhishek Kumar commented on RANGER-4939: Moving it out of the 2.6 release, updating the fix version. > Upgrade Elasticsearch version to 7.17.24 > > > Key: RANGER-4939 > URL: https://issues.apache.org/jira/browse/RANGER-4939 > Project: Ranger > Issue Type: Improvement > Components: audit >Affects Versions: 2.5.0 >Reporter: FerArribas >Assignee: FerArribas >Priority: Major > Labels: security > Fix For: 3.0.0, 2.5.0, 2.6.0 > > Attachments: > 0001-RANGER-4939-Upgrade-Elasticsearch-version-to-7.17.24.patch > > Original Estimate: 336h > Time Spent: 40m > Remaining Estimate: 335h 20m > > Elasticsearch version 7.10.2 is affected by a high vulnerability > CVE-2023-31418. You must upgrade to version 7.17.22 to fix this > vulnerability. > For the moment, it is not easy to upgrade to a more current version than > 7.17.22 since the Elastic API is not backwards compatible and changes the > implementation a lot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-4743) [JDK 11]: Fix ranger admin logging
[ https://issues.apache.org/jira/browse/RANGER-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4743. Fix Version/s: (was: 3.0.0) (was: 2.6.0) Resolution: Not A Problem The logback and slf4j versions were bumped in [RANGER-4855|https://issues.apache.org/jira/browse/RANGER-4855], this is no longer an issue. > [JDK 11]: Fix ranger admin logging > --- > > Key: RANGER-4743 > URL: https://issues.apache.org/jira/browse/RANGER-4743 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Blocker > Attachments: 0001-RANGER-4743.patch > > > Currently, the ranger-admin logs do not appear when built and run with jdk 11. > Logback and slf4j versions need to be upgraded to fix the above issue. > More info: [https://logback.qos.ch/download.html] > CC: [~rmani] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4888) The ranger setup.sh/db setup fails on Mysql ranger creation
[
https://issues.apache.org/jira/browse/RANGER-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4888:
---
Fix Version/s: 3.0.0
(was: 2.6.0)
> The ranger setup.sh/db setup fails on Mysql ranger creation
> ---
>
> Key: RANGER-4888
> URL: https://issues.apache.org/jira/browse/RANGER-4888
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
> Environment: Ubuntu 20.04
>Reporter: Steven Weiss
>Priority: Major
> Fix For: 3.0.0
>
>
> {quote}Running setup.sh
>
> Error:
>
> CREATE TABLE `x_trx_log_v2` ( `id` bigint(20) NOT NULL AUTO_INCREMENT,
> `create_time` datetime DEFAULT NULL, `added_by_id` bigint(20) DEFAULT NULL,
> `class_type` int(11) NOT NULL DEFAULT '0', `object_id` bigint(20) DEFAULT
> NULL, `parent_object_id` bigint(20) DEFAULT NULL,
> `parent_object_class_type` int(11) NOT NULL DEFAULT '0',
> `parent_object_name` varchar(1024) DEFAULT NULL, `object_name`
> varchar(1024) DEFAULT NULL, `change_info` MEDIUMTEXT NULL DEFAULT NULL,
> `trx_id` varchar(1024) DEFAULT NULL, `action` varchar(255) DEFAULT NULL,
> `sess_id` varchar(512) DEFAULT NULL, `req_id` varchar(30) DEFAULT NULL,
> `sess_type` varchar(30) DEFAULT NULL, PRIMARY KEY (`id`), KEY
> `x_trx_log_v2_FK_added_by_id` (`added_by_id`), KEY `x_trx_log_v2_cr_time`
> (`create_time`), KEY `x_trx_log_v2_trx_id` (`trx_id`) )ROW_FORMAT=DYNAMIC;
> java.sql.SQLSyntaxErrorException: Specified key was too long; max key length
> is 3072 bytes
> SQLException : SQL state: 42000 java.sql.SQLSyntaxErrorException: Specified
> key was too long; max key length is 3072 bytes ErrorCode: 1071
>
> Problem seems to be the trx_id is too long{quote}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4888) The ranger setup.sh/db setup fails on Mysql ranger creation
[
https://issues.apache.org/jira/browse/RANGER-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921586#comment-17921586
]
Abhishek Kumar commented on RANGER-4888:
Moving it out of the 2.6 release, updating the fix version.
> The ranger setup.sh/db setup fails on Mysql ranger creation
> ---
>
> Key: RANGER-4888
> URL: https://issues.apache.org/jira/browse/RANGER-4888
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
> Environment: Ubuntu 20.04
>Reporter: Steven Weiss
>Priority: Major
> Fix For: 2.6.0
>
>
> {quote}Running setup.sh
>
> Error:
>
> CREATE TABLE `x_trx_log_v2` ( `id` bigint(20) NOT NULL AUTO_INCREMENT,
> `create_time` datetime DEFAULT NULL, `added_by_id` bigint(20) DEFAULT NULL,
> `class_type` int(11) NOT NULL DEFAULT '0', `object_id` bigint(20) DEFAULT
> NULL, `parent_object_id` bigint(20) DEFAULT NULL,
> `parent_object_class_type` int(11) NOT NULL DEFAULT '0',
> `parent_object_name` varchar(1024) DEFAULT NULL, `object_name`
> varchar(1024) DEFAULT NULL, `change_info` MEDIUMTEXT NULL DEFAULT NULL,
> `trx_id` varchar(1024) DEFAULT NULL, `action` varchar(255) DEFAULT NULL,
> `sess_id` varchar(512) DEFAULT NULL, `req_id` varchar(30) DEFAULT NULL,
> `sess_type` varchar(30) DEFAULT NULL, PRIMARY KEY (`id`), KEY
> `x_trx_log_v2_FK_added_by_id` (`added_by_id`), KEY `x_trx_log_v2_cr_time`
> (`create_time`), KEY `x_trx_log_v2_trx_id` (`trx_id`) )ROW_FORMAT=DYNAMIC;
> java.sql.SQLSyntaxErrorException: Specified key was too long; max key length
> is 3072 bytes
> SQLException : SQL state: 42000 java.sql.SQLSyntaxErrorException: Specified
> key was too long; max key length is 3072 bytes ErrorCode: 1071
>
> Problem seems to be the trx_id is too long{quote}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4813) update audit UI to retrieve V2 trx log record
[
https://issues.apache.org/jira/browse/RANGER-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4813:
---
Fix Version/s: (was: 2.6.0)
Moving it out of the 2.6 release, updating the fix version.
> update audit UI to retrieve V2 trx log record
> -
>
> Key: RANGER-4813
> URL: https://issues.apache.org/jira/browse/RANGER-4813
> Project: Ranger
> Issue Type: Improvement
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Abhishek
>Priority: Major
> Fix For: 3.0.0
>
>
> Currently admin audit UI retrieves multiple V1 trx logs to gather details of
> an update (REST API: service/assets//report/\{transactionId}). This should be
> optimized to retrieve a single V2 trx log record (introduced in RANGER-4803)
> to render in UI. A new API should be added to retrieve V2 trx log record.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-5119) Update branch ranger-2.6 to produce 2.6.1-SNAPSHOT
Abhishek Kumar created RANGER-5119: -- Summary: Update branch ranger-2.6 to produce 2.6.1-SNAPSHOT Key: RANGER-5119 URL: https://issues.apache.org/jira/browse/RANGER-5119 Project: Ranger Issue Type: Sub-task Components: build-infra Reporter: Abhishek Kumar Assignee: Abhishek Kumar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5120) Publish ranger docker images for ranger-2.6 release
[ https://issues.apache.org/jira/browse/RANGER-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5120: --- Description: Ranger is available in DockerHub: https://hub.docker.com/r/apache/ranger release 2.6 should also have ranger image (and its dependencies) published to DockerHub. Links to relevant DockerHub registries: 1. apache/ranger: https://hub.docker.com/r/apache/ranger 2. apache/ranger-db: https://hub.docker.com/r/apache/ranger-db 3. apache/ranger-solr: https://hub.docker.com/r/apache/ranger-solr 4. apache/ranger-zk: https://hub.docker.com/r/apache/ranger-zk > Publish ranger docker images for ranger-2.6 release > --- > > Key: RANGER-5120 > URL: https://issues.apache.org/jira/browse/RANGER-5120 > Project: Ranger > Issue Type: Sub-task > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > > Ranger is available in DockerHub: > https://hub.docker.com/r/apache/ranger > release 2.6 should also have ranger image (and its dependencies) published to > DockerHub. > Links to relevant DockerHub registries: > 1. apache/ranger: https://hub.docker.com/r/apache/ranger > 2. apache/ranger-db: https://hub.docker.com/r/apache/ranger-db > 3. apache/ranger-solr: https://hub.docker.com/r/apache/ranger-solr > 4. apache/ranger-zk: https://hub.docker.com/r/apache/ranger-zk -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5120) Publish ranger docker images for ranger-2.6 release
Abhishek Kumar created RANGER-5120: -- Summary: Publish ranger docker images for ranger-2.6 release Key: RANGER-5120 URL: https://issues.apache.org/jira/browse/RANGER-5120 Project: Ranger Issue Type: Sub-task Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-5104. Resolution: Fixed > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Blocker > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0-with-pr-511.log, > ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921260#comment-17921260 ] Abhishek Kumar commented on RANGER-5104: Merged in [master|https://github.com/apache/ranger/commit/86b1bcd] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/36fcf76] > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Blocker > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0-with-pr-511.log, > ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5006) User name column in Ranger audit not rendering properly when it is of larger length
[ https://issues.apache.org/jira/browse/RANGER-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921259#comment-17921259 ] Abhishek Kumar commented on RANGER-5006: Merged in [master|https://github.com/apache/ranger/commit/92f3466] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/0b3d90c] > User name column in Ranger audit not rendering properly when it is of larger > length > --- > > Key: RANGER-5006 > URL: https://issues.apache.org/jira/browse/RANGER-5006 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Dhaval Rajpara >Assignee: Dhaval Rajpara >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: 0001-RANGER-5006.patch > > > User name column in Ranger audit not rendering properly when it is of larger > length. This scenario occurs in DataSharing where client_id is a lengthly > string and causing the audit field to overlap. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4992) Ranger REST API for audit access logs to return additional event time field in specific timezone format
[ https://issues.apache.org/jira/browse/RANGER-4992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921258#comment-17921258 ] Abhishek Kumar commented on RANGER-4992: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/0a4c98b] > Ranger REST API for audit access logs to return additional event time field > in specific timezone format > --- > > Key: RANGER-4992 > URL: https://issues.apache.org/jira/browse/RANGER-4992 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Guru Thejus >Assignee: Guru Thejus >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > > Ranger REST API for audit access logs will always return eventTime field in > UTC. As this field is needed as UTC to sync across different ranger systems, > the ask here is to add additional field zonedEventTime which return the event > time in specific time zone as per the query param input to the rest api. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4996) Make meta attributes fields in policy rest api response configurable
[ https://issues.apache.org/jira/browse/RANGER-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921257#comment-17921257 ] Abhishek Kumar commented on RANGER-4996: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/4e14deb] > Make meta attributes fields in policy rest api response configurable > > > Key: RANGER-4996 > URL: https://issues.apache.org/jira/browse/RANGER-4996 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Guru Thejus >Assignee: Guru Thejus >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > > Make createTime, updateTime, createdBy, updatedBy fields in the policy rest > api response configurable for retrieval. Currently these are pruned before > response is sent. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-4912) Upgrade Spring framework to 5.3.39
[ https://issues.apache.org/jira/browse/RANGER-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921256#comment-17921256 ] Abhishek Kumar edited comment on RANGER-4912 at 1/27/25 1:53 AM: - Merged in [ranger-2.6|https://github.com/apache/ranger/commit/6a4082a] was (Author: abhi_2110): Merged in [ranger-2.6|https://github.com/apache/ranger/commit/2081a89] > Upgrade Spring framework to 5.3.39 > -- > > Key: RANGER-4912 > URL: https://issues.apache.org/jira/browse/RANGER-4912 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: 0001-RANGER-4912-Upgrade-Spring-framework-to-5.3.39.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4912) Upgrade Spring framework to 5.3.39
[ https://issues.apache.org/jira/browse/RANGER-4912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921256#comment-17921256 ] Abhishek Kumar commented on RANGER-4912: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/2081a89] > Upgrade Spring framework to 5.3.39 > -- > > Key: RANGER-4912 > URL: https://issues.apache.org/jira/browse/RANGER-4912 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: 0001-RANGER-4912-Upgrade-Spring-framework-to-5.3.39.patch > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5001) Ignore denials for descendent resources
[ https://issues.apache.org/jira/browse/RANGER-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921253#comment-17921253 ] Abhishek Kumar commented on RANGER-5001: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/174b0ca] > Ignore denials for descendent resources > --- > > Key: RANGER-5001 > URL: https://issues.apache.org/jira/browse/RANGER-5001 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhay Kulkarni >Assignee: Fateh Singh >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Ranger policy engine currently supports finding if an user has a given > permission on a resource or any of its descendants. This functionality should > be extended to ignore denials for descendent resources, to enable finding if > an user has permissions for at least one of the descendent resource. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4914) Ranger TagSync does not support ofs path parsing for Ozone-Atlas currently
[
https://issues.apache.org/jira/browse/RANGER-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921252#comment-17921252
]
Abhishek Kumar commented on RANGER-4914:
Merged in [master|https://github.com/apache/ranger/commit/6b77713]
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/f78568b]
> Ranger TagSync does not support ofs path parsing for Ozone-Atlas currently
> --
>
> Key: RANGER-4914
> URL: https://issues.apache.org/jira/browse/RANGER-4914
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Fateh Singh
>Assignee: Fateh Singh
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When trying to create hive table on top of ozone ofs path, tagsync throws
> below error
> {code:java}
> 2024-08-06 13:33:00,805 ERROR
> org.apache.ranger.tagsync.source.atlas.AtlasResourceMapperUtil: Could not get
> serviceResource for atlas entity:91faefd3-0592-400e-b452-0c9a437555db:
> java.lang.Exception: volume-name not found in attribute 'qualifiedName':
> ofs://ozone1722927741/vol1/bucket1/employee_db/meh1_hive_ozone_table_171@cm
> at
> org.apache.ranger.tagsync.source.atlas.AtlasResourceMapper.throwExceptionWithMessage(AtlasResourceMapper.java:120)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasOzoneResourceMapper.buildResource(AtlasOzoneResourceMapper.java:113)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasResourceMapperUtil.getRangerServiceResource(AtlasResourceMapperUtil.java:64)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasNotificationMapper.buildServiceTags(AtlasNotificationMapper.java:259)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasNotificationMapper.buildServiceTags(AtlasNotificationMapper.java:198)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasNotificationMapper.processAtlasEntities(AtlasNotificationMapper.java:105)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasTagSource$ConsumerRunnable.buildAndUploadServiceTags(AtlasTagSource.java:255)
> at
> org.apache.ranger.tagsync.source.atlas.AtlasTagSource$ConsumerRunnable.run(AtlasTagSource.java:230)
> at java.lang.Thread.run(Thread.java:748){code}
> Sample command which causes issues:
> {code:java}
> $ CREATE EXTERNAL TABLE t1 (id int, name string) row format delimited fields
> terminated by ' ' stored as textfile location
> 'ofs://ozone1/volume1/bucket1/table_oz_demo1';{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4936) Feature to import and export individual policies
[ https://issues.apache.org/jira/browse/RANGER-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921247#comment-17921247 ] Abhishek Kumar commented on RANGER-4936: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/d58577f] > Feature to import and export individual policies > > > Key: RANGER-4936 > URL: https://issues.apache.org/jira/browse/RANGER-4936 > Project: Ranger > Issue Type: New Feature > Components: admin >Reporter: Guru Thejus >Assignee: Guru Thejus >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > Attachments: > 0001-Feature-for-download-and-upload-of-individual-polici.patch > > > Implement feature to import and export individual policies in ranger admin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-3641) Add API to enhance KMS capabilities
[
https://issues.apache.org/jira/browse/RANGER-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921246#comment-17921246
]
Abhishek Kumar commented on RANGER-3641:
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/b84ef66]
> Add API to enhance KMS capabilities
> ---
>
> Key: RANGER-3641
> URL: https://issues.apache.org/jira/browse/RANGER-3641
> Project: Ranger
> Issue Type: Improvement
> Components: kms
>Affects Versions: 3.0.0, 2.3.0
>Reporter: kirby zhou
>Assignee: Vikas Kumar
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
>
> Some APIs are very useful.
>
> * GenerateEEK with decrypted EEK returned together
> Like:
> {EEK, EK} = GenerateEEK2(KeyVersion)
> This helps Program which request a EEK to encrypt something itself such like
> KUDU or MySQL.
> It now takes 2 RPC calls to complete encryption. If a API can return EEK and
> EK together, we can save 1 RPC call.
>
> * Simple Encryption and Decryption API
> Like:
> {EncryptedData} = Encrypt(KeyVersion, PlainData)
> {PlainData} = Decrypt(KeyVersion, EncryptedData)
> This helps Ranger KMS works for some simple situation such as encrypting
> password.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3801) Add support for Ozone in docker
[ https://issues.apache.org/jira/browse/RANGER-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921245#comment-17921245 ] Abhishek Kumar commented on RANGER-3801: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/8f14fc6] Additional commit merged in [ranger-2.6|https://github.com/apache/ranger/commit/5c413eb] > Add support for Ozone in docker > --- > > Key: RANGER-3801 > URL: https://issues.apache.org/jira/browse/RANGER-3801 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Siyao Meng >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Hi folks, > I see Ranger has dev support for hadoop, hbase, hive, solr and others. Shall > we add ozone as well? As Ozone does support using > [RangerOzoneAuthorizer|https://github.com/apache/ranger/blob/master/plugin-ozone/src/main/java/org/apache/ranger/authorization/ozone/authorizer/RangerOzoneAuthorizer.java] > as the ACL checker? > https://github.com/apache/ranger/tree/master/dev-support/ranger-docker > Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4607) Ranger REST API improvements
[ https://issues.apache.org/jira/browse/RANGER-4607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921244#comment-17921244 ] Abhishek Kumar commented on RANGER-4607: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/fc77219] > Ranger REST API improvements > > > Key: RANGER-4607 > URL: https://issues.apache.org/jira/browse/RANGER-4607 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0, 2.4.1 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: 0001-RANGER-4607-Ranger-REST-API-improvements.patch > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4622) Fix the default value of ranger.accesslog.rotate.rename_on_rotate configuration in ranger--admin-default-site.xml
[ https://issues.apache.org/jira/browse/RANGER-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921243#comment-17921243 ] Abhishek Kumar commented on RANGER-4622: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/d6f09eb] > Fix the default value of ranger.accesslog.rotate.rename_on_rotate > configuration in ranger--admin-default-site.xml > - > > Key: RANGER-4622 > URL: https://issues.apache.org/jira/browse/RANGER-4622 > Project: Ranger > Issue Type: Improvement > Components: admin >Affects Versions: 2.3.0 >Reporter: zhaoshuaihua >Priority: Minor > Fix For: 3.0.0, 2.6.0 > > Attachments: > RANGER-4622_property_ranger_accesslog_rotate_rename_on_rotate,_the_default_value_is_false,.patch, > screenshot-1.png > > Original Estimate: 0.5h > Time Spent: 0.5h > Remaining Estimate: 0h > > Fix the default value of ranger.accesslog.rotate.rename_on_rotate > configuration in ranger--admin-default-site.xml. The default value of this > configuration is false instead of 15. > > !https://private-user-images.githubusercontent.com/50791733/291463576-4dbadd0b-0c89-411f-84bf-9f173dcdfd4c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDMxNDczMzIsIm5iZiI6MTcwMzE0NzAzMiwicGF0aCI6Ii81MDc5MTczMy8yOTE0NjM1NzYtNGRiYWRkMGItMGM4OS00MTFmLTg0YmYtOWYxNzNkY2RmZDRjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjIxVDA4MjM1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThiYTkwZGJhYmM5NWM5YWVlYzhkMTgyYmIyMjhhYzkwMzg3MTUwZmU3YzQ5MTcxMzY1OGQyZWRiMzhiNDEyYzImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.KjaxtRsqR1N9JuBgx4n3_45_tzIa9liHl787PCtqUFo! > !https://private-user-images.githubusercontent.com/50791733/291463606-a72f6e18-fcee-4f8d-8155-fa7cb9eb76e4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTEiLCJleHAiOjE3MDMxNDczMzIsIm5iZiI6MTcwMzE0NzAzMiwicGF0aCI6Ii81MDc5MTczMy8yOTE0NjM2MDYtYTcyZjZlMTgtZmNlZS00ZjhkLTgxNTUtZmE3Y2I5ZWI3NmU0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFJV05KWUFYNENTVkVINTNBJTJGMjAyMzEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjMxMjIxVDA4MjM1MlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc3YTg5YjhjZmIxNzUwYjkyYzE1MzBhZjNmOGEwZjI4NGZmODEzMDg5NDQ2M2VkNTU5YmVkNGEyNWEwNDc1M2QmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.k5_0FMEOriQX_Q0_hd7vx5LmOR6p3PV8ozwKQ1p9hv0! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4670) Hbase plugin configurable authorization level (table, column family, column)
[ https://issues.apache.org/jira/browse/RANGER-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921242#comment-17921242 ] Abhishek Kumar commented on RANGER-4670: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/4d20197] > Hbase plugin configurable authorization level (table, column family, column) > > > Key: RANGER-4670 > URL: https://issues.apache.org/jira/browse/RANGER-4670 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Fateh Singh >Assignee: Fateh Singh >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 3.5h > Remaining Estimate: 0h > > Currently hbase plugin authoirization at table, column family and column > level which causes slowness when large number of columns exist. Having a > configuration to short circuit this authorization at different levels based > on customer need can provide performance gains. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4709) Set role command is not audited by ranger
[ https://issues.apache.org/jira/browse/RANGER-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921241#comment-17921241 ] Abhishek Kumar commented on RANGER-4709: Merged in [master|https://github.com/apache/ranger/commit/d338761] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/c9bbe63] > Set role command is not audited by ranger > - > > Key: RANGER-4709 > URL: https://issues.apache.org/jira/browse/RANGER-4709 > Project: Ranger > Issue Type: Bug > Components: audit >Reporter: suja s >Assignee: Guru Thejus >Priority: Major > Fix For: 3.0.0, 2.6.0 > > > STEPS TO REPRODUCE: > Create roles r1, r2 via hive beeline. > Assign role r1 to user u1 > Connect to beeline as user u1 > Execute command 'set role none'. > Operation is succesful. > Execute command 'set role r2'. > Operation fails as u1 is not part of r2. > Execute command 'set role r1'. > Operation is succesful. > Inspect access audit logs -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4905) Reduce memory needed to create Ranger policy engine
[ https://issues.apache.org/jira/browse/RANGER-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921240#comment-17921240 ] Abhishek Kumar commented on RANGER-4905: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/a740901] > Reduce memory needed to create Ranger policy engine > --- > > Key: RANGER-4905 > URL: https://issues.apache.org/jira/browse/RANGER-4905 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni >Priority: Major > Fix For: 3.0.0, 2.6.0 > > > Ranger policy engine creates a RangerPolicyResourceMatcher object for every > resource specified either in policy or in a tag association. > PolicyResourceMatcher, for the services that have more than one level in > their resource hierarchy, consists of RangerResourceMatcher objects for each > level in the resource-level hierarchy for the resource. In many cases, this > leads to creation of multiple RangerResourceMatchers with identical resource > specification. > This Jira avoids creation of multiple RangerResourceMatcher objects by > maintaining a cache of them in the RangerPluginContext object associated with > the Ranger policy engine, thereby reducing policy engine's memory needs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4915) The default SSL Ciphers are too weak for user sync service
[ https://issues.apache.org/jira/browse/RANGER-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921239#comment-17921239 ] Abhishek Kumar commented on RANGER-4915: Merged in [master|https://github.com/apache/ranger/commit/e671f86] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/995c230] > The default SSL Ciphers are too weak for user sync service > -- > > Key: RANGER-4915 > URL: https://issues.apache.org/jira/browse/RANGER-4915 > Project: Ranger > Issue Type: Bug > Components: usersync >Affects Versions: 2.1.0, 2.2.0, 2.3.0, 2.4.0, 2.5.0 > Environment: Ranger 2.1.0 >Reporter: zhenye zhang >Priority: Minor > Labels: pull-request-available > Fix For: 3.0.0, 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > When we enable the ssl(ranger.usersync.ssl=true), the security tools report > the default SSL Ciphers are too weak. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4921) Fix docker compose command in CI
[ https://issues.apache.org/jira/browse/RANGER-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921238#comment-17921238 ] Abhishek Kumar commented on RANGER-4921: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/aa8fd72] > Fix docker compose command in CI > > > Key: RANGER-4921 > URL: https://issues.apache.org/jira/browse/RANGER-4921 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > > docker-compose command changed to docker compose -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4922) Reduce time to find tags associated with multi-level resource
[
https://issues.apache.org/jira/browse/RANGER-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921235#comment-17921235
]
Abhishek Kumar commented on RANGER-4922:
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/0447404]
> Reduce time to find tags associated with multi-level resource
> -
>
> Key: RANGER-4922
> URL: https://issues.apache.org/jira/browse/RANGER-4922
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
>
> With the following use case:
> * Service supports resource hierarchy with more than one level
> * Large number of tags are associated with the resources, with majority of
> tagged resources with values for all levels in resource hierarchy
> * Accessed resource does not have values for all levels in the resource
> hierarchy
> the time required to find the tags associated with the accessed resource is
> significant.
> When tested with a large number of tagged Ozone resources (~ 629,000) with
> approximately 20 tagged volumes and 103 tagged buckets and the rest being
> keys, the access evaluation times are:
> {code:java}
> (volume, bucket, key) : requestCount=629118, avgTimeTaken=49911ns
> (volume, bucket) : requestCount=103, avgTimeTaken=10738069ns
> (volume) :
> - requestCount=20, avgTimeTaken=21968890ns
> - requestCount=1056, avgTimeTaken=13763978ns (repeated requests in previous
> run multiple times) {code}
> This patch, using filtering and caching technique attempts to reduce this
> time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4991) GDS policy evaluation to support data masking and row filtering
[ https://issues.apache.org/jira/browse/RANGER-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-4991: --- Fix Version/s: (was: 2.6.0) > GDS policy evaluation to support data masking and row filtering > --- > > Key: RANGER-4991 > URL: https://issues.apache.org/jira/browse/RANGER-4991 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Reporter: Madhan Neethiraj >Assignee: Madhan Neethiraj >Priority: Major > Fix For: 3.0.0 > > Attachments: RANGER-4991.patch > > > GDS model support specifying data masking and row filtering to be specified > while adding resources to data shares. GDS policy engine should be updated to > process data masking and row filtering while evaluating access requests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5021) Add timeouts to job stages in CI
[ https://issues.apache.org/jira/browse/RANGER-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921232#comment-17921232 ] Abhishek Kumar commented on RANGER-5021: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/957093e] > Add timeouts to job stages in CI > > > Key: RANGER-5021 > URL: https://issues.apache.org/jira/browse/RANGER-5021 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > Introduce timeouts to stages in the CI pipeline supported in GitHub Actions > to: > * avoid infinite/long running processes. > * improved resource utilization for GitHub runners. > * detect problems early -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5008) Handle creation of federated user in Ranger
[ https://issues.apache.org/jira/browse/RANGER-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921234#comment-17921234 ] Abhishek Kumar commented on RANGER-5008: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/9043ff7] > Handle creation of federated user in Ranger > --- > > Key: RANGER-5008 > URL: https://issues.apache.org/jira/browse/RANGER-5008 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 3.0.0 >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: > 0001-RANGER-5008-Handle-creation-of-Federated-user-in-Ran.patch > > > Handle creation of Federated user in Ranger. This will enable external client > to be identified as federated users for accessing GDS resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5019) spotbugs check doesn't work for sub-module maven build
[ https://issues.apache.org/jira/browse/RANGER-5019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921233#comment-17921233 ] Abhishek Kumar commented on RANGER-5019: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/aa5f2fb] > spotbugs check doesn't work for sub-module maven build > -- > > Key: RANGER-5019 > URL: https://issues.apache.org/jira/browse/RANGER-5019 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When Maven build is run at sub-module level, it fails with this error: > [ERROR] Could not find resource './dev-support/spotbugsIncludeFile.xml'. -> > [Help 1] > > The Jira aims to fix running maven build for sub-modules. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5065) Disable releases for apache.snapshots repo
[
https://issues.apache.org/jira/browse/RANGER-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921231#comment-17921231
]
Abhishek Kumar commented on RANGER-5065:
Merged in [master|https://github.com/apache/ranger/commit/34e4b31]
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/f084dc3]
> Disable releases for apache.snapshots repo
> --
>
> Key: RANGER-5065
> URL: https://issues.apache.org/jira/browse/RANGER-5065
> Project: Ranger
> Issue Type: Improvement
> Components: build-infra
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Major
> Labels: snapshot-repo
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:title=https://github.com/apache/ranger/blob/5c8d4d045190c7d40fac5b2ecc41a588038adb66/pom.xml#L781-L788}
>
>
> true
>
> apache.snapshots.https
> Apache Development Snapshot Repository
>
> https://repository.apache.org/content/repositories/snapshots
>
> {code}
> The Apache snapshot repository should be enabled only for snapshots.
> {{enabled}} is true by default, so {{releases}} omitted is also enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-5066) Improve CI workflow
[
https://issues.apache.org/jira/browse/RANGER-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921230#comment-17921230
]
Abhishek Kumar commented on RANGER-5066:
Merged in [master|https://github.com/apache/ranger/commit/6f57f2f]
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/c87e807]
> Improve CI workflow
> ---
>
> Key: RANGER-5066
> URL: https://issues.apache.org/jira/browse/RANGER-5066
> Project: Ranger
> Issue Type: Improvement
> Components: build-infra
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> I would like to propose some improvements for the CI workflow:
> - Use {{actions/cache}} instead of {{setup-java}}'s simple cache option.
> This allows restoring "similar" caches, not just exact cache hits.
> - Run {{build-11}} only after {{build-8}}. If Java 8 build fails, no need to
> spend time trying with Java 11. Run {{build-11}} and {{docker-build}} (test)
> concurrently.
> - Run the workflow on {{push}} for any branch. This allows contributors to
> run the workflow in their fork, to get CI feedback before opening PR.
> (Without pushing to {{master}} in their fork.)
> Will post a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-5067) ranger-nestedstructure-plugin is not built on linux
[
https://issues.apache.org/jira/browse/RANGER-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921229#comment-17921229
]
Abhishek Kumar commented on RANGER-5067:
Merged in [master|https://github.com/apache/ranger/commit/7e4a629]
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/d18cda9]
> ranger-nestedstructure-plugin is not built on linux
> ---
>
> Key: RANGER-5067
> URL: https://issues.apache.org/jira/browse/RANGER-5067
> Project: Ranger
> Issue Type: Bug
> Components: build-infra
>Affects Versions: 3.0.0, 2.4.0
>Reporter: Attila Doroszlai
>Assignee: Attila Doroszlai
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> {{plugin-nestedstructure}} is not built on Linux, because it is not part of
> the {{linux}} profile. {{distro}} still depends on it. This causes CI to
> try to download it from remote repo.
> {code}
> [INFO] Reactor Summary for ranger 3.0.0-SNAPSHOT:
> [INFO]
> [INFO] ranger . SUCCESS [ 4.278
> s]
> [INFO] Credential Support . SUCCESS [ 44.567
> s]
> [INFO] Audit Component SUCCESS [ 35.431
> s]
> [INFO] ranger-plugin-classloader .. SUCCESS [ 34.992
> s]
> [INFO] Common library for Plugins . SUCCESS [01:20
> min]
> [INFO] Installer Support Component SUCCESS [ 29.891
> s]
> [INFO] Credential Builder . SUCCESS [ 47.060
> s]
> [INFO] Embedded Web Server Invoker SUCCESS [ 44.815
> s]
> [INFO] Jdbc SQL Connector . SUCCESS [ 33.135
> s]
> [INFO] Atlas Security Plugin .. SUCCESS [ 40.359
> s]
> [INFO] Atlas Security Plugin Shim . SUCCESS [ 25.459
> s]
> [INFO] Elasticsearch Security Plugin Shim . SUCCESS [ 15.925
> s]
> [INFO] Elasticsearch Security Plugin .. SUCCESS [ 32.292
> s]
> [INFO] HBase Security Plugin Shim . SUCCESS [ 50.251
> s]
> [INFO] HBase Security Plugin .. SUCCESS [01:18
> min]
> [INFO] Hdfs Security Plugin ... SUCCESS [02:06
> min]
> [INFO] Hdfs Security Plugin Shim .. SUCCESS [ 22.624
> s]
> [INFO] Hive Security Plugin ... SUCCESS [01:58
> min]
> [INFO] Hive Security Plugin Shim .. SUCCESS [ 39.813
> s]
> [INFO] ranger-intg SUCCESS [01:03
> min]
> [INFO] KAFKA Security Plugin .. SUCCESS [03:45
> min]
> [INFO] KAFKA Security Plugin Shim . SUCCESS [ 25.559
> s]
> [INFO] ranger-metrics . SUCCESS [ 46.721
> s]
> [INFO] Key Management Service . SUCCESS [01:14
> min]
> [INFO] KMS Security Plugin SUCCESS [ 32.584
> s]
> [INFO] KMS Security Plugin Shim ... SUCCESS [ 10.694
> s]
> [INFO] Knox Security Plugin Shim .. SUCCESS [ 26.812
> s]
> [INFO] Knox Security Plugin ... SUCCESS [01:30
> min]
> [INFO] Kudu Security Plugin ... SUCCESS [ 24.301
> s]
> [INFO] Kylin Security Plugin .. SUCCESS [01:00
> min]
> [INFO] Kylin Security Plugin Shim . SUCCESS [ 27.745
> s]
> [INFO] NiFi Security Plugin ... SUCCESS [ 55.302
> s]
> [INFO] NiFi Registry Security Plugin .. SUCCESS [ 55.488
> s]
> [INFO] Ozone Security Plugin .. SUCCESS [ 44.257
> s]
> [INFO] OZONE Security Plugin Shim . SUCCESS [ 31.369
> s]
> [INFO] Presto Security Plugin . SUCCESS [01:06
> min]
> [INFO] Presto Security Plugin Shim SUCCESS [ 31.023
> s]
> [INFO] SchemaRegistry Security Plugin . SUCCESS [01:05
> min]
> [INFO] SOLR Security Plugin ... SUCCESS [ 51.599
> s]
> [INFO] SOLR Security Plugin Shim .. SUCCESS [ 30.414
> s]
> [INFO] Sqoop Security Plugin .. SUCCESS [01:03
> min]
> [INFO] Sqoop Security Plugin Shim . SUCCESS [ 23.170
> s]
> [INFO] Storm Security Plugin .. SUCCESS [ 55.737
> s]
> [INFO] Storm Security Plugin shim . SUCCESS [ 25.006
> s]
> [INFO] Ranger HA Common Library ...
[jira] [Commented] (RANGER-5068) Bump rat plugin to 0.16.1
[ https://issues.apache.org/jira/browse/RANGER-5068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921228#comment-17921228 ] Abhishek Kumar commented on RANGER-5068: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/82efe52] > Bump rat plugin to 0.16.1 > - > > Key: RANGER-5068 > URL: https://issues.apache.org/jira/browse/RANGER-5068 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > This version of rat plugin is thread safe. > for more details: > [https://creadur.apache.org/rat/apache-rat-plugin/rat-mojo.html] > It will help in CI as well since multi-threaded builds are running. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5070) Update profiles to include dependent modules
[
https://issues.apache.org/jira/browse/RANGER-5070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921227#comment-17921227
]
Abhishek Kumar commented on RANGER-5070:
Merged in [ranger-2.6|https://github.com/apache/ranger/commit/adb22ff]
> Update profiles to include dependent modules
>
>
> Key: RANGER-5070
> URL: https://issues.apache.org/jira/browse/RANGER-5070
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Modules list in profiles should be updated to include following dependent
> modules:
> # {{ranger-metrics}} where {{kms}} is included
> # {{ranger-auth}} where {{security-admin}} is included
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-5071) CI: Javascript tests with PhantomJS failing
[ https://issues.apache.org/jira/browse/RANGER-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921226#comment-17921226 ] Abhishek Kumar commented on RANGER-5071: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/76115bd] > CI: Javascript tests with PhantomJS failing > > > Key: RANGER-5071 > URL: https://issues.apache.org/jira/browse/RANGER-5071 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Attachments: failing_karma_test.log > > Time Spent: 10m > Remaining Estimate: 0h > > GitHub notifications on running pipelines indicate: > `ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see > https://github.com/actions/runner-images/issues/10636` > Recent CI builds are running on `ubuntu-24.04` which is causing PhantomJS > dependent tests to fail. (Attached the logs) > Upgrade to `ubuntu-24.04` would have updated core libraries like OpenSSL and > potentially removed older versions that PhantomJS depends on, such as > libssl1.1. > Switching to `ubuntu-22.04` to get the CI builds going. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5112) Remove unused dependencies in plugins
[ https://issues.apache.org/jira/browse/RANGER-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5112: --- Fix Version/s: 3.0.0 (was: 2.6.0) > Remove unused dependencies in plugins > - > > Key: RANGER-5112 > URL: https://issues.apache.org/jira/browse/RANGER-5112 > Project: Ranger > Issue Type: Task > Components: plugins >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Grzegorz Kokosinski >Priority: Major > Fix For: 3.0.0 > > > Remove unused dependencies from: > * plugin-kafka > * ranger-elasticsearch-plugin-shim > * ranger-kms-plugin-shim > * unixauthclient -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4888) The ranger setup.sh/db setup fails on Mysql ranger creation
[
https://issues.apache.org/jira/browse/RANGER-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921223#comment-17921223
]
Abhishek Kumar commented on RANGER-4888:
Please update the Priority to Blocker if this needs addressed in the 2.6.0
release, the ranger-2.6 branch will be in locked mode after Jan-29. thanks.
> The ranger setup.sh/db setup fails on Mysql ranger creation
> ---
>
> Key: RANGER-4888
> URL: https://issues.apache.org/jira/browse/RANGER-4888
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 2.4.0
> Environment: Ubuntu 20.04
>Reporter: Steven Weiss
>Priority: Major
> Fix For: 2.6.0
>
>
> {quote}Running setup.sh
>
> Error:
>
> CREATE TABLE `x_trx_log_v2` ( `id` bigint(20) NOT NULL AUTO_INCREMENT,
> `create_time` datetime DEFAULT NULL, `added_by_id` bigint(20) DEFAULT NULL,
> `class_type` int(11) NOT NULL DEFAULT '0', `object_id` bigint(20) DEFAULT
> NULL, `parent_object_id` bigint(20) DEFAULT NULL,
> `parent_object_class_type` int(11) NOT NULL DEFAULT '0',
> `parent_object_name` varchar(1024) DEFAULT NULL, `object_name`
> varchar(1024) DEFAULT NULL, `change_info` MEDIUMTEXT NULL DEFAULT NULL,
> `trx_id` varchar(1024) DEFAULT NULL, `action` varchar(255) DEFAULT NULL,
> `sess_id` varchar(512) DEFAULT NULL, `req_id` varchar(30) DEFAULT NULL,
> `sess_type` varchar(30) DEFAULT NULL, PRIMARY KEY (`id`), KEY
> `x_trx_log_v2_FK_added_by_id` (`added_by_id`), KEY `x_trx_log_v2_cr_time`
> (`create_time`), KEY `x_trx_log_v2_trx_id` (`trx_id`) )ROW_FORMAT=DYNAMIC;
> java.sql.SQLSyntaxErrorException: Specified key was too long; max key length
> is 3072 bytes
> SQLException : SQL state: 42000 java.sql.SQLSyntaxErrorException: Specified
> key was too long; max key length is 3072 bytes ErrorCode: 1071
>
> Problem seems to be the trx_id is too long{quote}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4939) Upgrade Elasticsearch version to 7.17.24
[ https://issues.apache.org/jira/browse/RANGER-4939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921224#comment-17921224 ] Abhishek Kumar commented on RANGER-4939: Please update the Priority to Blocker if this needs addressed in the 2.6.0 release, the ranger-2.6 branch will be in locked mode after Jan-29. thanks. > Upgrade Elasticsearch version to 7.17.24 > > > Key: RANGER-4939 > URL: https://issues.apache.org/jira/browse/RANGER-4939 > Project: Ranger > Issue Type: Improvement > Components: audit >Affects Versions: 2.5.0 >Reporter: FerArribas >Assignee: FerArribas >Priority: Major > Labels: security > Fix For: 3.0.0, 2.5.0, 2.6.0 > > Attachments: > 0001-RANGER-4939-Upgrade-Elasticsearch-version-to-7.17.24.patch > > Original Estimate: 336h > Time Spent: 40m > Remaining Estimate: 335h 20m > > Elasticsearch version 7.10.2 is affected by a high vulnerability > CVE-2023-31418. You must upgrade to version 7.17.22 to fix this > vulnerability. > For the moment, it is not easy to upgrade to a more current version than > 7.17.22 since the Elastic API is not backwards compatible and changes the > implementation a lot. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5104: --- Priority: Blocker (was: Major) > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Blocker > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0-with-pr-511.log, > ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4813) update audit UI to retrieve V2 trx log record
[
https://issues.apache.org/jira/browse/RANGER-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921225#comment-17921225
]
Abhishek Kumar commented on RANGER-4813:
Please update the Priority to Blocker if this needs addressed in the 2.6.0
release, the ranger-2.6 branch will be in locked mode after Jan-29. thanks.
> update audit UI to retrieve V2 trx log record
> -
>
> Key: RANGER-4813
> URL: https://issues.apache.org/jira/browse/RANGER-4813
> Project: Ranger
> Issue Type: Improvement
> Components: admin
>Reporter: Madhan Neethiraj
>Assignee: Abhishek
>Priority: Major
> Fix For: 3.0.0, 2.6.0
>
>
> Currently admin audit UI retrieves multiple V1 trx logs to gather details of
> an update (REST API: service/assets//report/\{transactionId}). This should be
> optimized to retrieve a single V2 trx log record (introduced in RANGER-4803)
> to render in UI. A new API should be added to retrieve V2 trx log record.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-5113) DELETE multiple policies with a wildcard via API call
[
https://issues.apache.org/jira/browse/RANGER-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921222#comment-17921222
]
Abhishek Kumar commented on RANGER-5113:
Please update the Priority to Blocker if this needs addressed in the 2.6.0
release, the ranger-2.6 branch will be in locked mode after Jan-29. thanks.
> DELETE multiple policies with a wildcard via API call
> -
>
> Key: RANGER-5113
> URL: https://issues.apache.org/jira/browse/RANGER-5113
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Guru Thejus
>Assignee: Guru Thejus
>Priority: Major
> Fix For: 2.6.0
>
>
> {color:#172b4d}Currently we do not have a way to delete multiple policies
> using a wild card.{color} This improvement is to provide a new API for the
> same
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-5117) Fix ssl config param in installprop2xml.properties
[ https://issues.apache.org/jira/browse/RANGER-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921221#comment-17921221 ] Abhishek Kumar commented on RANGER-5117: Merged in [master|https://github.com/apache/ranger/commit/fb8d3b8] Merged in [ranger-2.6|https://github.com/apache/ranger/commit/bb80bb4] > Fix ssl config param in installprop2xml.properties > -- > > Key: RANGER-5117 > URL: https://issues.apache.org/jira/browse/RANGER-5117 > Project: Ranger > Issue Type: Bug > Components: usersync >Affects Versions: 2.0.0, 2.1.0 >Reporter: Abhishek Kumar >Priority: Major > Fix For: 2.6.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5117) Fix ssl config param in installprop2xml.properties
Abhishek Kumar created RANGER-5117: -- Summary: Fix ssl config param in installprop2xml.properties Key: RANGER-5117 URL: https://issues.apache.org/jira/browse/RANGER-5117 Project: Ranger Issue Type: Bug Components: usersync Reporter: Abhishek Kumar Fix For: 2.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-4931) java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field list'
[
https://issues.apache.org/jira/browse/RANGER-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17921214#comment-17921214
]
Abhishek Kumar commented on RANGER-4931:
[~basapuram.kumar] done
> java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field
> list'
>
>
> Key: RANGER-4931
> URL: https://issues.apache.org/jira/browse/RANGER-4931
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.5.0
>Reporter: Basapuram Kumar
>Assignee: Basapuram Kumar
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Trying upgrade ranger from 2.3.0 to 2.5.0, but failed with the below error.
>
>
> {noformat}
> 2024-09-12 20:32:52,340 [I] Patch 070-add-gds-perm.sql is being applied..
> 2024-09-12 20:32:52,340 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -input
> /usr/odp/current/ranger-admin/db/mysql/patches/070-add-gds-perm.sql
> Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver
> class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered
> via the SPI and manual loading of the driver class is generally unnecessary.
> Error executing: call insertRangerPrerequisiteGDSEntries();
> java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field
> list'
> SQLException : SQL state: 42S22 java.sql.SQLSyntaxErrorException: Unknown
> column 'rangerusersyncID' in 'field list' ErrorCode: 1054
> 2024-09-12 20:32:52,542 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -query "select version from x_db_version_h where
> version = '070' and active = 'Y';"
> 2024-09-12 20:32:52,704 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -query "delete from x_db_version_h where version =
> '070' and active = 'N' and updated_by='ce19.acceldata.dvl';"
> 2024-09-12 20:32:52,858 [E] 070-add-gds-perm.sql import failed!{noformat}
>
>
> As a workaround, added the requuired columns in the "070-add-gds-perm.sql ",
> with that, able to pass this stage.
> Added these columns after L43.
> [https://github.com/apache/ranger/blob/master/security-admin/db/mysql/patches/070-add-gds-perm.sql#L43]
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4931) java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field list'
[
https://issues.apache.org/jira/browse/RANGER-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Kumar updated RANGER-4931:
---
Fix Version/s: 3.0.0
> java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field
> list'
>
>
> Key: RANGER-4931
> URL: https://issues.apache.org/jira/browse/RANGER-4931
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.5.0
>Reporter: Basapuram Kumar
>Assignee: Basapuram Kumar
>Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Trying upgrade ranger from 2.3.0 to 2.5.0, but failed with the below error.
>
>
> {noformat}
> 2024-09-12 20:32:52,340 [I] Patch 070-add-gds-perm.sql is being applied..
> 2024-09-12 20:32:52,340 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -input
> /usr/odp/current/ranger-admin/db/mysql/patches/070-add-gds-perm.sql
> Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver
> class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered
> via the SPI and manual loading of the driver class is generally unnecessary.
> Error executing: call insertRangerPrerequisiteGDSEntries();
> java.sql.SQLSyntaxErrorException: Unknown column 'rangerusersyncID' in 'field
> list'
> SQLException : SQL state: 42S22 java.sql.SQLSyntaxErrorException: Unknown
> column 'rangerusersyncID' in 'field list' ErrorCode: 1054
> 2024-09-12 20:32:52,542 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -query "select version from x_db_version_h where
> version = '070' and active = 'Y';"
> 2024-09-12 20:32:52,704 [JISQL] /usr/lib/jvm/java-11-openjdk/bin/java -cp
> /usr/odp/current/ranger-admin/ews/lib/mysql-jdbc-driver.jar:/usr/odp/current/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://ce19.acceldata.dvl/ranger?useSSL=false -u 'ranger' -p ''
> -noheader -trim -c \; -query "delete from x_db_version_h where version =
> '070' and active = 'N' and updated_by='ce19.acceldata.dvl';"
> 2024-09-12 20:32:52,858 [E] 070-add-gds-perm.sql import failed!{noformat}
>
>
> As a workaround, added the requuired columns in the "070-add-gds-perm.sql ",
> with that, able to pass this stage.
> Added these columns after L43.
> [https://github.com/apache/ranger/blob/master/security-admin/db/mysql/patches/070-add-gds-perm.sql#L43]
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5104: --- Attachment: ranger-upgrade-2.2.0-to-2.6.0-with-pr-511.log > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0-with-pr-511.log, > ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5061) security-admin module: update for code readability improvement
[ https://issues.apache.org/jira/browse/RANGER-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17917015#comment-17917015 ] Abhishek Kumar commented on RANGER-5061: Follow-up fix: [#PR 514|https://github.com/apache/ranger/pull/514] merged in [master|https://github.com/apache/ranger/commit/a828d3f] > security-admin module: update for code readability improvement > -- > > Key: RANGER-5061 > URL: https://issues.apache.org/jira/browse/RANGER-5061 > Project: Ranger > Issue Type: Sub-task > Components: admin >Reporter: Madhan Neethiraj >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Time Spent: 5h 50m > Remaining Estimate: 0h > > Branch Name: *RANGER-5061_master* > ||Modules (security-admin/src/main/java/) ||Assignee||Status|| > |org.apache.ranger.amazon|Dinesh|Merged in RANGER-5061_master| > |org.apache.ranger.authentication|Dinesh|Merged in RANGER-5061_master| > |org.apache.ranger.biz|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.common|Vyom|Merged in RANGER-5061_master| > |org.apache.ranger.credentialapi|Dinesh|Merged in RANGER-5061 > [_master|https://github.com/apache/ranger/pull/496]| > |org.apache.ranger.db|Dinesh|Merged in RANGER-5061_master| > |org.apache.ranger.elasticsearch|Vyom|Merged in RANGER-5061_master| > |org.apache.ranger.entity|Vyom|Merged in RANGER-5061_master| > |org.apache.ranger.json|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.metrics|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.patch|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.rest|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.security|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.service|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.solr|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.util|Ramesh|Merged in RANGER-5061_master | > |org.apache.ranger.validation|Pradeep|Merged in RANGER-5061_master| > |org.apache.ranger.view|Pradeep|Merged in RANGER-5061_master| > |javax.ws.rs.core|Pradeep|Merged in RANGER-5061_master| > > ||Unit Tests (security-admin/src/test/java/) ||Assignee||Status|| > |org.apache.ranger.audit|Abhishek Kumar|Merged| > |org.apache.ranger.biz|Abhishek Kumar|Merged| > |org.apache.ranger.common|Abhishek Kumar|Merged| > |org.apache.ranger.elasticsearch|Abhishek Kumar|Merged| > |org.apache.ranger.patch|Abhishek Kumar|Merged| > |org.apache.ranger.rest|Abhishek Kumar|Merged| > |org.apache.ranger.security|Abhishek Kumar|Merged| > |org.apache.ranger.service|Abhishek Kumar|Merged| > |org.apache.ranger.util|Abhishek Kumar|Merged| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5104: --- Affects Version/s: 2.2.0 2.1.0 2.0.0 > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.0.0, 2.1.0, 2.2.0 >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5104: --- Attachment: ranger-upgrade-2.2.0-to-2.6.0.log > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5104) Ranger Upgrade is failing while executing the PatchPreSql057_ForUpdateToUniqueGUID_J10052
[ https://issues.apache.org/jira/browse/RANGER-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5104: --- Fix Version/s: 2.6.0 > Ranger Upgrade is failing while executing the > PatchPreSql057_ForUpdateToUniqueGUID_J10052 > - > > Key: RANGER-5104 > URL: https://issues.apache.org/jira/browse/RANGER-5104 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Pradeep Agrawal >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Attachments: ranger-upgrade-2.2.0-to-2.6.0.log > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-5114) Build and Publish Ranger Docker Images with GitHub Actions
Abhishek Kumar created RANGER-5114: -- Summary: Build and Publish Ranger Docker Images with GitHub Actions Key: RANGER-5114 URL: https://issues.apache.org/jira/browse/RANGER-5114 Project: Ranger Issue Type: Task Components: Ranger Reporter: Abhishek Kumar Assignee: Abhishek Kumar Implement a workflow file which can build ranger docker images on demand and publish them to DockerHub. This will also be useful during ranger release tasks. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (RANGER-5080) Docker setup to support SQL Server database
[ https://issues.apache.org/jira/browse/RANGER-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916875#comment-17916875 ] Abhishek Kumar commented on RANGER-5080: Merged in [ranger-2.6|https://github.com/apache/ranger/commit/0b5602c] > Docker setup to support SQL Server database > --- > > Key: RANGER-5080 > URL: https://issues.apache.org/jira/browse/RANGER-5080 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Docker setup in dev-support/ranger-docker currently supports MySQL,Postgres > and Oracle database flavors. > > This should be extended to support MS SQL Server database as well, to make it > easier to test Ranger with it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5080) Docker setup to support SQL Server database
[ https://issues.apache.org/jira/browse/RANGER-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5080: --- Fix Version/s: 2.6.0 > Docker setup to support SQL Server database > --- > > Key: RANGER-5080 > URL: https://issues.apache.org/jira/browse/RANGER-5080 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0, 2.6.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Docker setup in dev-support/ranger-docker currently supports MySQL,Postgres > and Oracle database flavors. > > This should be extended to support MS SQL Server database as well, to make it > easier to test Ranger with it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-5102) Add config parameter to allow audits to HDFS in both WRITE and APPEND modes in case of errors/exceptions
[ https://issues.apache.org/jira/browse/RANGER-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar updated RANGER-5102: --- Fix Version/s: 3.0.0 (was: 2.6.0) > Add config parameter to allow audits to HDFS in both WRITE and APPEND modes > in case of errors/exceptions > > > Key: RANGER-5102 > URL: https://issues.apache.org/jira/browse/RANGER-5102 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.5.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Ranger audits to HDFS currently use APPEND mode in case of errors/exceptions > encountered in writing audits to HDFS destination (to prevent large number of > audit files) and fallbacks to WRITE mode if unable to APPEND. > > Add a config param to enable APPEND mode (to be used under specific > circumstances). -- This message was sent by Atlassian Jira (v8.20.10#820010)
