[CARBONDATA-3592] Fix query on bloom in case of multiple data files in one segment

Problem:
1. Query on bloom datamap fails when there are multiple data files in one segment.
2. Query on bloom is giving wrong results in case of multiple carbondata files.

Solution:
1. Old pruned index files were cleared from the FilteredIndexSharedNames list. So further
pruning was not done on all the valid index files. Hence added a check to clear the index
files only in valid scenarios. Also handled the case where wrong blocklet id is passed while
creating the blocklet from relative blocklet id.
2. Make the partitions based on block path so that all the CarbonInputSplits in a MultiBlockSplit
are used for bloom reading. This means 1 task for 1 shard(unique block path).

This closes #3474
4 files changed
tree: 0fda026feca26b163eb5a7f3150572f9c656e93a
  1. .github/
  2. assembly/
  3. bin/
  4. build/
  5. common/
  6. conf/
  7. core/
  8. datamap/
  9. dev/
  10. docs/
  11. examples/
  12. format/
  13. hadoop/
  14. integration/
  15. licenses-binary/
  16. processing/
  17. python/
  18. store/
  19. streaming/
  20. tools/
  21. .gitignore
  22. LICENSE
  23. NOTICE
  24. pom.xml
  25. README.md
README.md

Apache CarbonData is an indexed columnar data store solution for fast analytics on big data platform, e.g.Apache Hadoop, Apache Spark, etc.

You can find the latest CarbonData document and learn more at: http://carbondata.apache.org

CarbonData cwiki

Visit count: HitCount

Status

Spark2.2: Build Status Coverage Status

Features

CarbonData file format is a columnar store in HDFS, it has many features that a modern columnar format has, such as splittable, compression schema ,complex data type etc, and CarbonData has following unique features:

  • Stores data along with index: it can significantly accelerate query performance and reduces the I/O scans and CPU resources, where there are filters in the query. CarbonData index consists of multiple level of indices, a processing framework can leverage this index to reduce the task it needs to schedule and process, and it can also do skip scan in more finer grain unit (called blocklet) in task side scanning instead of scanning the whole file.
  • Operable encoded data :Through supporting efficient compression and global encoding schemes, can query on compressed/encoded data, the data can be converted just before returning the results to the users, which is “late materialized”.
  • Supports for various use cases with one single Data format : like interactive OLAP-style query, Sequential Access (big scan), Random Access (narrow scan).

Building CarbonData

CarbonData is built using Apache Maven, to build CarbonData

Online Documentation

Integration

Other Technical Material

Fork and Contribute

This is an active open source project for everyone, and we are always open to people who want to use this system or contribute to it. This guide document introduce how to contribute to CarbonData.

Contact us

To get involved in CarbonData:

About

Apache CarbonData is an open source project of The Apache Software Foundation (ASF).