from:"Prasad Nagaraj Subramanya \(JIRA\)"

[jira] [Resolved] (DRILL-5998) Queue information of queries which fail due to queue time out not shown

2018-01-22 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya resolved DRILL-5998.
--
Resolution: Cannot Reproduce

> Queue information of queries which fail due to queue time out not shown
> ---
>
> Key: DRILL-5998
> URL: https://issues.apache.org/jira/browse/DRILL-5998
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Client - HTTP
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>Priority: Major
>
> When a query fails because of queue time out, the queue information is not 
> shown in the web UI



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (DRILL-6066) AssertionError: Internal error: Conversion to relational algebra failed to preserve datatypes: validated type

2018-01-15 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-6066:
-
Affects Version/s: (was: 1.13.0)

> AssertionError: Internal error: Conversion to relational algebra failed to 
> preserve datatypes: validated type
> -
>
> Key: DRILL-6066
> URL: https://issues.apache.org/jira/browse/DRILL-6066
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Query Planning  Optimization
>Reporter: Prasad Nagaraj Subramanya
>Priority: Major
>
> Query -
> framework/resources/Datasources/limit0/aggregates/tpcds_variants/parquet/create_tpcdsVariants_views.sh
> {code}
> create or replace view `dfs.tpcds_sf1_parquet`.store_v as select 
> cast( s_store_sk as integer)  as s_store_sk, 
> cast( s_store_id as varchar(200))  as s_store_id, 
> cast( s_rec_start_date as date)  as s_rec_start_date, 
> cast( s_rec__date as date)  as s_rec__date, 
> cast( s_closed_date_sk as integer)  as s_closed_date_sk, 
> cast( s_store_name as varchar(200))  as s_store_name, 
> cast( s_number_employees as integer)  as s_number_employees, 
> cast( s_floor_space as integer)  as s_floor_space, 
> cast( s_hours as varchar(200))  as s_hours, 
> cast( s_manager as varchar(200))  as s_manager, 
> cast( s_market_id as integer)  as s_market_id, 
> cast( s_geography_class as varchar(200))  as s_geography_class, 
> cast( s_market_desc as varchar(200))  as s_market_desc, 
> cast( s_market_manager as varchar(200))  as s_market_manager, 
> cast( s_division_id as integer)  as s_division_id, 
> cast( s_division_name as varchar(200))  as s_division_name, 
> cast( s_company_id as integer)  as s_company_id, 
> cast( s_company_name as varchar(200))  as s_company_name, 
> cast( s_street_number as varchar(200))  as s_street_number, 
> cast( s_street_name as varchar(200))  as s_street_name, 
> cast( s_street_type as varchar(200))  as s_street_type, 
> cast( s_suite_number as varchar(200))  as s_suite_number, 
> cast( s_city as varchar(200))  as s_city, 
> cast( s_county as varchar(200))  as s_county, 
> cast( s_state as varchar(200))  as s_state, 
> cast( s_zip as varchar(200))  as s_zip, 
> cast( s_country as varchar(200))  as s_country, 
> cast( s_gmt_offset as double)  as s_gmt_offset, 
> cast( s_tax_precentage as double)  as s_tax_precentage 
> from dfs.`/drill/testdata/tpcds_sf1/parquet/store`;
> {code}
> ERROR -
> {code}
> Error: SYSTEM ERROR: AssertionError: Internal error: Conversion to relational 
> algebra failed to preserve datatypes:
> validated type:
> RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "ISO-8859-1" 
> COLLATE "ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE 
> s_rec__date, INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET 
> "ISO-8859-1" COLLATE "ISO-8859-1$en_US$primary" s_store_name, INTEGER 
> s_number_employees, INTEGER s_floor_space, VARCHAR(200) CHARACTER SET 
> "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_hours, VARCHAR(200) CHARACTER 
> SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_manager, INTEGER 
> s_market_id, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
> "ISO-8859-1$en_US$primary" s_geography_class, VARCHAR(200) CHARACTER SET 
> "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_market_desc, VARCHAR(200) 
> CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_market_manager, 
> INTEGER s_division_id, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
> "ISO-8859-1$en_US$primary" s_division_name, INTEGER s_company_id, 
> VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
> s_company_name, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
> "ISO-8859-1$en_US$primary" s_street_number, VARCHAR(200) CHARACTER SET 
> "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_name, VARCHAR(200) 
> CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_type, 
> VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
> s_suite_number, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
> "ISO-8859-1$en_US$primary" s_city, VARCHAR(200) CHARACTER SET "UTF-16LE" 
> COLLATE "ISO-8859-1$en_US$primary" s_county, VARCHAR(200) CHARACTER SET 
> "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_state, VARCHAR(200) CHARACTER 
> SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_zip, VARCHAR(200) 
> CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_country, DOUBLE 
> s_gmt_offset, DOUBLE s_tax_precentage) NOT NULL
> converted type:
> RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
> "ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE 
> s_rec__date, INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" 
> COLLATE "ISO-8859-1$en_US$primary"

[jira] [Updated] (DRILL-6066) AssertionError: Internal error: Conversion to relational algebra failed to preserve datatypes: validated type

2018-01-13 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-6066:
-
Description: 
Query -
framework/resources/Datasources/limit0/aggregates/tpcds_variants/parquet/create_tpcdsVariants_views.sh
{code}
create or replace view `dfs.tpcds_sf1_parquet`.store_v as select 
cast( s_store_sk as integer)  as s_store_sk, 
cast( s_store_id as varchar(200))  as s_store_id, 
cast( s_rec_start_date as date)  as s_rec_start_date, 
cast( s_rec__date as date)  as s_rec__date, 
cast( s_closed_date_sk as integer)  as s_closed_date_sk, 
cast( s_store_name as varchar(200))  as s_store_name, 
cast( s_number_employees as integer)  as s_number_employees, 
cast( s_floor_space as integer)  as s_floor_space, 
cast( s_hours as varchar(200))  as s_hours, 
cast( s_manager as varchar(200))  as s_manager, 
cast( s_market_id as integer)  as s_market_id, 
cast( s_geography_class as varchar(200))  as s_geography_class, 
cast( s_market_desc as varchar(200))  as s_market_desc, 
cast( s_market_manager as varchar(200))  as s_market_manager, 
cast( s_division_id as integer)  as s_division_id, 
cast( s_division_name as varchar(200))  as s_division_name, 
cast( s_company_id as integer)  as s_company_id, 
cast( s_company_name as varchar(200))  as s_company_name, 
cast( s_street_number as varchar(200))  as s_street_number, 
cast( s_street_name as varchar(200))  as s_street_name, 
cast( s_street_type as varchar(200))  as s_street_type, 
cast( s_suite_number as varchar(200))  as s_suite_number, 
cast( s_city as varchar(200))  as s_city, 
cast( s_county as varchar(200))  as s_county, 
cast( s_state as varchar(200))  as s_state, 
cast( s_zip as varchar(200))  as s_zip, 
cast( s_country as varchar(200))  as s_country, 
cast( s_gmt_offset as double)  as s_gmt_offset, 
cast( s_tax_precentage as double)  as s_tax_precentage 
from dfs.`/drill/testdata/tpcds_sf1/parquet/store`;
{code}

ERROR -
{code}
Error: SYSTEM ERROR: AssertionError: Internal error: Conversion to relational 
algebra failed to preserve datatypes:
validated type:
RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "ISO-8859-1" COLLATE 
"ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE s_rec__date, 
INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET "ISO-8859-1" COLLATE 
"ISO-8859-1$en_US$primary" s_store_name, INTEGER s_number_employees, INTEGER 
s_floor_space, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_hours, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_manager, INTEGER s_market_id, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_geography_class, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_market_desc, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_market_manager, INTEGER s_division_id, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_division_name, INTEGER s_company_id, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_company_name, VARCHAR(200) CHARACTER SET 
"UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_number, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_name, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_street_type, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_suite_number, VARCHAR(200) CHARACTER SET 
"UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_city, VARCHAR(200) CHARACTER 
SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_county, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_state, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_zip, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_country, DOUBLE s_gmt_offset, DOUBLE s_tax_precentage) NOT NULL
converted type:
RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE s_rec__date, 
INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_store_name, INTEGER s_number_employees, INTEGER 
s_floor_space, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_hours, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_manager, INTEGER s_market_id, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_geography_class, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_market_desc, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_market_manager, INTEGER s_division_id, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_division_name, INTEGER s_company_id, VARCHAR(200) CHARACTER SET "UTF-16LE"

