zzcclp opened a new pull request #1191: URL: https://github.com/apache/kylin/pull/1191
## Proposed changes ### Problems: When run docker image for the first time, sometimes hive command will be executed concurrently and it will insert two version records into the VERSION table, this will lead to start kylin unsuccessfully. **error messages:** Something wrong with Hive CLI or Beeline, please execute Hive CLI or Beeline CLI in terminal to find the root cause. ### Solutions: call script $KYLIN_HOME/bin/check-hive-usability.sh before all kylin.sh, it will insert one version record into VERSION table . ### Tested on my laptop: 1. cd kylin/docker 2. ./build_image.sh 3. docker run -d -m 8G -p 7070:7070 -p 8088:8088 -p 50070:50070 -p 8032:8032 -p 8042:8042 -p 16010:16010 -p 8998:8998 -p 2181:2181 apachekylin/apache-kylin-standalone:latest 4. all dependents and kylin worked successfully. 5. docker container stop container-id 6. docker container start container-id, all worked successfully. ## Types of changes What types of changes does your code introduce to Kylin? _Put an `x` in the boxes that apply_ - [x] 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._ - [x] I have create an issue on [Kylin's jira](https://issues.apache.org/jira/browse/KYLIN), and have described the bug/feature there in detail - [x] 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` branch - [ ] 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, etc... ---------------------------------------------------------------- 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: us...@infra.apache.org
