date:20171214

[jira] [Created] (IMPALA-6326) segfault during impyla HiveServer2Cursor.cancel_operation() over SSL

2017-12-14 Thread Matthew Mulder (JIRA)

Matthew Mulder created IMPALA-6326:
--

 Summary: segfault during impyla 
HiveServer2Cursor.cancel_operation() over SSL
 Key: IMPALA-6326
 URL: https://issues.apache.org/jira/browse/IMPALA-6326
 Project: IMPALA
  Issue Type: Bug
  Components: Clients
Affects Versions: Impala 2.11.0
Reporter: Matthew Mulder
Priority: Minor


During a stress test on a secure cluster one of the clients crashed in 
HiveServer2Cursor.cancel_operation().

The stress test debug log shows{code}2017-12-13 16:50:52,624 21607 Query 
Consumer DEBUG:concurrent_select[579]:Requesting memory reservation
2017-12-13 16:50:52,624 21607 Query Consumer 
DEBUG:concurrent_select[245]:Reserved 102 MB; 1455 MB available; 95180 MB 
overcommitted
2017-12-13 16:50:52,625 21607 Query Consumer 
DEBUG:concurrent_select[581]:Received memory reservation
2017-12-13 16:50:52,658 21607 Query Consumer DEBUG:concurrent_select[865]:Using 
tpcds_300_decimal_parquet database
2017-12-13 16:50:52,658 21607 Query Consumer DEBUG:db_connection[203]:IMPALA: 
USE tpcds_300_decimal_parquet
2017-12-13 16:50:52,825 21607 Query Consumer DEBUG:db_connection[203]:IMPALA: 
SET ABORT_ON_ERROR=1
2017-12-13 16:50:53,060 21607 Query Consumer 
DEBUG:concurrent_select[877]:Setting mem limit to 102 MB
2017-12-13 16:50:53,060 21607 Query Consumer DEBUG:db_connection[203]:IMPALA: 
SET MEM_LIMIT=102M
2017-12-13 16:50:53,370 21607 Query Consumer 
DEBUG:concurrent_select[881]:Running query with 102 MB mem limit at 
vc0704.halxg.cloudera.com with timeout secs 52:
select
  dt.d_year,
  item.i_category_id,
  item.i_category,
  sum(ss_ext_sales_price)
from
  date_dim dt,
  store_sales,
  item
where
  dt.d_date_sk = store_sales.ss_sold_date_sk
  and store_sales.ss_item_sk = item.i_item_sk
  and item.i_manager_id = 1
  and dt.d_moy = 11
  and dt.d_year = 2000
group by
  dt.d_year,
  item.i_category_id,
  item.i_category
order by
  sum(ss_ext_sales_price) desc,
  dt.d_year,
  item.i_category_id,
  item.i_category
limit 100;

2017-12-13 16:51:08,491 21607 Query Consumer DEBUG:concurrent_select[889]:Query 
id is b6425b84aa45f633:9ce7cad9
2017-12-13 16:51:15,337 21607 Query Consumer 
DEBUG:concurrent_select[900]:Waiting for query to execute
2017-12-13 16:51:22,316 21607 Query Consumer 
DEBUG:concurrent_select[900]:Waiting for query to execute
2017-12-13 16:51:27,266 21607 Fetch Results b6425b84aa45f633:9ce7cad9 
DEBUG:concurrent_select[1009]:Fetching result for query with id 
b6425b84aa45f633:9ce7cad9
2017-12-13 16:51:44,625 21607 Query Consumer 
DEBUG:concurrent_select[940]:Attempting cancellation of query with id 
b6425b84aa45f633:9ce7cad9
2017-12-13 16:51:44,627 21607 Query Consumer INFO:hiveserver2[259]:Canceling 
active operation{code}The impalad log shows{code}I1213 16:50:54.287511 136399 
admission-controller.cc:510] Schedule for id=b6425b84aa45f633:9ce7cad9 
in pool_name=root.systest cluster_mem_needed=816.00 MB PoolConfig: 
max_requests=-1 max_queued=200 max_mem=-1.00 B
I1213 16:50:54.289767 136399 admission-controller.cc:515] Stats: 
agg_num_running=184, agg_num_queued=0, agg_mem_reserved=1529.63 GB,  
local_host(local_mem_admitted=132.02 GB, num_admitted_running=21, num_queued=0, 
backend_mem_reserved=194.58 GB)
I1213 16:50:54.291550 136399 admission-controller.cc:531] Admitted query 
id=b6425b84aa45f633:9ce7cad9
I1213 16:50:54.296922 136399 coordinator.cc:99] Exec() 
query_id=b6425b84aa45f633:9ce7cad9 stmt=/* Mem: 102 MB. Coordinator: 
vc0704.halxg.cloudera.com. */
select
  dt.d_year,
  item.i_category_id,
  item.i_category,
  sum(ss_ext_sales_price)