[jira] [Created] (DRILL-6066) AssertionError: Internal error: Conversion to relational algebra failed to preserve datatypes: validated type

2018-01-02 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-6066:


 Summary: AssertionError: Internal error: Conversion to relational 
algebra failed to preserve datatypes: validated type
 Key: DRILL-6066
 URL: https://issues.apache.org/jira/browse/DRILL-6066
 Project: Apache Drill
  Issue Type: Bug
  Components: Query Planning & Optimization
Affects Versions: 1.13.0
Reporter: Prasad Nagaraj Subramanya


Query -
framework/resources/Datasources/limit0/aggregates/tpcds_variants/parquet/create_tpcdsVariants_views.sh
{code}
create or replace view `dfs.tpcds_sf1_parquet`.store_v as select 
cast( s_store_sk as integer)  as s_store_sk, 
cast( s_store_id as varchar(200))  as s_store_id, 
cast( s_rec_start_date as date)  as s_rec_start_date, 
cast( s_rec__date as date)  as s_rec__date, 
cast( s_closed_date_sk as integer)  as s_closed_date_sk, 
cast( s_store_name as varchar(200))  as s_store_name, 
cast( s_number_employees as integer)  as s_number_employees, 
cast( s_floor_space as integer)  as s_floor_space, 
cast( s_hours as varchar(200))  as s_hours, 
cast( s_manager as varchar(200))  as s_manager, 
cast( s_market_id as integer)  as s_market_id, 
cast( s_geography_class as varchar(200))  as s_geography_class, 
cast( s_market_desc as varchar(200))  as s_market_desc, 
cast( s_market_manager as varchar(200))  as s_market_manager, 
cast( s_division_id as integer)  as s_division_id, 
cast( s_division_name as varchar(200))  as s_division_name, 
cast( s_company_id as integer)  as s_company_id, 
cast( s_company_name as varchar(200))  as s_company_name, 
cast( s_street_number as varchar(200))  as s_street_number, 
cast( s_street_name as varchar(200))  as s_street_name, 
cast( s_street_type as varchar(200))  as s_street_type, 
cast( s_suite_number as varchar(200))  as s_suite_number, 
cast( s_city as varchar(200))  as s_city, 
cast( s_county as varchar(200))  as s_county, 
cast( s_state as varchar(200))  as s_state, 
cast( s_zip as varchar(200))  as s_zip, 
cast( s_country as varchar(200))  as s_country, 
cast( s_gmt_offset as double)  as s_gmt_offset, 
cast( s_tax_precentage as double)  as s_tax_precentage 
from dfs.`/drill/testdata/tpcds_sf1/parquet/store`;
{code}

ERROR -
{code}
Error: SYSTEM ERROR: AssertionError: Internal error: Conversion to relational 
algebra failed to preserve datatypes:
validated type:
RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "ISO-8859-1" COLLATE 
"ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE s_rec__date, 
INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET "ISO-8859-1" COLLATE 
"ISO-8859-1$en_US$primary" s_store_name, INTEGER s_number_employees, INTEGER 
s_floor_space, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_hours, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_manager, INTEGER s_market_id, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_geography_class, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_market_desc, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_market_manager, INTEGER s_division_id, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_division_name, INTEGER s_company_id, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_company_name, VARCHAR(200) CHARACTER SET 
"UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_number, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_street_name, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_street_type, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_suite_number, VARCHAR(200) CHARACTER SET 
"UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_city, VARCHAR(200) CHARACTER 
SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_county, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_state, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_zip, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" 
s_country, DOUBLE s_gmt_offset, DOUBLE s_tax_precentage) NOT NULL
converted type:
RecordType(INTEGER s_store_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_store_id, DATE s_rec_start_date, DATE s_rec__date, 
INTEGER s_closed_date_sk, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_store_name, INTEGER s_number_employees, INTEGER 
s_floor_space, VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE 
"ISO-8859-1$en_US$primary" s_hours, VARCHAR(200) CHARACTER SET "UTF-16LE" 
COLLATE "ISO-8859-1$en_US$primary" s_manager, INTEGER s_market_id, VARCHAR(200) 
CHARACTER SET "UTF-16LE" COLLATE "ISO-8859-1$en_US$primary" s_geography_class, 
VARCHAR(200) CHARACTER SET "UTF-16LE" COLLATE

[jira] [Commented] (DRILL-6025) Execution time of a running query shown as 'NOT AVAILABLE'

2017-12-11 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16287225#comment-16287225
 ] 

Prasad Nagaraj Subramanya commented on DRILL-6025:
--

No, the total time shows the duration since the query was started

I am talking of the case when the query state is 'RUNNING'. In such a case we 
could show the execution time till that point in time, similar to total time of 
a query in execution.

> Execution time of a running query shown as 'NOT AVAILABLE'
> --
>
> Key: DRILL-6025
> URL: https://issues.apache.org/jira/browse/DRILL-6025
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Client - HTTP
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>
> When a query is in 'RUNNING' state, the execution time is shown as 'NOT 
> AVAILABLE'
> We could show the execution duration till the current time



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

[jira] [Created] (DRILL-6025) Execution time of a running query shown as 'NOT AVAILABLE'

2017-12-11 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-6025:


 Summary: Execution time of a running query shown as 'NOT AVAILABLE'
 Key: DRILL-6025
 URL: https://issues.apache.org/jira/browse/DRILL-6025
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya


When a query is in 'RUNNING' state, the execution time is shown as 'NOT 
AVAILABLE'

We could show the execution duration till the current time



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

[jira] [Updated] (DRILL-6025) Execution time of a running query shown as 'NOT AVAILABLE'

2017-12-11 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-6025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-6025:
-
Issue Type: Improvement  (was: Bug)

> Execution time of a running query shown as 'NOT AVAILABLE'
> --
>
> Key: DRILL-6025
> URL: https://issues.apache.org/jira/browse/DRILL-6025
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Client - HTTP
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>
> When a query is in 'RUNNING' state, the execution time is shown as 'NOT 
> AVAILABLE'
> We could show the execution duration till the current time



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

[jira] [Created] (DRILL-5998) Queue information of queries which fail due to queue time out not shown

2017-11-28 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5998:


 Summary: Queue information of queries which fail due to queue time 
out not shown
 Key: DRILL-5998
 URL: https://issues.apache.org/jira/browse/DRILL-5998
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya


When a query fails because of queue time out, the queue information is not 
shown in the web UI



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

[jira] [Assigned] (DRILL-4092) Support for INTERSECT

2017-11-11 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya reassigned DRILL-4092:


Assignee: Prasad Nagaraj Subramanya  (was: Chunhui Shi)

> Support for INTERSECT 
> --
>
> Key: DRILL-4092
> URL: https://issues.apache.org/jira/browse/DRILL-4092
> Project: Apache Drill
>  Issue Type: New Feature
>Reporter: Victoria Markman
>Assignee: Prasad Nagaraj Subramanya
>




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

[jira] [Updated] (DRILL-5909) need new JMX metrics for (FAILED and CANCELED) queries

2017-11-10 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5909:
-
Issue Type: Improvement  (was: Bug)

> need new JMX metrics for (FAILED and CANCELED) queries
> --
>
> Key: DRILL-5909
> URL: https://issues.apache.org/jira/browse/DRILL-5909
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Execution - Monitoring
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Khurram Faraaz
>Assignee: Prasad Nagaraj Subramanya
>  Labels: ready-to-commit
> Fix For: 1.12.0
>
>
> we have these JMX metrics today
> {noformat}
> drill.queries.running
> drill.queries.completed
> {noformat}
> we need these new JMX metrics
> {noformat}
> drill.queries.failed
> drill.queries.canceled
> {noformat}



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

[jira] [Updated] (DRILL-5952) Implement "CREATE TABLE IF NOT EXISTS"

2017-11-10 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5952:
-
Issue Type: Improvement  (was: Bug)

> Implement "CREATE TABLE IF NOT EXISTS"
> --
>
> Key: DRILL-5952
> URL: https://issues.apache.org/jira/browse/DRILL-5952
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: SQL Parser
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
> Fix For: 1.12.0
>
>
> Currently, if a table/view with the same name exists CREATE TABLE fails with 
> VALIDATION ERROR
> Having "IF NOT EXISTS" support for CREATE TABLE will ensure that query 
> succeeds 



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

