Isilon: don't warn for multiple remote parquet blocks
Isilon: don't warn for multiple remote parquet blocks

If we weren't able to assign a block to a local impalad, then it may be
that the HDFS is actually Isilon (where all scan ranges are remote).  On
Isilon, HDFS block size is a global value (rather than per-file) and so
it can be somewhat common for files to be split across blocks.  However,
HDFS block size has no meaning in terms of data locality on that system,
so the warning is spurious.

When running against "native" HDFS, blocks should usually be assignable
to a local node so suppressing the warning for the above case shouldn't
have much impact for "native" HDFS.

Change-Id: I43172e4386658e48729c5de5e4985e807d30db4d
Reviewed-on: http://gerrit.cloudera.org:8080/371
Reviewed-by: Dan Hecht <20ebd99959f0f6e5dcb0fc319b4d8ef53a16b5fb@cloudera.com>
Tested-by: Internal Jenkins

cloudera/recordservice,cloudera/recordservice,cloudera/recordservice,cloudera/recordservice,cloudera/recordservice,cloudera/recordservice,cloudera/recordservice