Parquet Pushdown
- Lingua principale
- Java
- Stelle
- 3.1k
- Fork
- 1.6k
- Merge medio
- 3g 12h
- PR unite (30g)
- 33
Descrizione
Hi,
I am doing some experiments with Apache Parquet to test Predicate pushdown and effect of different row group sizes. My assumptions are:
1) Parquet reader first read the metadata to filter out row groups and data pages
2) Then, it reads only those row groups and data pages which match the filter.
3) The total size of read should be the **sum of row group size and size of meta data**.
I have a wide table with 1184 columns. 2 columns are long type and remaining columns are binary. One of the long column is sorted and unique. I disabled dictionary encoding and compression. My file size is 34GB in CSV. I converted it to Parquet. I tried with two options
1) Generate only 1 File of Parquet (i.e. 43GB)
2) Generate multiple files of Parquet (i.e., overall size 43GB).
I allow only 1 Mapper to eliminate the effect of parallelism.
I have a query to search 1 record from the sorted column. The results are for row group 16MB and data page size of 1MB
When there is only 1 file of Parquet.
Input(s):
Successfully read **1 records (22135659519 bytes)** from: "/output/wide/16777216/1048576"
When there is multiple file of Parquet
Input(s):
Successfully read **1 records (800413428 bytes)** from: "/output/wide/16777216/1048576"
My questions are:
1) Why there is big difference. In one file, I am reading 22GB and with multiple file, It is reading 800MB. This is a bug or what?
2) Why it is not reading 16MB + Size of meta data (which is 252MB). Why it is reading more than that?
3) Can I rely on the pig statistics for estimating bytes read?
4) My assumptions are correct or am I missing something?
Could you please have a look into this problem and guide me if it is a bug ?
Logs are attached with this email.
Thank you
Regards
Rana Faisal
**Environment**: Apache Hadoop 2.7.0
Apache Pig 0.17.0
Apache Parquet 1.9.0
**Reporter**: [Rana Faisal Munir](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ranafaisal342)
#### Original Issue Attachments:
- [selc_32_16777216_1048576_sorted_multiplefile.log](https://issues.apache.org/jira/secure/attachment/12905699/selc_32_16777216_1048576_sorted_multiplefile.log)
- [selc_32_16777216_1048576_sorted.log](https://issues.apache.org/jira/secure/attachment/12905700/selc_32_16777216_1048576_sorted.log)
**Note**: *This issue was originally created as [PARQUET-1192](https://issues.apache.org/jira/browse/PARQUET-1192). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia esaminando i log allegati per le esecuzioni con un singolo file e con più file, quindi riproduci la query con l’ambiente indicato, composto da Hadoop 2.7.0, Pig 0.17.0 e Parquet 1.9.0. Confronta i byte letti riportati con le impostazioni dei row group e delle pagine di dati. Il lavoro è completato quando viene spiegata la differenza e viene determinato se il comportamento delle statistiche o del predicate pushdown indica un bug confermato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- data-engineering
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100