[jira] [Updated] (DRILL-5921) Counters metrics should be listed in table

2017-11-10 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5921:
-
Issue Type: Improvement  (was: Bug)

> Counters metrics should be listed in table
> --
>
> Key: DRILL-5921
> URL: https://issues.apache.org/jira/browse/DRILL-5921
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Client - HTTP
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>Priority: Minor
>  Labels: ready-to-commit
> Fix For: 1.12.0
>
>
> Counter metrics are currently displayed as json string in the Drill UI. They 
> should be listed in a table similar to other metrics.



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

[jira] [Created] (DRILL-5952) Implement "CREATE TABLE IF NOT EXISTS"

2017-11-10 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5952:


 Summary: Implement "CREATE TABLE IF NOT EXISTS"
 Key: DRILL-5952
 URL: https://issues.apache.org/jira/browse/DRILL-5952
 Project: Apache Drill
  Issue Type: Bug
  Components: SQL Parser
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
 Fix For: 1.12.0


Currently, if a table/view with the same name exists CREATE TABLE fails with 
VALIDATION ERROR

Having "IF NOT EXISTS" support for CREATE TABLE will ensure that query succeeds 



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

[jira] [Created] (DRILL-5923) State of a successfully completed query shown as "COMPLETED"

2017-11-02 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5923:


 Summary: State of a successfully completed query shown as 
"COMPLETED"
 Key: DRILL-5923
 URL: https://issues.apache.org/jira/browse/DRILL-5923
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
Priority: Major
 Fix For: 1.12.0


Drill UI currently lists a successfully completed query as "COMPLETED". 
Successfully completed, failed and canceled queries are all grouped as 
Completed queries. 

It would be better to list the state of a successfully completed query as 
"Succeeded" to avoid confusion.



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

[jira] [Created] (DRILL-5921) Counters metrics should be listed in table

2017-11-01 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5921:


 Summary: Counters metrics should be listed in table
 Key: DRILL-5921
 URL: https://issues.apache.org/jira/browse/DRILL-5921
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
Priority: Minor
 Fix For: 1.12.0


Counter metrics are currently displayed as json string in the Drill UI. They 
should be listed in a table similar to other metrics.



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

[jira] [Updated] (DRILL-5909) need new JMX metrics for (FAILED and CANCELED) queries

2017-11-01 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5909:
-
Fix Version/s: 1.12.0

> need new JMX metrics for (FAILED and CANCELED) queries
> --
>
> Key: DRILL-5909
> URL: https://issues.apache.org/jira/browse/DRILL-5909
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Monitoring
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Khurram Faraaz
>Assignee: Prasad Nagaraj Subramanya
>Priority: Major
> Fix For: 1.12.0
>
>
> we have these JMX metrics today
> {noformat}
> drill.queries.running
> drill.queries.completed
> {noformat}
> we need these new JMX metrics
> {noformat}
> drill.queries.failed
> drill.queries.canceled
> {noformat}



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

[jira] [Assigned] (DRILL-5909) need new JMX metrics for (FAILED and CANCELED) queries

2017-11-01 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya reassigned DRILL-5909:


Assignee: Prasad Nagaraj Subramanya

> need new JMX metrics for (FAILED and CANCELED) queries
> --
>
> Key: DRILL-5909
> URL: https://issues.apache.org/jira/browse/DRILL-5909
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Monitoring
>Affects Versions: 1.11.0, 1.12.0
>Reporter: Khurram Faraaz
>Assignee: Prasad Nagaraj Subramanya
>Priority: Major
>
> we have these JMX metrics today
> {noformat}
> drill.queries.running
> drill.queries.completed
> {noformat}
> we need these new JMX metrics
> {noformat}
> drill.queries.failed
> drill.queries.canceled
> {noformat}



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

[jira] [Commented] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

2017-10-21 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214172#comment-16214172
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5822:
--

I missed one thing in the description. This happens when order by is used in 
the query.
{code}
alter session set `planner.slice_target`=1;
select * from dfs.`/json_dir` order by p_partkey;
{code}

DRILL-5845 solves the issue only in TopNBatch. But this query uses 
managed/ExternalSortBatch

> Select * on directory containing multiple json files (one or more empty) with 
> same schema doesn't preserve column order
> ---
>
> Key: DRILL-5822
> URL: https://issues.apache.org/jira/browse/DRILL-5822
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Vitalii Diravka
> Fix For: 1.12.0
>
>
> Repro steps
> 1) Have multiple json files in a directory having the same schema
> 2) Also have one or more empty files 
> Scenarios
> 1) Only one minor fragment{code}select * from dfs.`/json_dir`;{code}
> {code}Result:
> +--++--+-+---++-+--+++
> | row_key  | p_partkey  |  p_name  | 
> p_mfgr  |  p_brand  |   p_type   | p_size  | p_container  
> | p_retailprice  |   p_comment|
> +--++--+-+---++-+--+++
> | 1| 1  | goldenrod lace spring peru powder| 
> Manufacturer#1  | Brand#13  | PROMO BURNISHED COPPER | 7   | JUMBO 
> PKG| 901.0  | ly. slyly ironi|
> | 2| 2  | blush rosy metallic lemon navajo | 
> Manufacturer#1  | Brand#13  | LARGE BRUSHED BRASS| 1   | LG CASE  
> | 902.0  | lar accounts amo   |
> {code}
>  2) One minor fragment per file
> {code}alter session set `planner.slice_target`=1;
> select * from dfs.`/json_dir`;{code}
> Result:
> {code}
> +---++--+-+--+++-++--+
> |  p_brand  |   p_comment| p_container  | p_mfgr  |   
>p_name  | p_partkey  | p_retailprice  | p_size  |  
>  p_type   | row_key  |
> +---++--+-+--+++-++--+
> | Brand#13  | ly. slyly ironi| JUMBO PKG| Manufacturer#1  | 
> goldenrod lace spring peru powder| 1  | 901.0  | 7
>| PROMO BURNISHED COPPER | 1|
> | Brand#13  | lar accounts amo   | LG CASE  | Manufacturer#1  | blush 
> rosy metallic lemon navajo | 2  | 902.0  | 1   | 
> LARGE BRUSHED BRASS| 2|
> {code}
>  



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

[jira] [Created] (DRILL-5896) Handle vector creation in HbaseRecordReader to avoid NullableInt vectors later

2017-10-20 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5896:


 Summary: Handle vector creation in HbaseRecordReader to avoid 
NullableInt vectors later
 Key: DRILL-5896
 URL: https://issues.apache.org/jira/browse/DRILL-5896
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - HBase
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
 Fix For: 1.12.0


When a hbase query projects both a column family and a column in the column 
family, the vector for the column is not created in the HbaseRecordReader.

So, in cases where scan batch is empty we create a NullableInt vector for this 
column. We need to handle column creation in the reader.



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

[jira] [Created] (DRILL-5887) Display process user/ groups in Drill UI

2017-10-17 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5887:


 Summary: Display process user/ groups in Drill UI
 Key: DRILL-5887
 URL: https://issues.apache.org/jira/browse/DRILL-5887
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
Priority: Minor
 Fix For: 1.12.0


Drill UI only lists admin user/ groups specified as options

We should display the process user/ groups who have admin privilege



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

[jira] [Created] (DRILL-5880) java.sql.SQLException: UNSUPPORTED_OPERATION ERROR: This query cannot be planned possibly due to either a cartesian join or an inequality join

2017-10-16 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5880:


 Summary: java.sql.SQLException: UNSUPPORTED_OPERATION ERROR: This 
query cannot be planned possibly due to either a cartesian join or an 
inequality join
 Key: DRILL-5880
 URL: https://issues.apache.org/jira/browse/DRILL-5880
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


Consider the below query
{code}
select region.sales_region as c0, region_1.sales_region as c1, 
sum(sales_fact_1997.unit_sales) as m0 from region as region, store as store, 
sales_fact_1997 as sales_fact_1997, region as region_1, customer as customer 
where sales_fact_1997.store_id = store.store_id and store.region_id = 
region.region_id and region.sales_region = 'South West' and 
sales_fact_1997.customer_id = customer.customer_id and 
customer.customer_region_id = region_1.region_id and region_1.sales_region = 
'South West' group by region.sales_region, region_1.sales_region
{code}

