Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Duplicate
-
Impala 1.1.1
-
None
Description
In the impala-shell, the default value of HBASE_CACHING is shown as 0, when in fact it's 1000 (I think).
[my-impala-daemon:21000] > SET;
Default query options:
ABORT_ON_DEFAULT_LIMIT_EXCEEDED: 0
ABORT_ON_ERROR: 0
ALLOW_UNSUPPORTED_FORMATS: 0
BATCH_SIZE: 0
DEBUG_ACTION:
DEFAULT_ORDER_BY_LIMIT: -1
DISABLE_CODEGEN: 0
HBASE_CACHE_BLOCKS: 0
HBASE_CACHING: 0 <--
MAX_ERRORS: 0
MAX_IO_BUFFERS: 0
MAX_SCAN_RANGE_LENGTH: 0
MEM_LIMIT: 0
NUM_NODES: 0
NUM_SCANNER_THREADS: 0
PARQUET_COMPRESSION_CODEC: SNAPPY
SUPPORT_START_OVER: false
This can be pretty confusing since it's implicitly using a different value. In my case, it was reading my HBase table which has very wide rows, and it was causing the region servers to fall over.
Attachments
Issue Links
- duplicates
-
IMPALA-5589 set; shows invalid values for unset query options
- Resolved