[
https://issues.apache.org/jira/browse/RANGER-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mehul Parikh reassigned RANGER-2229:
Assignee: bhavik patel
> Perform graceful terminate with retries before doing forceful ki
[
https://issues.apache.org/jira/browse/RANGER-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620169#comment-16620169
]
Nitin Galave edited comment on RANGER-2215 at 9/19/18 6:30 AM:
---
[
https://issues.apache.org/jira/browse/RANGER-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620169#comment-16620169
]
Nitin Galave commented on RANGER-2215:
--
Committed to [master|
https://github.com/a
[
https://issues.apache.org/jira/browse/RANGER-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mehul Parikh reassigned RANGER-2220:
Assignee: Dhaval Rajpara
> Admin UI loads slowly because of many small JavaScript files
>
suja s created RANGER-2229:
--
Summary: Perform graceful terminate with retries before doing
forceful kill for usersync and tagsync
Key: RANGER-2229
URL: https://issues.apache.org/jira/browse/RANGER-2229
Proje
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68684/#review208748
---
Ship it!
Ship It!
- Mehul Parikh
On Sept. 11, 2018, 1:26 p.m
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/68684/#review208746
---
Ship it!
Ship It!
- Gautam Borad
On Sept. 11, 2018, 1:26 p.m
[
https://issues.apache.org/jira/browse/RANGER-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2207:
-
Fix Version/s: 2.0.0
> Allow resources to appear in column mask policies without
[
https://issues.apache.org/jira/browse/RANGER-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2218:
-
Fix Version/s: 2.0.0
> Service-Definition update should not allow updates to nam
Thanks. Filed https://issues.apache.org/jira/browse/RANGER-2228
I will work on the release.
From: Colm O hEigeartaigh
Sent: Tuesday, September 18, 2018 12:08 PM
To: Velmurugan Periasamy
Cc: dev@ranger.apache.org
Subject: Re: Atlas version
Sure, that ma
[
https://issues.apache.org/jira/browse/RANGER-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2228:
-
Fix Version/s: (was: 1.1.0)
1.2.0
> Release Ranger 1.2.0
[
https://issues.apache.org/jira/browse/RANGER-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Velmurugan Periasamy updated RANGER-2228:
-
Description: Track release activities for Ranger 1.2.0 (was: Track release
acti
Velmurugan Periasamy created RANGER-2228:
Summary: Release Ranger 1.2.0
Key: RANGER-2228
URL: https://issues.apache.org/jira/browse/RANGER-2228
Project: Ranger
Issue Type: Task
Sure, that makes sense to me.
Colm.
On Tue, Sep 18, 2018 at 5:04 PM Velmurugan Periasamy wrote:
> Thank you Colm. My suggestion is to release Ranger 1.2.0 with Atlas
> version 1.1.0 (which just got released).
>
> Master can continue tracking Atlas 2.0.0-SNAPSHOT, and 1.1+ lines can be
> updated
Thank you Colm. My suggestion is to release Ranger 1.2.0 with Atlas version
1.1.0 (which just got released).
Master can continue tracking Atlas 2.0.0-SNAPSHOT, and 1.1+ lines can be
updated to Atlas 1.1.0.
Thoughts?
From: Colm O hEigeartaigh
Sent:
Hi all,
I'm wondering if there's a reason that we rely on Atlas 2.0.0-SNAPSHOT
instead of 1.1.0? The build works fine with Atlas 1.1.0. In particular, we
released Ranger 1.1.0 with a dependency on an atlas SNAPSHOT which is not
great.
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http:/
[
https://issues.apache.org/jira/browse/RANGER-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-2190:
Fix Version/s: (was: 1.1.0)
> Auto populate the relationship ends when relatio
> On 九月 12, 2018, 8:37 a.m., Vishal Suvagia wrote:
> > @Qiang Zhang, Kindly add the testing done with this patch ?
I am verifying the issue according to “Testing Done”
- Qiang
---
This is an automatically generated e-mail. To reply, vis
18 matches
Mail list logo