The query fails with the following error-
{code}
(org.apache.drill.exec.work.foreman.UnsupportedRelOperatorException) This query 
cannot be planned possibly due to either a cartesian join or an inequality join

org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToPrel():437
org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.getPlan():169
org.apache.drill.exec.planner.sql.DrillSqlWorker.getQueryPlan():131
org.apache.drill.exec.planner.sql.DrillSqlWorker.getPlan():79
org.apache.drill.exec.work.foreman.Foreman.runSQL():991
org.apache.drill.exec.work.foreman.Foreman.run():276
java.util.concurrent.ThreadPoolExecutor.runWorker():1145
java.util.concurrent.ThreadPoolExecutor$Worker.run():615
java.lang.Thread.run():744
{code}

This is a regression. It worked with drill 1.10.0

Having a single alias of the table region in the above query works fine.



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

[jira] [Created] (DRILL-5869) Empty maps not handled

2017-10-12 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5869:


 Summary: Empty maps not handled 
 Key: DRILL-5869
 URL: https://issues.apache.org/jira/browse/DRILL-5869
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - JSON
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


Consider the below json -
{code}
{a:{}}
{code}

A query on the column 'a' throws NPE -
{code}
select a from temp.json;
{code}

Stack trace -
{code}
org.apache.drill.common.exceptions.UserException: SYSTEM ERROR: 
NullPointerException

Fragment 0:0

[Error Id: 7f81fa02-4b20-4401-9d18-bd901653d11d on pns182.qa.lab:31010]
at 
org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:586)
 ~[drill-common-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor.sendFinalState(FragmentExecutor.java:298)
 [drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup(FragmentExecutor.java:160)
 [drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:267)
 [drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38) 
[drill-common-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[na:1.8.0_144]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[na:1.8.0_144]
at java.lang.Thread.run(Thread.java:748) [na:1.8.0_144]
Caused by: java.lang.NullPointerException: null
at 
org.apache.drill.exec.test.generated.ProjectorGen0.setup(ProjectorTemplate.java:91)
 ~[na:na]
at 
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.setupNewSchemaFromInput(ProjectRecordBatch.java:497)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.setupNewSchema(ProjectRecordBatch.java:505)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.record.AbstractSingleRecordBatch.innerNext(AbstractSingleRecordBatch.java:82)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.physical.impl.project.ProjectRecordBatch.innerNext(ProjectRecordBatch.java:141)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.record.AbstractRecordBatch.next(AbstractRecordBatch.java:164)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.physical.impl.BaseRootExec.next(BaseRootExec.java:105) 
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.physical.impl.ScreenCreator$ScreenRoot.innerNext(ScreenCreator.java:81)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.physical.impl.BaseRootExec.next(BaseRootExec.java:95) 
~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run(FragmentExecutor.java:234)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor$1.run(FragmentExecutor.java:227)
 ~[drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
at java.security.AccessController.doPrivileged(Native Method) 
~[na:1.8.0_144]
at javax.security.auth.Subject.doAs(Subject.java:422) ~[na:1.8.0_144]
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1595)
 ~[hadoop-common-2.7.0-mapr-1607.jar:na]
at 
org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:227)
 [drill-java-exec-1.12.0-SNAPSHOT.jar:1.12.0-SNAPSHOT]
... 4 common frames omitted
{code}



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

[jira] [Created] (DRILL-5861) Need HBase storage plugin validation when enabled / updated

2017-10-11 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5861:


 Summary: Need HBase storage plugin validation when enabled / 
updated
 Key: DRILL-5861
 URL: https://issues.apache.org/jira/browse/DRILL-5861
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - HBase
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya


Currently, when hbase storage plugin is enabled / updated there is no 
validation.

It would be good to have a validation.



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

[jira] [Commented] (DRILL-5859) Time for query queuing timeout not display correctly in WebUI

2017-10-10 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16199718#comment-16199718
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5859:
--

Opened a PR -  https://github.com/apache/drill/pull/982

> Time for query queuing timeout not display correctly in WebUI
> -
>
> Key: DRILL-5859
> URL: https://issues.apache.org/jira/browse/DRILL-5859
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Client - HTTP
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>Priority: Minor
> Fix For: 1.12.0
>
>
> With exec.queue.enable=true and exec.queue.timeout_millis=30 (ms), the 
> data for timed out queries due to exceeding the exec.queue.timeout_millis 
> limit in the WebUI shows as:
> {code}
> State:FAILED  Duration:   05 min 0.559 sec
> Foreman:  qa-node114.qa.lab   Planning:   0.529 sec
> Total Fragments:  0   Queued: Not Available
> Total Cost:   575,415,266.982 Execution:  05 min 0.030 sec
> {code}
> The "05 min 0.030 sec" value should be for the "Queued" key instead of the 
> "Execution" key.
> Also, the error in the log file for the query is shown as:
> "RESOURCE ERROR: Query timed out of the large queue after 300 ms."
> It should say "... 300 seconds"



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

[jira] [Created] (DRILL-5859) Time for query queuing timeout not display correctly in WebUI

2017-10-10 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5859:


 Summary: Time for query queuing timeout not display correctly in 
WebUI
 Key: DRILL-5859
 URL: https://issues.apache.org/jira/browse/DRILL-5859
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - HTTP
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
Assignee: Prasad Nagaraj Subramanya
Priority: Minor
 Fix For: 1.12.0


With exec.queue.enable=true and exec.queue.timeout_millis=30 (ms), the data 
for timed out queries due to exceeding the exec.queue.timeout_millis limit in 
the WebUI shows as:

{code}
State:  FAILED  Duration:   05 min 0.559 sec
Foreman:qa-node114.qa.lab   Planning:   0.529 sec
Total Fragments:0   Queued: Not Available
Total Cost: 575,415,266.982 Execution:  05 min 0.030 sec
{code}

The "05 min 0.030 sec" value should be for the "Queued" key instead of the 
"Execution" key.
Also, the error in the log file for the query is shown as:
"RESOURCE ERROR: Query timed out of the large queue after 300 ms."
It should say "... 300 seconds"



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

[jira] [Commented] (DRILL-5851) Empty table during a join operation with a non empty table produces cast exception

2017-10-09 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197060#comment-16197060
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5851:
--

This issue is being observed for all supported data sources. In short, this is 
because we return nullable INT when any reader reads empty data.

> Empty table during a join operation with a non empty table produces cast 
> exception 
> ---
>
> Key: DRILL-5851
> URL: https://issues.apache.org/jira/browse/DRILL-5851
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Relational Operators
>Affects Versions: 1.11.0
>Reporter: Hanumath Rao Maduri
>Assignee: Hanumath Rao Maduri
>
> Hash Join operation on tables with one table empty and the other non empty 
> throws an exception 
> {code} 
> Error: SYSTEM ERROR: DrillRuntimeException: Join only supports implicit casts 
> between 1. Numeric data
>  2. Varchar, Varbinary data 3. Date, Timestamp data Left type: VARCHAR, Right 
> type: INT. Add explicit casts to avoid this error
> {code}
> Here is an example query with which it is reproducible.
> {code}
> select * from cp.`sample-data/nation.parquet` nation left outer join 
> dfs.tmp.`2.csv` as two on two.a = nation.`N_COMMENT`;
> {code}
> the contents of 2.csv is empty (i.e not even header info).



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

[jira] [Commented] (DRILL-5851) Empty table during a join operation with a non empty table produces cast exception

2017-10-09 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16196581#comment-16196581
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5851:
--

I did some analysis on the test case. The cause of the issue is 
1) empty csv file and star query
2) parquet column involved in the join is of non-integer type (could be any 
other data source)

The issue is not observed under below circumstances -
a) If the parquet column was of type integer then we do not observe this issue. 
This is because its a '*' query and involves a csv file with no headers - an 
instance of RepeatedVarCharOutput is used which returns nullable int when there 
is no data.

b) If csv column was projected using columns[]
{code}
select * from cp.`sample-data/nation.parquet` nation left outer join 
dfs.tmp.`2.csv` as two on two.columns[1] = nation.`N_COMMENT`;
{code} 

