IMPALA-177 not fixed in 1.0.1?

On Mon, Jun 10, 2013 at 9:13 PM, Grisha Trubetskoy wrote:


Is there any way to check whether
https://issues.cloudera.org/browse/IMPALA-177 is fixed in 1.0.1?

I'm getting an LZO error as described in it for a table that contains a
file larger than 2GB... Or have I stumbled upon a different bug?

Thanks!

Grisha

On Mon, Jun 10, 2013 at 9:49 PM, Gregory Trubetskoy wrote:

This is slightly modified to obscure our internal details:

Backend 4:No block index for hdfs://<snip>/part-m-00000.lzo after offset:
2684354560
No block index for hdfs://i<snip>/part-m-00000.lzo after offset: 2684354560
Backend 5:No block index for hdfs://<snip>/part-m-00000.lzo after offset:
1879048192
No block index for hdfs://<snip>/part-m-00000.lzo after offset: 1879048192
Backend 6:No block index for hdfs://<snip>/part-m-00000.lzo after offset:
2147483648
No block index for hdfs://<snip>/part-m-00000.lzo after offset: 2147483648

The query is a simple select count(*). It works in Hive. Deleting the
*.index files fixes the Impala problem. The size of the part-m-00000.lzo is
2882773633 bytes, 2GB appears to be what triggers it.

On Tue, Jun 11, 2013 at 5:20 PM, Nong Li wrote:

This looks like a different issue. Can you attach the .index file for one
of the lzo files?


On Mon, Jun 10, 2013 at 9:49 PM, Gregory Trubetskoy <
grisha.trubetskoy@livingsocial.com> wrote:

On Tue, Jun 11, 2013 at 3:54 PM, Gregory Trubetskoy wrote:

Just sent it directly to your email, thx!