{"push_id":1281478973,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"fa6e47616e818f33d8d4774ce43ae6d62cdd59bd","before":"5e524d146c556b1f2ef6da6f8d9a6dbb6b8cea73","commits":[{"sha":"fa6e47616e818f33d8d4774ce43ae6d62cdd59bd","author":{"name":"Wes McKinney","email":"7af4275bc910f83fd113585f67f9fee33751d10a@twosigma.com"},"message":"PARQUET-676: Fix incorrect MaxBufferSize for small bit widths\n\nThis function was implemented incorrectly in the original source code from Impala. The bug never presented itself because Impala allocates a much larger buffer than is required for the data page rather than using the `MaxBufferSize` value.\n\nIn a worst case scenario, the RleEncoder can result in a concatenation of short RLE runs of 8 values (the minimum for RLE). For example:\n\n0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 ...\n\nIn encoded form, each RLE run occupies 2 bytes (for bit width 1). Thus 1024 values with this structure and bit width 1, at least 256 bytes are required to fully encode. If these were encoded as all literal runs, you can encode up to 504 values in a literal run (plus the indicator byte). Thus, in the same case (bit width 1) only\n\n(504 + 504 + 16)\n64 + 64 + 3 = 131\n\nbytes are required. This should also fix PARQUET-698.\n\nAuthor: Wes McKinney <wes.mckinney@twosigma.com>\n\nCloses #150 from wesm/PARQUET-676 and squashes the following commits:\n\n6ca44a8 [Wes McKinney] clang-format\ne48b0bf [Wes McKinney] Fix maximum buffer sizing for hybrid RLE encoding case where short RLE runs use more space than mostly literal runs","distinct":true,"url":"https://api.github.com/repos/apache/parquet-cpp/commits/fa6e47616e818f33d8d4774ce43ae6d62cdd59bd"}]}
{"actor":{"display_login":"asfgit"}}