Anuja Leekha created RANGER-1612:
Summary: When servicedef is accessed, one of the properties
"enableDenyPolicies" is returned as "false" if there is no value set for it.
Key: RANGER-1612
URL:
Colm, Peng.jianhua,
> I will encourage future review requests that have a very trivial spelling
> fix to hold on to the fix for a while, so that we can fix multiple spelling
> fixes etc. at the same time.
Consolidating trivial updates into a single patch/JIRA will certainly help.
However,
Zsombor,
>> Instead of discouraging contributions
My suggestion was to discourage patches that have *only* very, very tiny and
non-essential updates – like changing case of a label word from “G” to “g”,
removing a blank line, etc; or patches that touch hundreds of files for
[
https://issues.apache.org/jira/browse/RANGER-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang resolved RANGER-1575.
-
Resolution: Fixed
> Some users hope that the pid file of the Ranger Admin can be unified
>
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59255/#review175947
---
Ship it!
Ship It!
- Qiang Zhang
On 五月 23, 2017, 4:07 a.m.,
Instead of discouraging contributions, the project should ease the
contribution - and also the review process.
The current JIRA + Reviewboard infrastructure needs a lot's of unnecessary
manual steps, which hurts everyone who wants to help.
Currently, the contributor needs to do the following,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59523/
---
Review request for ranger.
Bugs: RANGER-689
[
https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-689:
---
Attachment: 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch
> For
[
https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-689:
---
Fix Version/s: 1.0.0
> For Solr plugin, use resources folders for adding Ranger
[
https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16022697#comment-16022697
]
Colm O hEigeartaigh commented on RANGER-689:
Putting the jars into service/lib/ext does not
[
https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-689:
---
Summary: For Solr plugin, use resources folders for adding Ranger
properties (was:
[
https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh reassigned RANGER-689:
--
Assignee: Colm O hEigeartaigh
> For Solr plugin, use lib/ext and resources
+1 for Madhan's recommendations,
Colm, I agree that we should not discourage new contributions. However, I
think, we should also not encourage such single line/whitespace
contributions. We want contributors who can do more functionals/feature
changes and while doing that they can also fix the
Hi Madhan,
Merging these small issues to other branches will increase the workload and the
probability of error. If possible, we can undertake similar tasks when some
important issues need to be merged into other branches.
With the improvement of quality, these small issues will be
[
https://issues.apache.org/jira/browse/RANGER-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1584:
Fix Version/s: 1.0.0
> Allow tagsync to support log directory from Ambari
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/59255/#review175914
---
Ship it!
Ship It!
- Colm O hEigeartaigh
On May 23, 2017,
[
https://issues.apache.org/jira/browse/RANGER-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh closed RANGER-1049.
---
> Testing connection at a Kerberos server
> ---
>
>
[
https://issues.apache.org/jira/browse/RANGER-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh closed RANGER-1050.
---
> Change my name on all systems
> -
>
> Key:
[
https://issues.apache.org/jira/browse/RANGER-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved RANGER-1050.
-
Resolution: Not A Problem
> Change my name on all systems
>
Hi Madhan,
Trivial commits provide a path to get new contributors on board to the
project - something that the project needs IMO. Yes it may make backporting
fixes a little more difficult, but it's hardly an intractable problem to
figure out some whitespace changes between branches - it's not as
[
https://issues.apache.org/jira/browse/RANGER-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang resolved RANGER-1610.
-
Resolution: Invalid
> Modify the Logger scope and keep the consistent info in
[
https://issues.apache.org/jira/browse/RANGER-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Qiang Zhang reassigned RANGER-1610:
---
Assignee: Qiang Zhang
> Modify the Logger scope and keep the consistent info in
All,
I notice a number of recent patches address trivial issues like white space,
spelling mistakes (one patch just changed a single letter in a label). And few
other patches update a large number of files for trivial/non-functional changes
– like whitespaces. I strongly suggest we refrain
23 matches
Mail list logo