c) If a empty csv was used with extract header set to true, and we had 
projections rather than *
{code}
select nation.`N_COMMENT`, nation.`N_NAME`, two.b  from 
cp.`sample-data/nation.parquet` nation left outer join dfs.tmp.`2.csv` as two 
on two.a = nation.`N_COMMENT`;
{code}

> Empty table during a join operation with a non empty table produces cast 
> exception 
> ---
>
> Key: DRILL-5851
> URL: https://issues.apache.org/jira/browse/DRILL-5851
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Relational Operators
>Affects Versions: 1.11.0
>Reporter: Hanumath Rao Maduri
>Assignee: Hanumath Rao Maduri
>
> Hash Join operation on tables with one table empty and the other non empty 
> throws an exception 
> {code} 
> Error: SYSTEM ERROR: DrillRuntimeException: Join only supports implicit casts 
> between 1. Numeric data
>  2. Varchar, Varbinary data 3. Date, Timestamp data Left type: VARCHAR, Right 
> type: INT. Add explicit casts to avoid this error
> {code}
> Here is an example query with which it is reproducible.
> {code}
> select * from cp.`sample-data/nation.parquet` nation left outer join 
> dfs.tmp.`2.csv` as two on two.a = nation.`N_COMMENT`;
> {code}
> the contents of 2.csv is empty (i.e not even header info).



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

[jira] [Commented] (DRILL-5851) Empty table during a join operation with a non empty table produces cast exception

2017-10-06 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16195542#comment-16195542
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5851:
--

This looks to be only when parquet file is involved in the join. Any other file 
type (csv, psv, json), hbase or maprdb works fine after the fix for DRILL-5546.

> Empty table during a join operation with a non empty table produces cast 
> exception 
> ---
>
> Key: DRILL-5851
> URL: https://issues.apache.org/jira/browse/DRILL-5851
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Relational Operators
>Affects Versions: 1.11.0
>Reporter: Hanumath Rao Maduri
>Assignee: Hanumath Rao Maduri
>
> Hash Join operation on tables with one table empty and the other non empty 
> throws an exception 
> {code} 
> Error: SYSTEM ERROR: DrillRuntimeException: Join only supports implicit casts 
> between 1. Numeric data
>  2. Varchar, Varbinary data 3. Date, Timestamp data Left type: VARCHAR, Right 
> type: INT. Add explicit casts to avoid this error
> {code}
> Here is an example query with which it is reproducible.
> {code}
> select * from cp.`sample-data/nation.parquet` nation left outer join 
> dfs.tmp.`2.csv` as two on two.a = nation.`N_COMMENT`;
> {code}
> the contents of 2.csv is empty (i.e not even header info).



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

[jira] [Assigned] (DRILL-5743) Using order by clause in a select * query on hbase table returns only the row_key and order by field(s)

2017-10-03 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya reassigned DRILL-5743:


Assignee: Prasad Nagaraj Subramanya

> Using order by clause in a select * query on hbase table returns only the 
> row_key and order by field(s)
> ---
>
> Key: DRILL-5743
> URL: https://issues.apache.org/jira/browse/DRILL-5743
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - HBase
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>Assignee: Prasad Nagaraj Subramanya
>
> 1) Consider a hbase table 'part' having column family 'data', which contains 
> columns related to tpch part table
> {code}
> select * from hbase.`part`;
> {code}
> Result
> {code}
> +-+--+
> | row_key | data |
> +-+--+
> | [B@381ea162 | 
> {"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="}
>  |
> {code}
> 3) Consider the following query -
> {code}
> select * from hbase.`part` as t order by t.data.p_name;
> {code}
> Expected
> The query should return row_key, and all the columns in 'data' column family 
> ordered by column 'data.p_name'
> Actual
> {code}
> +--++
> |   row_key|  data  |
> +--++
> | [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
> +--++
> {code}
> Result contains only the row_key and column data.p_name, order by data.p_name



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

[jira] [Commented] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

2017-09-28 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184544#comment-16184544
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5822:
--

[~vitalii] Sorry for the confusion with different number of rows. I copied the 
rows just to give an idea of the unordering. Made the changes in the 
description accordingly.

It is reproducible on latest drill master (commit id - 
8a8bf63f7e9f804e761c69f8e94f34417f83c7f7)

Before the fix for DRILL-5546 we got empty rows equal to the total number of 
rows in all the files combined
{code}
+--+
|  |
+--+
|  |
|  |
{code}

> Select * on directory containing multiple json files (one or more empty) with 
> same schema doesn't preserve column order
> ---
>
> Key: DRILL-5822
> URL: https://issues.apache.org/jira/browse/DRILL-5822
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
> Fix For: 1.12.0
>
>
> Repro steps
> 1) Have multiple json files in a directory having the same schema
> 2) Also have one or more empty files 
> Scenarios
> 1) Only one minor fragment{code}select * from dfs.`/json_dir`;{code}
> {code}Result:
> +--++--+-+---++-+--+++
> | row_key  | p_partkey  |  p_name  | 
> p_mfgr  |  p_brand  |   p_type   | p_size  | p_container  
> | p_retailprice  |   p_comment|
> +--++--+-+---++-+--+++
> | 1| 1  | goldenrod lace spring peru powder| 
> Manufacturer#1  | Brand#13  | PROMO BURNISHED COPPER | 7   | JUMBO 
> PKG| 901.0  | ly. slyly ironi|
> | 2| 2  | blush rosy metallic lemon navajo | 
> Manufacturer#1  | Brand#13  | LARGE BRUSHED BRASS| 1   | LG CASE  
> | 902.0  | lar accounts amo   |
> {code}
>  2) One minor fragment per file
> {code}alter session set `planner.slice_target`=1;
> select * from dfs.`/json_dir`;{code}
> Result:
> {code}
> +---++--+-+--+++-++--+
> |  p_brand  |   p_comment| p_container  | p_mfgr  |   
>p_name  | p_partkey  | p_retailprice  | p_size  |  
>  p_type   | row_key  |
> +---++--+-+--+++-++--+
> | Brand#13  | ly. slyly ironi| JUMBO PKG| Manufacturer#1  | 
> goldenrod lace spring peru powder| 1  | 901.0  | 7
>| PROMO BURNISHED COPPER | 1|
> | Brand#13  | lar accounts amo   | LG CASE  | Manufacturer#1  | blush 
> rosy metallic lemon navajo | 2  | 902.0  | 1   | 
> LARGE BRUSHED BRASS| 2|
> {code}
>  



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

[jira] [Updated] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

2017-09-28 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5822:
-
Description: 
Repro steps
1) Have multiple json files in a directory having the same schema
2) Also have one or more empty files 

Scenarios
1) Only one minor fragment{code}select * from dfs.`/json_dir`;{code}
{code}Result:
+--++--+-+---++-+--+++
| row_key  | p_partkey  |  p_name  | p_mfgr 
 |  p_brand  |   p_type   | p_size  | p_container  | 
p_retailprice  |   p_comment|
+--++--+-+---++-+--+++
| 1| 1  | goldenrod lace spring peru powder| 
Manufacturer#1  | Brand#13  | PROMO BURNISHED COPPER | 7   | JUMBO PKG  
  | 901.0  | ly. slyly ironi|
| 2| 2  | blush rosy metallic lemon navajo | 
Manufacturer#1  | Brand#13  | LARGE BRUSHED BRASS| 1   | LG CASE
  | 902.0  | lar accounts amo   |
{code}
 2) One minor fragment per file
{code}alter session set `planner.slice_target`=1;
select * from dfs.`/json_dir`;{code}
Result:
{code}
+---++--+-+--+++-++--+
|  p_brand  |   p_comment| p_container  | p_mfgr  | 
 p_name  | p_partkey  | p_retailprice  | p_size  |  
 p_type   | row_key  |
+---++--+-+--+++-++--+
| Brand#13  | ly. slyly ironi| JUMBO PKG| Manufacturer#1  | 
goldenrod lace spring peru powder| 1  | 901.0  | 7  
 | PROMO BURNISHED COPPER | 1|
| Brand#13  | lar accounts amo   | LG CASE  | Manufacturer#1  | blush 
rosy metallic lemon navajo | 2  | 902.0  | 1   | 
LARGE BRUSHED BRASS| 2|
{code}
 

  was:
Repro steps
1) Have multiple json files in a directory having the same schema
2) Also have one or more empty files 

