ORC-135: PPD for timestamp is wrong when reader and writer timezones are different

[prasanthj]

When reader and writer timezones are different, PPD evaluation does not offset the timezone when reading the min and max values. This can result is wrong PPD evaluation and hence incorrect results.

Example:
Table written in US/Eastern timezone. All values in this table are "2007-08-01 00:00:00.0".
PPD disabled

hive> set hive.optimize.index.filter=false;
hive> select ORDER_DATE from ORDER_FACT_small where ORDER_DATE='2007-08-01 00:00:00.0' limit 1;
2007-08-01 00:00:00.0
OK

PPD enabled

set hive.optimize.index.filter=true;
select ORDER_DATE from ORDER_FACT_small where ORDER_DATE='2007-08-01 00:00:00.0' limit 1;
OK

No rows are returned when PPD is enabled (reader timezone is UTC)

[prasanthj]

These imports are not required. Will remove it in the next patch.

[omalley]

Ok, I took a pass at this:

https://github.com/omalley/orc/tree/orc-135

Changes:

• Block all use of PPD on timestamps from before ORC-135.
• Block PPD on timestamp with numeric constraints
• TimestampColumnStatistics.getMinimum and getMaximum return Timestamps in the local timezone.
• Loading old TimestampColumnStatistics loads the min and max assuming local timezone.
• Add utilities to SerializationUtils for conversion to and from utc.
• Make BloomFilter.encoding an int so that we can detect future values.
• Future BloomFilter encodings are not used.
• Some more test cases