from
  date_dim dt,
  store_sales,
  item
where
  dt.d_date_sk = store_sales.ss_sold_date_sk
  and store_sales.ss_item_sk = item.i_item_sk
  and item.i_manager_id = 1
  and dt.d_moy = 11
  and dt.d_year = 2000
group by
  dt.d_year,
  item.i_category_id,
  item.i_category
order by
  sum(ss_ext_sales_price) desc,
  dt.d_year,
  item.i_category_id,
  item.i_category
limit 100;
I1213 16:50:59.263310 136399 query-state.cc:151] Using query memory limit from 
query options: 102.00 MB
I1213 16:50:59.267033 136399 mem-tracker.cc:189] Using query memory limit: 
102.00 MB
I1213 16:50:59.272271 136399 coordinator.cc:357] starting execution on 8 
backends for query b6425b84aa45f633:9ce7cad9
I1213 16:51:07.525143 136399 coordinator.cc:370] started execution on 8 
backends for query b6425b84aa45f633:9ce7cad9
I1213 16:51:08.358772 136399 impala-hs2-server.cc:490] ExecuteStatement(): 
return_val=TExecuteStatementResp {
  01: status (struct) = TStatus {
01: statusCode (i32) = 0,
  },
  02: operationHandle (struct) = TOperationHandle {
01: operationId (struct) = THandleIdentifier {
  01: guid (string) = 
"3\xf6E\xaa\x84[B\xb6\x00\x00\x00\x00\xd9\xca\xe7\x9c",
  02: secret (string) =

[jira] [Created] (IMPALA-6325) Improve Query Kudu Table Error msg

2017-12-14 Thread yyzzjj (JIRA)

yyzzjj created IMPALA-6325:
--

 Summary: Improve  Query Kudu Table Error msg  
 Key: IMPALA-6325
 URL: https://issues.apache.org/jira/browse/IMPALA-6325
 Project: IMPALA
  Issue Type: Improvement
  Components: Backend, Clients
Affects Versions: Impala 2.10.0, Impala 2.11.0
Reporter: yyzzjj


like 
  Status: Unable to create Kudu client: Network error: Could not determine 
local host names: Unable to lookup FQDN: 成功 (error 0)

should contain  query which table report error  

if sql have many kudu table  should test everyone 
  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IMPALA-6324) Support reading RLE-encoded boolean values in Parquet scanner

2017-12-14 Thread Tim Armstrong (JIRA)

Tim Armstrong created IMPALA-6324:
-

 Summary: Support reading RLE-encoded boolean values in Parquet 
scanner
 Key: IMPALA-6324
 URL: https://issues.apache.org/jira/browse/IMPALA-6324
 Project: IMPALA
  Issue Type: Improvement
  Components: Backend
Reporter: Tim Armstrong


Per this discussion on the Parquet mailing list, RLE will become a valid 
encoding for the boolean type in parquet. We should add support for reading 
this.

https://mail-archives.apache.org/mod_mbox/parquet-dev/201712.mbox/%3CCAJPUwMDbGgkS1WmN8OvuuA%3DQ%2BXd%2BOwLn2XZAu7CNGF1sMVZMJg%40mail.gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IMPALA-6322) Group by expression fails when expression includes a CAST

2017-12-14 Thread N Campbell (JIRA)

N Campbell created IMPALA-6322:
--

 Summary: Group by expression fails when expression includes a CAST
 Key: IMPALA-6322
 URL: https://issues.apache.org/jira/browse/IMPALA-6322
 Project: IMPALA
  Issue Type: Bug
  Components: Backend
Affects Versions: Impala 2.9.0
Reporter: N Campbell


Impala 2.5 thru 2.9 will fail to execute a Group by when it includes an 
expression which also includes a includes CAST.

*Fails*
SELECT
`sno` AS `SNO`, 
upper( cast(`pno` as varchar(32)) ) AS `PNO`
FROM
`cert`.`tsupply` 
GROUP BY 
`sno`, 
upper ( cast(`pno` as varchar(32)) )

Error: [Simba][ImpalaJDBCDriver](500051) ERROR processing query/statement. 
Error Code: 0, SQL state: TStatus(statusCode:ERROR_STATUS, sqlState:HY000, 
errorMessage:AnalysisException: select list expression not produced by 
aggregation output (missing from GROUP BY clause?): upper(CAST(pno AS 
VARCHAR(32)))
), Query: SELECT
`sno` AS `SNO`, 
upper( cast(`pno` as varchar(32)) ) AS `PNO`
FROM
`cert`.`tsupply` 
GROUP BY 
`sno`, 
upper ( cast(`pno` as varchar(32)) ).
SQLState:  HY000
ErrorCode: 500051

*Works*

SELECT
`sno` AS `SNO`, 
upper(pno) AS `PNO`
FROM
`cert`.`tsupply` 
GROUP BY 
`sno`, 
upper(pno)

SELECT distinct
`sno` AS `SNO`, 
upper( cast(`pno` as varchar(32)) ) AS `PNO`
FROM
`cert`.`tsupply` 

select `SNO`, `PNO` from (
SELECT
`sno` AS `SNO`, 
upper( cast(`pno` as varchar(32)) ) AS `PNO`
FROM `cert`.`tsupply` 
) T
GROUP BY 
`SNO`,
   `PNO`




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IMPALA-6321) there is a mistake about 'MaterializeTupleTime' for kudu

2017-12-14 Thread HeLifu (JIRA)

HeLifu created IMPALA-6321:
--

 Summary: there is a mistake about 'MaterializeTupleTime' for kudu
 Key: IMPALA-6321
 URL: https://issues.apache.org/jira/browse/IMPALA-6321
 Project: IMPALA
  Issue Type: Bug
  Components: Backend
Affects Versions: Impala 2.9.0
Reporter: HeLifu


hi, 
i find that the 'MaterializeTupleTime' for kuduScanner is very different from 
hdfsScanner while reading impala's profile.
in 'class HdfsParquetScanner' there is a timer named 
'ScopedTimer assemble_rows_timer_', but in 'class 
KuduScanner' there is not.
maybe we need to add the timer for kuduScanner, just like hdfsScanner does.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IMPALA-6326) segfault during impyla HiveServer2Cursor.cancel_operation() over SSL

[jira] [Created] (IMPALA-6325) Improve Query Kudu Table Error msg

[jira] [Created] (IMPALA-6324) Support reading RLE-encoded boolean values in Parquet scanner

[jira] [Created] (IMPALA-6322) Group by expression fails when expression includes a CAST

[jira] [Created] (IMPALA-6321) there is a mistake about 'MaterializeTupleTime' for kudu

5 matches

Site Navigation

Mail list logo

Footer information