Cardinality of filter Optimization

.mailmap

@@ -0,0 +1,25 @@
+<akpall@fb.com> <iosakshay@gmail.com>
+<atavory@fb.com> <atavory@gmail.com>
+<andriirosa@fb.com> <andriyrosa@gmail.com>
+<hluo@twitter.com> <luohao@users.noreply.github.com>
+<grzegorz@starburstdata.com> <kokosing@users.noreply.github.com>
+<karol.sobczak@karolsobczak.com> <napewnotrafi@gmail.com>
+<ke1024@fb.com> <50636602+kewang1024@users.noreply.github.com>
+<piotr.findeisen@gmail.com> <findepi@users.noreply.github.com>
+<rschlussel@fb.com> <34256034+rschlussel2@users.noreply.github.com>
+<rschlussel@fb.com> <34256034+rschlussel@users.noreply.github.com>
+<rongrong@fb.com> <rongrong100@gmail.com>
+<shengpei@fb.com> <szhang29@ncsu.edu>
+<tdm@fb.com> <tim@timdmeehan.com>
+<vgajjala@fb.com> <varungajjala@users.noreply.github.com>
+<vzhang@fb.com> <6372365+viczhang861@users.noreply.github.com>
+<vzhang@fb.com> <picrinite@users.noreply.github.com>
+<wxie@fb.com> <wenlei.xie@gmail.com>
+<wxie@fb.com> <wenleix@users.noreply.github.com>
+<heyi@fb.com> <hellium01@users.noreply.github.com>
+<zluo@twitter.com> <rooservelt.luo@gmail.com>
+<ccayiroglu@fb.com> <cayiroglu@gmail.com>
+<yingsu@fb.com> <33299678+yingsu00@users.noreply.github.com>
+<ggreg@fb.com> <ggregl@gmail.com>
+<rongrong@fb.com> <rongrong100@gmail.com>
+<aweisberg@fb.com> <ariel@weisberg.ws>

.travis.yml

@@ -2,7 +2,7 @@ language: java
 
 env:
   global:
-    - MAVEN_OPTS="-Xmx512M -XX:+ExitOnOutOfMemoryError"
+    - MAVEN_OPTS="-Xmx1024M -XX:+ExitOnOutOfMemoryError"
     - MAVEN_SKIP_CHECKS_AND_DOCS="-Dair.check.skip-all=true -Dmaven.javadoc.skip=true"
     - MAVEN_FAST_INSTALL="-DskipTests $MAVEN_SKIP_CHECKS_AND_DOCS -B -q -T C1"
     - ARTIFACTS_UPLOAD_PATH_BRANCH=travis_build_artifacts/${TRAVIS_REPO_SLUG}/${TRAVIS_BRANCH}/${TRAVIS_BUILD_NUMBER}
@@ -19,6 +19,10 @@ env:
     - TEST_SPECIFIC_MODULES=presto-hive
     - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-materialized"
     - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-recoverable-grouped-execution"
+    - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-pushdown-filter-queries-basic"
+    - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-pushdown-filter-queries-advanced" 
+    - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-repartitioning"
+    - TEST_SPECIFIC_MODULES=presto-hive TEST_FLAGS="-P test-hive-parquet"
     - TEST_SPECIFIC_MODULES=presto-main
     - TEST_SPECIFIC_MODULES=presto-mongodb
     - TEST_OTHER_MODULES=!presto-tests,!presto-raptor,!presto-accumulo,!presto-cassandra,!presto-hive,!presto-kudu,!presto-docs,!presto-server,!presto-server-rpm,!presto-main,!presto-mongodb

CONTRIBUTING.md

@@ -2,9 +2,7 @@
 
 ## Contributor License Agreement ("CLA")
 
-In order to accept your pull request, we need you to submit a CLA. You only need to do this once, so if you've done this for another Facebook open source project, you're good to go. If you are submitting a pull request for the first time, just let us know that you have completed the CLA and we can cross-check with your GitHub username.
-
-Complete your CLA here: <https://code.facebook.com/cla>
+In order to accept your pull request, we need you to submit a CLA. You only need to do this once, so if you've done this for one repository in the [prestodb](https://github.com/prestodb) organization, you're good to go. If you are submitting a pull request for the first time, the communitybridge-easycla bot will notify you if you haven't signed, and will provide you with a link.  If you are contributing on behalf of a company, you might want to let the person who manages your corporate CLA whitelist know they will be receiving a request from you.
 
 ## License
 

README.md

@@ -103,26 +103,5 @@ To iterate quickly, simply re-build the project in IntelliJ after packaging is c
 
 ## Release Notes
 
-When authoring a pull request, the PR description should include relevant release notes.
-
-The release notes should be placed at the bottom of PR description. The format of the section will be:
-
-```
-== RELEASE NOTES ==
-
-General Changes
-* ...
-* ...
-
-Hive Changes
-* ...
-* ...
-```
-
-Long line items can be wrapped without leading asterisk (*). White-spacing and capitalization are flexible.
-
-If the pull request does not have a user-facing impact and thus a release note is not required. Place the following line at the bottom of the PR description:
-
-```
-== NO RELEASE NOTE ==
-```
+When authoring a pull request, the PR description should include its relevant release notes.
+Follow [Release Notes Guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines) when authoring release notes.