Scenarios
1) Only one minor fragment{code}select * from dfs.`/json_dir`;{code}
{code}Result:
+--++--+-+---++-+--+++
| row_key  | p_partkey  |  p_name  | p_mfgr 
 |  p_brand  |   p_type   | p_size  | p_container  | 
p_retailprice  |   p_comment|
+--++--+-+---++-+--+++
| 1| 1  | goldenrod lace spring peru powder| 
Manufacturer#1  | Brand#13  | PROMO BURNISHED COPPER | 7   | JUMBO PKG  
  | 901.0  | ly. slyly ironi|
| 2| 2  | blush rosy metallic lemon navajo | 
Manufacturer#1  | Brand#13  | LARGE BRUSHED BRASS| 1   | LG CASE
  | 902.0  | lar accounts amo   |
{code}
 2) One minor fragment per file
{code}alter session set `planner.slice_target`=1;
select * from dfs.`/json_dir`;{code}
Result:
{code}
+---++--+-+--+++-++--+
|  p_brand  |   p_comment| p_container  | p_mfgr  | 
 p_name  | p_partkey  | p_retailprice  | p_size  |  
 p_type   | row_key  |
+---++--+-+--+++-++--+
| Brand#13  | ly. slyly ironi| JUMBO PKG| Manufacturer#1  | 
goldenrod lace spring peru powder| 1  | 901.0  | 7  
 | PROMO BURNISHED COPPER | 1|
| Brand#13  | lar accounts amo   | LG CASE  | Manufacturer#1  | blush 
rosy metallic lemon navajo | 2  | 902.0  | 1   | 
LARGE BRUSHED BRASS| 2|
| Brand#42  | egular deposits hag| WRAP CASE| Manufacturer#4  | dark 
green antique puff wheat| 3

[jira] [Created] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

2017-09-27 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5822:


 Summary: Select * on directory containing multiple json files (one 
or more empty) with same schema doesn't preserve column order
 Key: DRILL-5822
 URL: https://issues.apache.org/jira/browse/DRILL-5822
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - JSON
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
 Fix For: 1.12.0


Repro steps
1) Have multiple json files in a directory having the same schema
2) Also have one or more empty files 

Scenarios
1) Only one minor fragment{code}select * from dfs.`/json_dir`;{code}
{code}Result:
+--++--+-+---++-+--+++
| row_key  | p_partkey  |  p_name  | p_mfgr 
 |  p_brand  |   p_type   | p_size  | p_container  | 
p_retailprice  |   p_comment|
+--++--+-+---++-+--+++
| 1| 1  | goldenrod lace spring peru powder| 
Manufacturer#1  | Brand#13  | PROMO BURNISHED COPPER | 7   | JUMBO PKG  
  | 901.0  | ly. slyly ironi|
| 2| 2  | blush rosy metallic lemon navajo | 
Manufacturer#1  | Brand#13  | LARGE BRUSHED BRASS| 1   | LG CASE
  | 902.0  | lar accounts amo   |
{code}
 2) One minor fragment per file
{code}alter session set `planner.slice_target`=1;
select * from dfs.`/json_dir`;{code}
Result:
{code}
+---++--+-+--+++-++--+
|  p_brand  |   p_comment| p_container  | p_mfgr  | 
 p_name  | p_partkey  | p_retailprice  | p_size  |  
 p_type   | row_key  |
+---++--+-+--+++-++--+
| Brand#13  | ly. slyly ironi| JUMBO PKG| Manufacturer#1  | 
goldenrod lace spring peru powder| 1  | 901.0  | 7  
 | PROMO BURNISHED COPPER | 1|
| Brand#13  | lar accounts amo   | LG CASE  | Manufacturer#1  | blush 
rosy metallic lemon navajo | 2  | 902.0  | 1   | 
LARGE BRUSHED BRASS| 2|
| Brand#42  | egular deposits hag| WRAP CASE| Manufacturer#4  | dark 
green antique puff wheat| 3  | 903.0  | 21  | 
STANDARD POLISHED BRASS| 3|
{code}
 



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

[jira] [Created] (DRILL-5819) Default value of security.admin.user_groups and security.admin.users is "true"

2017-09-25 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5819:


 Summary: Default value of security.admin.user_groups and 
security.admin.users is "true"
 Key: DRILL-5819
 URL: https://issues.apache.org/jira/browse/DRILL-5819
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya
 Fix For: 1.12.0


Default value of security.admin.user_groups and security.admin.users is "true"



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

[jira] [Updated] (DRILL-5711) Incorrect operator profiles for queries on json files

2017-09-20 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5711:
-
Description: 
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile. It has the following issues -
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type

Attached
1) Two json files
2) Snapshot of query profile and operator profile

Commit id - 9d1d815737528251a7500621cc976b57e7f3be59

  was:
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type

Attached
1) Two json files
2) Snapshot of query profile and operator profile

Commit id - 9d1d815737528251a7500621cc976b57e7f3be59


> Incorrect operator profiles for queries on json files
> -
>
> Key: DRILL-5711
> URL: https://issues.apache.org/jira/browse/DRILL-5711
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
> Attachments: OperatorProfiles.png, part.json, partsupp.json, 
> QueryProfile.png
>
>
> 1) Join query on two json files
> {code}
> select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
> dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
> {code}
> 2) Check the query profile. It has the following issues -
> a) JSON_SUB_SCAN type incorrectly ordered
> b) Missing SCREEN type
> Attached
> 1) Two json files
> 2) Snapshot of query profile and operator profile
> Commit id - 9d1d815737528251a7500621cc976b57e7f3be59



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

[jira] [Assigned] (DRILL-5745) Invalid "location" information in Drill web server

2017-09-20 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya reassigned DRILL-5745:


Assignee: Prasad Nagaraj Subramanya

> Invalid "location" information in Drill web server
> --
>
> Key: DRILL-5745
> URL: https://issues.apache.org/jira/browse/DRILL-5745
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Web Server
>Affects Versions: 1.11.0
>Reporter: Paul Rogers
>Assignee: Prasad Nagaraj Subramanya
>Priority: Minor
>  Labels: ready-to-commit
> Fix For: 1.12.0
>
>
> The file {{ProfileResources.java}} has the following incorrect code line:
> {code}
>   this.location = "http://localhost:8047/profile/; + queryId + ".json";
> {code}
> This code makes three errors.
> 1. The "http" prefix ignores the fact that the Drillbit can have SSL enabled 
> for the web server.
> 2. In a browser, "localhost" refers to the the machine running the browser. 
> This is valid only if the browser runs on the same machine as the Drillbit, 
> which is not, in general, true.
> 3. The port number is hardcoded to 8047, but it can be customized in the 
> config file.
> Therefore, most of the time, the link won't work on a production server.



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

[jira] [Resolved] (DRILL-5724) Scan on a local directory containing multiple text files (one or more empty) throws FileNotFoundException

2017-09-15 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya resolved DRILL-5724.
--
Resolution: Cannot Reproduce

> Scan on a local directory containing multiple text files (one or more empty) 
> throws FileNotFoundException
> -
>
> Key: DRILL-5724
> URL: https://issues.apache.org/jira/browse/DRILL-5724
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Text & CSV
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> 1) Create a directory having multiple text files (one or more empty)
> 2) Do a scan on the directory
> {code}
> select * from lfs.`/home/user/dir1`;
> {code}
> The query throws the below error-
> {code}
> Error: SYSTEM ERROR: FileNotFoundException: File 
> file:///home/user/dir1/ does not exist
> Setup failed for CompliantTextRecordReader
> Fragment 1:2
> {code}
> Issue reproducible with - csv, tsv and psv files



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

[jira] [Commented] (DRILL-5724) Scan on a local directory containing multiple text files (one or more empty) throws FileNotFoundException

2017-09-15 Thread Prasad Nagaraj Subramanya (JIRA)


[ 
https://issues.apache.org/jira/browse/DRILL-5724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16168302#comment-16168302
 ] 

Prasad Nagaraj Subramanya commented on DRILL-5724:
--

Issue not reproducible with commit id - 7a900b71fd269aceee7301afb18fd8d303df5bcd

