title: Does partition filter order has significant performance impact on spark read
body: <p>Example :  table XXXX is partition by column1 and column2</p>
  <pre><code>           reading table XXXX by where clause Column1 and column2
             option 1: select xxxx where column1 =&quot;&quot; and column2 =&quot;&quot;
             option 2: select xxxx where column2 =&quot;&quot; and column1 =&quot;&quot;
            
     does option 1 and option 2 has different read performance because of filter order and table partitionBy column1 and column2?
  
  i have checked DAG for both case which is having partitionFilter in filescan.
  
  question is 
  option1 : where(column1 =&quot;&quot; and column2 =&quot;&quot;)
  option 2: where(column2 =&quot;&quot; and column1 =&quot;&quot; ) 
  does it have differenet read performance beacuse of table patition by column1, column2?
  </code></pre>