GitHub user kunal642 opened a pull request:

    https://github.com/apache/carbondata/pull/2869

    [WIP] Changes for improving carbon reader performance

    1. Added carbondata file listing for getting splits to avoid block/blocklet 
datamap
    loading when filter expressions is not provided by the user
    
    2. Implemented Vectorized reader, exposes a property to switch between 
record reader/vector reader.
    
    Be sure to do all of the following checklist to help us incorporate 
    your contribution quickly and easily:
    
     - [ ] Any interfaces changed?
     
     - [ ] Any backward compatibility impacted?
     
     - [ ] Document update required?
    
     - [ ] Testing done
            Please provide details on 
            - Whether new unit test cases have been added or why no new tests 
are required?
            - How it is tested? Please attach test report.
            - Is it a performance related change? Please attach the performance 
test report.
            - Any additional information to help reviewers in testing this 
change.
           
     - [ ] For large changes, please consider breaking it into sub-tasks under 
an umbrella JIRA. 
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kunal642/carbondata reader_perf_improvement

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/carbondata/pull/2869.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2869
    
----
commit 8cf00c5dc94e8e3a1ee83a9e6416772a671f2830
Author: kunal642 <kunalkapoor642@...>
Date:   2018-10-26T06:13:22Z

    Changes for improving carbon reader performance
    
    1. Added carbondata file listing for getting splits to avoid block/blocklet 
datamap
    loading when filter expressions is not provided by the user
    
    2. Implemented Vectorized reader, exposes a property to switch between 
record reader/vector reader.

----


---

Reply via email to