[ 
https://issues.apache.org/jira/browse/KYLIN-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442055#comment-17442055
 ] 

ASF GitHub Bot commented on KYLIN-5099:
---------------------------------------

zhangayqian opened a new pull request #1766:
URL: https://github.com/apache/kylin/pull/1766


   …lin4
   
   ## 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]


> parquet file size is too big in kylin4 with spark3 than kylin3 with mr
> ----------------------------------------------------------------------
>
>                 Key: KYLIN-5099
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5099
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v4.0.0
>            Reporter: tanyao
>            Priority: Blocker
>         Attachments: image-2021-10-15-10-43-54-830.png, 
> image-2021-10-15-10-44-49-178.png, image-2021-10-18-10-00-34-440.png, 
> image-2021-10-18-10-02-07-998.png, image-2021-10-18-10-06-15-839.png, 
> screenshot-1.png
>
>
> hi ,
>  i am trying to use spark 3.1.1 as the build engine in kylin4.0, the hive 
> table has 200W+ rows with orc type, and there are 10 dimensions definded, the 
> original size is about 50M.
> when i use kylin4.0 to build this cube ,the final parquet files size all 
> together  is 1G+,that is to say , a single segment  is about 1G+. However , i 
> use the same hive table data with the same cube model and dimensions , the 
> hbase segment size is just 100M+. In case of kylin4.0, all spark params are 
> set automatically by kylin
> why this happened? And the building time in kylin4.0 is not faster then 
> kylin3.1 , even worse! both of them take about 10mins, i can not find the 
> benefits about kylin4.0
> !image-2021-10-15-10-43-54-830.png!
>  
> !image-2021-10-15-10-44-49-178.png!
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to