{"push_id":796897334,"size":4,"distinct_size":4,"ref":"refs/heads/IMPALA-2020","head":"8a18e0cf160787ca23a4ccebaf80e916af92e221","before":"8d27d1b9f11f81419903849c6fd234e8898ba023","commits":[{"sha":"d1fcb673bf52ae439c592156cb7678ce9903815c","author":{"email":"d1d1e60202ec9f2503deb1b724986485a125d802@cloudera.com","name":"ishaan"},"message":"Remove cdh5.5.0-SNAPSHOT Hadoop/HBase/Hive/LLAMA/Sentry dependencies.\n\nChange-Id: I168b829980125ee8facb32d74d276234cf4006e4","distinct":true,"url":"https://api.github.com/repos/cchanning/Impala/commits/d1fcb673bf52ae439c592156cb7678ce9903815c"},{"sha":"8d743e8be6f541a129c2fcbab8d619b66c868b39","author":{"email":"d1d1e60202ec9f2503deb1b724986485a125d802@cloudera.com","name":"ishaan"},"message":"Add cdh5.7.0-SNAPSHOT Hadoop/HBase/Hive/LLAMA/Sentry dependencies.\n\nChange-Id: Ifda9939b7ad035b9877d75fbedbeb15cfa7ce517","distinct":true,"url":"https://api.github.com/repos/cchanning/Impala/commits/8d743e8be6f541a129c2fcbab8d619b66c868b39"},{"sha":"b572bcea1fcf665d3bebad44096c1f3f9bb4f6bd","author":{"email":"d1d1e60202ec9f2503deb1b724986485a125d802@cloudera.com","name":"ishaan"},"message":"Revert expected output for file size in nested planner tests.\n\nPreviously, a patch changed the expected file sizes for nested planner test because of a\nchange in the underlying thirdparty bits in cdh5.5.0. However, this is not reflected in\ntrunk, so this patch reverts those changes.\n\nChange-Id: I650f6a8415e20508a926e029d8df78523d830eb2","distinct":true,"url":"https://api.github.com/repos/cchanning/Impala/commits/b572bcea1fcf665d3bebad44096c1f3f9bb4f6bd"},{"sha":"8a18e0cf160787ca23a4ccebaf80e916af92e221","author":{"email":"f8249166ebee57207c05257bc9491ced177037e5@cloudera.com","name":"Christopher Channing"},"message":"IMPALA-2020: Support implicit rounding of decimals when casting between types.\n\nThis patch introduces a new query option called “DECIMAL_ROUND_MODE” which defines\ntwo states: [0 = TRUNCATE, 1 = ROUND].  In “ROUND” mode, Impala considers the value\nof the next digit to the right of the round boundary when making rounding decisions.\nIf this digit is >= 5 then an upward round will occur. The casting behaviour is modeled\non what Oracle’s RDBMS currently provides.\n\nA list of the type conversions handled are:\n\nDouble -> Decimal(P,S)\nFloat -> Decimal(P,S)\nString -> Decimal(P,S)\nDecimal(P,S) -> [String, Decimal(P2,S2) | Double | TinyInt | SmallInt | Int | BigInt]\nDecimal(P,S) -> VarChar(L):  When DECIMAL_ROUND_MODE is set to ROUND, the length of the\nvarchar is used as the round boundary. A leading zero will be suppressed in favour of\nshowing more digits when there is a constraint on space (which is determined by the\nlength of the varchar). For example:\n\n    cast(cast(-0.73761 as decimal(5, 5)) as varchar(5)) = \"-.738\"\n\nChange-Id: If757cfc4eb1086734f98386df7d42c4f188433b1","distinct":true,"url":"https://api.github.com/repos/cchanning/Impala/commits/8a18e0cf160787ca23a4ccebaf80e916af92e221"}]}