> Scan on a local directory containing multiple text files (one or more empty) 
> throws FileNotFoundException
> -
>
> Key: DRILL-5724
> URL: https://issues.apache.org/jira/browse/DRILL-5724
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - Text & CSV
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> 1) Create a directory having multiple text files (one or more empty)
> 2) Do a scan on the directory
> {code}
> select * from lfs.`/home/user/dir1`;
> {code}
> The query throws the below error-
> {code}
> Error: SYSTEM ERROR: FileNotFoundException: File 
> file:///home/user/dir1/ does not exist
> Setup failed for CompliantTextRecordReader
> Fragment 1:2
> {code}
> Issue reproducible with - csv, tsv and psv files



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

[jira] [Created] (DRILL-5775) Select * query on a maprdb binary table fails

2017-09-07 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5775:


 Summary: Select * query on a maprdb binary table fails
 Key: DRILL-5775
 URL: https://issues.apache.org/jira/browse/DRILL-5775
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - MapRDB
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


Select * query on a maprdb binary table fails with the below exception

Failed with exception
java.sql.SQLException: SYSTEM ERROR: IllegalArgumentException: 
HBaseRecordReader does not allow column *. Column * should have been converted 
to list of

[jira] [Updated] (DRILL-5743) Using order by clause in a select * query on hbase table returns only the row_key and order by field(s)

2017-08-27 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5743:
-
Description: 
1) Consider a hbase table 'part' having column family 'data', which contains 
columns related to tpch part table
{code}
select * from hbase.`part`;
{code}

Result
{code}
+-+--+
| row_key | data |
+-+--+
| [B@381ea162 | 
{"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="}
 |
{code}

3) Consider the following query -
{code}
select * from hbase.`part` as t order by t.data.p_name;
{code}

Expected
The query should return row_key, and all the columns in 'data' column family 
ordered by column 'data.p_name'

Actual
{code}
+--++
|   row_key|  data  |
+--++
| [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
+--++
{code}
Result contains only the row_key and column data.p_name, order by data.p_name

  was:
1) Consider a hbase table 'part' having column family 'data', which contains 
columns related to tpch part table
{code}
select * from hbase.`part`;
{code}

Result
{code}
+-+--+
| row_key | data |
+-+--+
| [B@381ea162 | 
{"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="}
 |
{code}

3) Consider the following query -
{code}
select * from hbase.`part` as t order by t.data.p_name;
{code}

Expected
The query should return row_key, and all the columns in 'data' column family

Actual
{code}
+--++
|   row_key|  data  |
+--++
| [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
+--++
{code}


> Using order by clause in a select * query on hbase table returns only the 
> row_key and order by field(s)
> ---
>
> Key: DRILL-5743
> URL: https://issues.apache.org/jira/browse/DRILL-5743
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - HBase
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> 1) Consider a hbase table 'part' having column family 'data', which contains 
> columns related to tpch part table
> {code}
> select * from hbase.`part`;
> {code}
> Result
> {code}
> +-+--+
> | row_key | data |
> +-+--+
> | [B@381ea162 | 
> {"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="}
>  |
> {code}
> 3) Consider the following query -
> {code}
> select * from hbase.`part` as t order by t.data.p_name;
> {code}
> Expected
> The query should return row_key, and all the columns in 'data' column family 
> ordered by column 'data.p_name'
> Actual
> {code}
> +--++
> |   row_key|  data  |
> +--++
> | [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
> +--++
> {code}
> Result contains only the row_key and column data.p_name, order by data.p_name



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

[jira] [Created] (DRILL-5743) Using order by clause in a select * query on hbase table returns only the row_key and order by field(s)

2017-08-27 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5743:


 Summary: Using order by clause in a select * query on hbase table 
returns only the row_key and order by field(s)
 Key: DRILL-5743
 URL: https://issues.apache.org/jira/browse/DRILL-5743
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - HBase
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


1) Consider a hbase table 'part' having column family 'data', which contains 
columns related to tpch part table
{code}
select * from hbase.`part`;
{code}

Result
{code}
+-+--+
| row_key | data |
+-+--+
| [B@381ea162 | 
{"p_brand":"QnJhbmQjNDU=","p_comment":"aW5hbCBkZXBvc2l0cy4gY2FyZWY=","p_container":"TEcgQk9Y","p_mfgr":"TWFudWZhY3R1cmVyIzQ=","p_name":"cG93ZGVyIGJyb3duIHNhbG1vbiBzZWFzaGVsbCBkaW0=","p_partkey":"OTk5OQ==","p_retailprice":"MTkwOC45OQ==","p_size":"OA==","p_type":"TEFSR0UgUE9MSVNIRUQgU1RFRUw="}
 |
{code}

3) Consider the following query -
{code}
select * from hbase.`part` as t order by t.data.p_name;
{code}

Expected
The query should return row_key, and all the columns in 'data' column family

Actual
{code}
+--++
|   row_key|  data  |
+--++
| [B@1bfcb7b6  | {"p_name":"eWVsbG93IHdoaXRlIHRhbiBraGFraSBzYWRkbGU="}  |
+--++
{code}



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

[jira] [Created] (DRILL-5742) CONVERT_FROM_JSON on a non-existing column in a file throws null pointer exception

2017-08-25 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5742:


 Summary: CONVERT_FROM_JSON on a non-existing column in a file 
throws null pointer exception
 Key: DRILL-5742
 URL: https://issues.apache.org/jira/browse/DRILL-5742
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


Query using CONVERT_FROM_JSON on a non-existing field.
{code}
SELECT CONVERT_FROM(columns[3], 'JSON') as col1 FROM dfs.`file1.tbl`;
{code}

The file above has only 3 columns.

Throws the below exception
{code}
Error: SYSTEM ERROR: NullPointerException

Fragment 0:0
{code}

Expected behavior - The query should return null, which is the behavior if we 
scan a non-existing field.



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

[jira] [Created] (DRILL-5724) Scan on a local directory containing multiple text files (one or more empty) throws FileNotFoundException

2017-08-16 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5724:


 Summary: Scan on a local directory containing multiple text files 
(one or more empty) throws FileNotFoundException
 Key: DRILL-5724
 URL: https://issues.apache.org/jira/browse/DRILL-5724
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - Text & CSV
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


1) Create a directory having multiple text files (one or more empty)
2) Do a scan on the directory
{code}
select * from lfs.`/home/user/dir1`;
{code}

The query throws the below error-
{code}
Error: SYSTEM ERROR: FileNotFoundException: File 
file:///home/user/dir1/ does not exist

Setup failed for CompliantTextRecordReader
Fragment 1:2
{code}

Issue reproducible with - csv, tsv and psv files



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

[jira] [Updated] (DRILL-5719) Join query on a non existing column in a json file runs longer than usual

2017-08-14 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5719:
-
Summary: Join query on a non existing column in a json file runs longer 
than usual  (was: Join query on a non existing column in a json file runs 
infinitely)

> Join query on a non existing column in a json file runs longer than usual
> -
>
> Key: DRILL-5719
> URL: https://issues.apache.org/jira/browse/DRILL-5719
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> 1) Join query on two json files
> {code}
> select t.partkey, t1.ps_partkey from dfs.`testData/part.json` as t RIGHT JOIN 
> dfs.`testData/partsupp.json` as t1 ON t.partkey = t1.ps_partkey;
> {code}
> The part_json file has no key by name partkey.
> Attached part.json & partsupp.json files



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

[jira] [Created] (DRILL-5719) Join query on a non existing column in a json file runs infinitely

2017-08-13 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5719:


 Summary: Join query on a non existing column in a json file runs 
infinitely
 Key: DRILL-5719
 URL: https://issues.apache.org/jira/browse/DRILL-5719
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - JSON
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


1) Join query on two json files
{code}
select t.partkey, t1.ps_partkey from dfs.`testData/part.json` as t RIGHT JOIN 
dfs.`testData/partsupp.json` as t1 ON t.partkey = t1.ps_partkey;
{code}
The part_json file has no key by name partkey.

Attached part.json & partsupp.json files



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

[jira] [Updated] (DRILL-5711) Incorrect operator profiles for queries on json files

2017-08-09 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5711:
-
Description: 
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type

Attached
1) Two json files
2) Snapshot of query profile and operator profile

Commit id - 9d1d815737528251a7500621cc976b57e7f3be59

  was:
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type

Attached
1) Two json files
2) Snapshot of query profile and operator profile


