kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [kylin] hit-lacus opened a new pull request #1535: KYLIN-4858 Support Kylin4 deployment on CDH 6.X
Date Mon, 04 Jan 2021 06:54:31 GMT

hit-lacus opened a new pull request #1535:

   ## Proposed changes
   Describe the big picture of your changes here to communicate to the maintainers why we
should accept this pull request. If it fixes a bug or resolves a feature request, be sure
to link to that issue.
   ## Types of changes
   What types of changes does your code introduce to Kylin?
   _Put an `x` in the boxes that apply_
   - [ ] Bugfix (non-breaking change which fixes an issue)
   - [ ] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing functionality to not work
as expected)
   - [ ] Documentation Update (if none of the other choices apply)
   ## Checklist
   _Put an `x` in the boxes that apply. You can also fill these out after creating the PR.
If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply
a reminder of what we are going to look for before merging your code._
   - [ ] I have create an issue on [Kylin's jira](,
and have described the bug/feature there in detail
   - [ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin
project open-source"
   - [ ] Compiling and unit tests pass locally with my changes
   - [ ] I have added tests that prove my fix is effective or that my feature works
   - [ ] If this change need a document change, I will prepare another pr against the `document`
   - [ ] Any dependent changes have been merged
   ## Further comments
   If this is a relatively large or complex change, kick off the discussion at user@kylin
or dev@kylin by explaining why you chose the solution you did and what alternatives you considered,

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:

View raw message