capistrant opened a new pull request #8847: Fix groupMapping endpoint URIs in 
druid-basic-security doc
   <!-- Thanks for trying to help us make Apache Druid (incubating) be the best 
it can be! Please fill out as much of the following information as is possible 
(where relevant, and remove it when irrelevant) to help make the intention and 
scope of this PR clear in order to ease review. -->
   <!-- Replace XXXX with the id of the issue fixed in this PR. Remove this 
section if there is no corresponding issue. Don't reference the issue in the 
title of this pull-request. -->
   <!-- If you are a committer, follow the PR action item checklist for 
   ### Description
   <!-- Describe the goal of this PR, what problem are you fixing. If there is 
a corresponding issue (referenced above), it's not necessary to repeat the 
description here, however, you may choose to keep one summary sentence. -->
   <!-- Describe your patch: what did you change in code? How did you fix the 
problem? -->
   <!-- If there are several relatively logically separate changes in this PR, 
create a mini-section for each of them. For example: -->
   Documentation update only. I was testing out the new LDAP feature and found 
some inconsistencies in the docs. Fixes the URIs for LDAP group mapping 
endpoints. The docs do not reflect the camel casing that is present in the code 
for the endpoint. 
 This change will properly reflect the implementation.
   In each section, please describe design decisions made, including:
    - Choice of algorithms
    - Behavioral aspects. What configuration values are acceptable? How are 
corner cases and error conditions handled, such as when there are insufficient 
    - Class organization and design (how the logic is split between classes, 
inheritance, composition, design patterns)
    - Method organization and design (how the logic is split between methods, 
parameters and return types)
    - Naming (class, method, API, configuration, HTTP endpoint, names of 
emitted metrics)
   <!-- It's good to describe an alternative design (or mention an alternative 
name) for every design (or naming) decision point and compare the alternatives 
with the designs that you've implemented (or the names you've chosen) to 
highlight the advantages of the chosen designs and names. -->
   <!-- If there was a discussion of the design of the feature implemented in 
this PR elsewhere (e. g. a "Proposal" issue, any other issue, or a thread in 
the development mailing list), link to that discussion from this PR description 
and explain what have changed in your final design compared to your original 
proposal or the consensus version in the end of the discussion. If something 
hasn't changed since the original discussion, you can omit a detailed 
discussion of those aspects of the design here, perhaps apart from brief 
mentioning for the sake of readability of this PR description. -->
   <!-- Some of the aspects mentioned above may be omitted for simple and small 
changes. -->
   This PR has:
   - [X] been self-reviewed.
   - [X] been tested in a test Druid cluster.
   <!-- Check the items by putting "x" in the brackets for the done things. Not 
all of these items apply to every PR. Remove the items which are not done or 
not relevant to the PR. None of the items from the checklist above are strictly 
necessary, but it would be very helpful if you at least self-review the PR. -->
   ##### Key changed/added classes in this PR
   None. Docs only!

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to