> Incorrect operator profiles for queries on json files
> -
>
> Key: DRILL-5711
> URL: https://issues.apache.org/jira/browse/DRILL-5711
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
> Attachments: OperatorProfiles.png, part.json, partsupp.json, 
> QueryProfile.png
>
>
> 1) Join query on two json files
> {code}
> select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
> dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
> {code}
> 2) Check the query profile
> a) JSON_SUB_SCAN type incorrectly ordered
> b) Missing SCREEN type
> Attached
> 1) Two json files
> 2) Snapshot of query profile and operator profile
> Commit id - 9d1d815737528251a7500621cc976b57e7f3be59



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

[jira] [Updated] (DRILL-5711) Incorrect operator profiles for queries on json files

2017-08-09 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5711:
-
Description: 
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type

Attached
1) Two json files
2) Snapshot of query profile and operator profile

  was:
1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part` as p, 
dfs.`testData/json/partsupp` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type


> Incorrect operator profiles for queries on json files
> -
>
> Key: DRILL-5711
> URL: https://issues.apache.org/jira/browse/DRILL-5711
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
> Attachments: OperatorProfiles.png, part.json, partsupp.json, 
> QueryProfile.png
>
>
> 1) Join query on two json files
> {code}
> select ps.ps_suppkey from dfs.`testData/json/part.josn` as p, 
> dfs.`testData/json/partsupp.json` as ps where p.p_partkey = ps.ps_partkey;
> {code}
> 2) Check the query profile
> a) JSON_SUB_SCAN type incorrectly ordered
> b) Missing SCREEN type
> Attached
> 1) Two json files
> 2) Snapshot of query profile and operator profile



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

[jira] [Updated] (DRILL-5711) Incorrect operator profiles for queries on json files

2017-08-09 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5711:
-
Attachment: OperatorProfiles.png
QueryProfile.png
part.json
partsupp.json

> Incorrect operator profiles for queries on json files
> -
>
> Key: DRILL-5711
> URL: https://issues.apache.org/jira/browse/DRILL-5711
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Storage - JSON
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
> Attachments: OperatorProfiles.png, part.json, partsupp.json, 
> QueryProfile.png
>
>
> 1) Join query on two json files
> {code}
> select ps.ps_suppkey from dfs.`testData/json/part` as p, 
> dfs.`testData/json/partsupp` as ps where p.p_partkey = ps.ps_partkey;
> {code}
> 2) Check the query profile
> a) JSON_SUB_SCAN type incorrectly ordered
> b) Missing SCREEN type



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

[jira] [Created] (DRILL-5711) Incorrect operator profiles for queries on json files

2017-08-09 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5711:


 Summary: Incorrect operator profiles for queries on json files
 Key: DRILL-5711
 URL: https://issues.apache.org/jira/browse/DRILL-5711
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - JSON
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


1) Join query on two json files
{code}
select ps.ps_suppkey from dfs.`testData/json/part` as p, 
dfs.`testData/json/partsupp` as ps where p.p_partkey = ps.ps_partkey;
{code}

2) Check the query profile
a) JSON_SUB_SCAN type incorrectly ordered
b) Missing SCREEN type



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

[jira] [Created] (DRILL-5706) Select * on hbase table having multiple regions(one or more empty) returns wrong result intermittently

2017-08-04 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5706:


 Summary: Select * on hbase table having multiple regions(one or 
more empty) returns wrong result intermittently
 Key: DRILL-5706
 URL: https://issues.apache.org/jira/browse/DRILL-5706
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - HBase
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


1) Create a hbase table with 4 regions
{code}
create 'myhbase', 'cf1', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col1','somedata'
put 'myhbase','c','cf1:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
select * from hbase.myhbase;
{code}
The query returns wrong result intermittently



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

[jira] [Updated] (DRILL-5705) Select * on hbase table having multiple regions and multiple schema returns wrong result

2017-08-04 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5705:
-
Description: 
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase','d','cf1:col1','somedata'
put 'myhbase','d','cf2:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.

  was:
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase','d','cf1:col1','somedata'
put 'myhbase','d','cf2:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.


> Select * on hbase table having multiple regions and multiple schema returns 
> wrong result
> 
>
> Key: DRILL-5705
> URL: https://issues.apache.org/jira/browse/DRILL-5705
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> Repro steps-
> 1) Create a hbase table with 4 regions-
> {code}
> create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
> put 'myhbase','a','cf1:col1','somedata'
> put 'myhbase','b','cf1:col2','somedata'
> put 'myhbase','c','cf2:col1','somedata'
> put 'myhbase','d','cf1:col1','somedata'
> put 'myhbase','d','cf2:col1','somedata'
> {code}
> 2) Run select * on the hbase table
> {code}
> select * from hbase.myhbase;
> {code}
> The query returns wrong result, and the result is not consistent across 
> multiple runs.



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

[jira] [Updated] (DRILL-5705) Select * on hbase table having multiple regions and multiple schema returns wrong result

2017-08-04 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5705:
-
Description: 
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase','d','cf1:col1','somedata'
put 'myhbase','d','cf2:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.

  was:
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase', 'd','cf1:col1','somedata'
put 'myhbase', 'd','cf2:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.


> Select * on hbase table having multiple regions and multiple schema returns 
> wrong result
> 
>
> Key: DRILL-5705
> URL: https://issues.apache.org/jira/browse/DRILL-5705
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> Repro steps-
> 1) Create a hbase table with 4 regions-
> {code}
> create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
> put 'myhbase','a','cf1:col1','somedata'
> put 'myhbase','b','cf1:col2','somedata'
> put 'myhbase','c','cf2:col1','somedata'
> put 'myhbase','d','cf1:col1','somedata'
> put 'myhbase','d','cf2:col1','somedata'
> {code}
> 2) Run select * on the hbase table
> {code}
> Select * from hbase.myhbase;
> {code}
> The query returns wrong result, and the result is not consistent across 
> multiple runs.



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

[jira] [Updated] (DRILL-5705) Select * on hbase table having multiple regions and multiple schema returns wrong result

2017-08-04 Thread Prasad Nagaraj Subramanya (JIRA)


 [ 
https://issues.apache.org/jira/browse/DRILL-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasad Nagaraj Subramanya updated DRILL-5705:
-
Description: 
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase', 'd','cf1:col1','somedata'
put 'myhbase', 'd','cf2:col1','somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.

  was:
Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase', 'd', 'cf1:col1', 'somedata'
put 'myhbase', 'd', 'cf2:col1', 'somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.


> Select * on hbase table having multiple regions and multiple schema returns 
> wrong result
> 
>
> Key: DRILL-5705
> URL: https://issues.apache.org/jira/browse/DRILL-5705
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.11.0
>Reporter: Prasad Nagaraj Subramanya
>
> Repro steps-
> 1) Create a hbase table with 4 regions-
> {code}
> create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
> put 'myhbase','a','cf1:col1','somedata'
> put 'myhbase','b','cf1:col2','somedata'
> put 'myhbase','c','cf2:col1','somedata'
> put 'myhbase', 'd','cf1:col1','somedata'
> put 'myhbase', 'd','cf2:col1','somedata'
> {code}
> 2) Run select * on the hbase table
> {code}
> Select * from hbase.myhbase;
> {code}
> The query returns wrong result, and the result is not consistent across 
> multiple runs.



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

[jira] [Created] (DRILL-5705) Select * on hbase table having multiple regions and multiple schema returns wrong result

2017-08-04 Thread Prasad Nagaraj Subramanya (JIRA)

Prasad Nagaraj Subramanya created DRILL-5705:


 Summary: Select * on hbase table having multiple regions and 
multiple schema returns wrong result
 Key: DRILL-5705
 URL: https://issues.apache.org/jira/browse/DRILL-5705
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.11.0
Reporter: Prasad Nagaraj Subramanya


Repro steps-

1) Create a hbase table with 4 regions-
{code}
create 'myhbase', 'cf1','cf2', {SPLITS => ['a', 'b', 'c']}
put 'myhbase','a','cf1:col1','somedata'
put 'myhbase','b','cf1:col2','somedata'
put 'myhbase','c','cf2:col1','somedata'
put 'myhbase', 'd', 'cf1:col1', 'somedata'
put 'myhbase', 'd', 'cf2:col1', 'somedata'
{code}

2) Run select * on the hbase table
{code}
Select * from hbase.myhbase;
{code}

The query returns wrong result, and the result is not consistent across 
multiple runs.



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

53 matches

Mail list logo