[GitHub] [pulsar] yoda-mon opened a new pull request, #18040: [improve][docs] Add chroot path related informations

[GitBox]

yoda-mon opened a new pull request, #18040:
URL: https://github.com/apache/pulsar/pull/18040

   <!--
   ### Contribution Checklist
     
     - PR title format should be *[type][component] summary*. For details, see 
*[Guideline - Pulsar PR Naming 
Convention](https://docs.google.com/document/d/1d8Pw6ZbWk-_pCKdOmdvx9rnhPiyuxwq60_TrD68d7BA/edit#heading=h.trs9rsex3xom)*.
 
   
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
     
     - Each commit in the pull request has a meaningful commit message
   
     - Once all items of the checklist are addressed, remove the above text and 
this checklist, leaving only the filled out template below.
   -->
   
   <!-- Either this PR fixes an issue, -->
   
   
   
   <!-- or this PR is one task of an issue -->
   
   
   
   ### Motivation
   
   <!-- Explain here the context, and why you're making that change. What is 
the problem you're trying to solve. -->
   On this PR https://github.com/apache/pulsar/pull/13985, `/my-chroot-path` 
was added to the URLs.
   If users follow the document, `bookkeeper.conf` and `broker.conf` lacks the 
informations about the path and fail to set up the cluster.
   
   ### Modifications
   
   <!-- Describe the modifications you've done. -->
   Add chroot path related informations to the documents and add `zk://` prefix 
to metadata URLs.
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. Please attach the local 
preview screenshots (run `sh start.sh` at `pulsar/site2/website`) to your PR 
description, or else your PR might not get merged. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   <img width="1688" alt="Screen Shot 2022-10-13 at 19 49 19" 
src="https://user-images.githubusercontent.com/14937752/195582431-0cc9077d-61df-4344-9528-c850e9c6313f.png";>
   <img width="1683" alt="Screen Shot 2022-10-13 at 19 49 59" 
src="https://user-images.githubusercontent.com/14937752/195582439-8419d206-196a-4fb9-aa1f-b44214ccea57.png";>
   
   
   ### Matching PR in forked repository
   
   PR in forked repository: <!-- ENTER URL HERE -->
   
   <!--
   After opening this PR, the build in apache/pulsar will fail and instructions 
will
   be provided for opening a PR in the PR author's forked repository.
   
   apache/pulsar pull requests should be first tested in your own fork since 
the 
   apache/pulsar CI based on GitHub Actions has constrained resources and quota.
   GitHub Actions provides separate quota for pull requests that are executed 
in 
   a forked repository.
   
   The tests will be run in the forked repository until all PR review comments 
have
   been handled, the tests pass and the PR is approved by a reviewer.
   -->
   


-- 
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.

To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org