Re: SparkSQL operator priority

2014-07-19 Thread Eric Friedman
Can position be null? Looks like there may be constraints with predicate push down in that case. https://github.com/apache/spark/pull/511/ On Jul 18, 2014, at 8:04 PM, Christos Kozanitis kozani...@berkeley.edu wrote: Hello What is the order with which SparkSQL deserializes parquet

Re: SparkSQL operator priority

2014-07-19 Thread Christos Kozanitis
Thanks Eric. That is the case as most of my fields are optional. So it seems that the problem comes from Parquet. On Sat, Jul 19, 2014 at 8:27 AM, Eric Friedman eric.d.fried...@gmail.com wrote: Can position be null? Looks like there may be constraints with predicate push down in that case.

SparkSQL operator priority

2014-07-18 Thread Christos Kozanitis
Hello What is the order with which SparkSQL deserializes parquet fields? Is it possible to modify it? I am using SparkSQL to query a parquet file that consists of a lot of fields (around 30 or so). Let me call an example table MyTable and let's suppose the name of one of its fields is position.