[
https://issues.apache.org/jira/browse/KYLIN-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432898#comment-17432898
]
ASF GitHub Bot commented on KYLIN-5069:
---------------------------------------
zhangayqian opened a new pull request #1754:
URL: https://github.com/apache/kylin/pull/1754
## 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.
## Github Branch
As most of the development works are on Kylin 4, we need to switch it as
main branch. Apache Kylin community changes the branch settings on Github since
2021-08-04 :
1. The original branch _kylin-on-parquet-v2_ for **Kylin 4.X** (Parquet
Storage) has been renamed to branch **main**, and configured as the **default**
branch;
2. The original branch _master_ for **Kylin 3.X** (HBase Storage) has been
renamed to branch **kylin3** ;
Please check [Intro to Kylin 4
architecture](https://kylin.apache.org/blog/2021/07/02/Apache-Kylin4-A-new-storage-and-compute-architecture/)
and [INFRA-22166](https://issues.apache.org/jira/browse/INFRA-22166) if you
are interested.
## 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](https://issues.apache.org/jira/browse/KYLIN), 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
- [ ] I have added necessary documentation (if appropriate)
- [ ] 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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
> Remove find-hive-dependency.sh in Kylin 4
> -----------------------------------------
>
> Key: KYLIN-5069
> URL: https://issues.apache.org/jira/browse/KYLIN-5069
> Project: Kylin
> Issue Type: Improvement
> Affects Versions: v4.0.0
> Reporter: Xiaoxiang Yu
> Assignee: Yaqian Zhang
> Priority: Major
> Fix For: v4.0.1
>
> Attachments: image-2021-08-30-16-10-46-712.png
>
>
> In kylin.sh, Kylin introduces a lot of jars into Kylin instance's class path,
> via find-hive-dependency.sh and "hadoop classpath". So class conflict issues
> happened often, and most of them are related with hive jars. I think it is
> better to remove 'find-hive-dependency.sh' and use SparkSession to fetch
> Hive meta.
>
> Following is part of script kylin.sh :
> {code:java}
> tomcat_classpath=${tomcat_root}/bin/bootstrap.jar:${tomcat_root}/bin/tomcat-juli.jar:${tomcat_root}/lib/*
> export
> KYLIN_TOMCAT_CLASSPATH=${tomcat_classpath}:${KYLIN_HOME}/conf:${KYLIN_HOME}/lib/*:${KYLIN_HOME}/ext/*:${hadoop_dependencies}:${flink_dependency}
> {code}
>
> Some exception looks like this:
> !image-2021-08-30-16-10-46-712.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
