date:20170410

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

2017-04-10 Thread Jinfeng Ni (JIRA)


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

Jinfeng Ni commented on DRILL-5327:
---

The root cause of the problem seems to be in UnionAll operator, which would 
replace the incoming batches' schema with optional:int typed columns, when both 
sides contains 0-row batch (with proper schema). The bug seems to be introduced 
by DRILL-4476. 

DRILL-4510 was opened to fix the problem, but seems to me the fix in PR is not 
right; we should not force union all operator to be in a single thread. 

The basic rule for UnionAll is quite simple. If any side of input to UnionAll 
has schema, even though rowcount = 0, UnionAll should not discard such schema 
information by injecting an optional:int column.  Unfortunately,  the fix of 
DRILL-4476 violates that, and hence causing various of issues. 

> Hash aggregate can return empty batch which can cause schema change exception
> -
>
> Key: DRILL-5327
> URL: https://issues.apache.org/jira/browse/DRILL-5327
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Drill
>Affects Versions: 1.10.0
>Reporter: Chun Chang
>Assignee: Jinfeng Ni
> Attachments: 271dbe08-c725-8e82-b6ea-53e9dab64e8b.sys.drill
>
>
> Hash aggregate can return empty batches which cause drill to throw schema 
> change exception (not handling this type of schema change). This is not a new 
> bug. But a recent hash function change (a theoretically correct change) may 
> have increased the chance of hitting this issue. I don't have scientific data 
> to support my claim (in fact I don't believe it's the case), but a regular 
> regression run used to pass fails now due to this bug. My concern is that 
> existing drill users out there may have queries that used to work but fail 
> now. It will be difficult to explain why the new release is better for them. 
> I put this bug as blocker so we can discuss it before releasing 1.10.
> {noformat}
> /root/drillAutomation/framework-master/framework/resources/Advanced/tpcds/tpcds_sf1/original/text/query66.sql
> Query: 
> -- start query 66 in stream 0 using template query66.tpl 
> SELECT w_warehouse_name, 
>w_warehouse_sq_ft, 
>w_city, 
>w_county, 
>w_state, 
>w_country, 
>ship_carriers, 
>year1,
>Sum(jan_sales) AS jan_sales, 
>Sum(feb_sales) AS feb_sales, 
>Sum(mar_sales) AS mar_sales, 
>Sum(apr_sales) AS apr_sales, 
>Sum(may_sales) AS may_sales, 
>Sum(jun_sales) AS jun_sales, 
>Sum(jul_sales) AS jul_sales, 
>Sum(aug_sales) AS aug_sales, 
>Sum(sep_sales) AS sep_sales, 
>Sum(oct_sales) AS oct_sales, 
>Sum(nov_sales) AS nov_sales, 
>Sum(dec_sales) AS dec_sales, 
>Sum(jan_sales / w_warehouse_sq_ft) AS jan_sales_per_sq_foot, 
>Sum(feb_sales / w_warehouse_sq_ft) AS feb_sales_per_sq_foot, 
>Sum(mar_sales / w_warehouse_sq_ft) AS mar_sales_per_sq_foot, 
>Sum(apr_sales / w_warehouse_sq_ft) AS apr_sales_per_sq_foot, 
>Sum(may_sales / w_warehouse_sq_ft) AS may_sales_per_sq_foot, 
>Sum(jun_sales / w_warehouse_sq_ft) AS jun_sales_per_sq_foot, 
>Sum(jul_sales / w_warehouse_sq_ft) AS jul_sales_per_sq_foot, 
>Sum(aug_sales / w_warehouse_sq_ft) AS aug_sales_per_sq_foot, 
>Sum(sep_sales / w_warehouse_sq_ft) AS sep_sales_per_sq_foot, 
>Sum(oct_sales / w_warehouse_sq_ft) AS oct_sales_per_sq_foot, 
>Sum(nov_sales / w_warehouse_sq_ft) AS nov_sales_per_sq_foot, 
>Sum(dec_sales / w_warehouse_sq_ft) AS dec_sales_per_sq_foot, 
>Sum(jan_net)   AS jan_net, 
>Sum(feb_net)   AS feb_net, 
>Sum(mar_net)   AS mar_net, 
>Sum(apr_net)   AS apr_net, 
>Sum(may_net)   AS may_net, 
>Sum(jun_net)   AS jun_net, 
>Sum(jul_net)   AS jul_net, 
>Sum(aug_net)   AS aug_net, 
>Sum(sep_net)   AS sep_net, 
>Sum(oct_net)

[jira] [Updated] (DRILL-5409) Update MapR version to 5.2.1-mapr

2017-04-10 Thread Abhishek Girish (JIRA)


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

Abhishek Girish updated DRILL-5409:
---
Labels: ready-to-commit  (was: )

> Update MapR version to 5.2.1-mapr
> -
>
> Key: DRILL-5409
> URL: https://issues.apache.org/jira/browse/DRILL-5409
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Tools, Build & Test
>Affects Versions: 1.11.0
>Reporter: Abhishek Girish
>Assignee: Patrick Wong
>  Labels: ready-to-commit
> Fix For: 1.11.0
>
>
> This if for the "mapr" profile. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-5409) Update MapR version to 5.2.1-mapr

2017-04-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on DRILL-5409:
---

Github user Agirish commented on the issue:

https://github.com/apache/drill/pull/813
  
+1


> Update MapR version to 5.2.1-mapr
> -
>
> Key: DRILL-5409
> URL: https://issues.apache.org/jira/browse/DRILL-5409
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Tools, Build & Test
>Affects Versions: 1.11.0
>Reporter: Abhishek Girish
>Assignee: Patrick Wong
> Fix For: 1.11.0
>
>
> This if for the "mapr" profile. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-5409) Update MapR version to 5.2.1-mapr

2017-04-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on DRILL-5409:
---

GitHub user pwong-mapr opened a pull request:

https://github.com/apache/drill/pull/813

DRILL-5409 - update MapR version to 5.2.1



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pwong-mapr/incubator-drill patch-5

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/drill/pull/813.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #813


commit 5c5656ee551a5200fe30f28515146536cf919a98
Author: Patrick Wong 
Date:   2017-04-10T22:45:14Z

DRILL-5409 - update MapR version to 5.2.1




> Update MapR version to 5.2.1-mapr
> -
>
> Key: DRILL-5409
> URL: https://issues.apache.org/jira/browse/DRILL-5409
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Tools, Build & Test
>Affects Versions: 1.11.0
>Reporter: Abhishek Girish
>Assignee: Patrick Wong
> Fix For: 1.11.0
>
>
> This if for the "mapr" profile. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DRILL-5415) Improve Fixture Builder to configure client properties and keep collection type properties for server

2017-04-10 Thread Sorabh Hamirwasia (JIRA)


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

Sorabh Hamirwasia updated DRILL-5415:
-
Labels: ready-to-commit  (was: )

> Improve Fixture Builder to configure client properties and keep collection 
> type properties for server
> -
>
> Key: DRILL-5415
> URL: https://issues.apache.org/jira/browse/DRILL-5415
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Tools, Build & Test
>Affects Versions: 1.11.0
>Reporter: Sorabh Hamirwasia
>Assignee: Sorabh Hamirwasia
>Priority: Minor
>  Labels: ready-to-commit
> Fix For: 1.11.0
>
>
> There are 2 improvements which are made as part of this pull request.
> 1) The Fixture Builder framework converts all the config properties for 
> Drillbit into string type. But there are certain configurations for 
> authentication (like auth.mechanism) which are expected to be list type. Thus 
> there will be failure during type check. Change to keep collections type 
> config value as is and insert those config value after string types are 
> inserted.
> 2) The Fixture Builder framework when builds it tries to apply any system 
> options / session options (if set) for which it creates a default client. 
> Hence with  cluster enabled for authentication this default client will not 
> provide any connection parameters for authentication and will fail to 
> connect. Allow Fixture Builder to accept client related properties as well so 
> that can be used while creating default client to connect to cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (DRILL-4908) Unable to setup Sybase JDBC Plugin with access to multiple databases

2017-04-10 Thread David Lee (JIRA)


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

David Lee closed DRILL-4908.

Resolution: Duplicate

Closing this issue and reopening it as part of Drill 1.10 with new examples.. 
The behavior in Drill 1.10 is different now and this use case cannot be 
reproduced with the example included.

> Unable to setup Sybase JDBC Plugin with access to multiple databases
> 
>
> Key: DRILL-4908
> URL: https://issues.apache.org/jira/browse/DRILL-4908
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: SQL Parser
>Affects Versions: 1.8.0
> Environment: linux, sybase ase, sybase iq, windows
>Reporter: David Lee
> Fix For: Future
>
>
> This may also be a problem with Microsoft SQL Server which uses the same SQL 
> Syntax.
> I am unable to setup a single JDBC plugin which allows me to query tables on 
> different databases on the server.
> I can setup multiple JDBC plugins for each database on the server and join 
> data across multiple JDBC connections, but this is extremely inefficient and 
> SQL queries 
> just hang.
> Test Case: Create two tables on two different databases and write a single 
> SQL statement to join them together. Try to replicate the results in Apache 
> Drill.
> A. Temp tables in Sybase:
> use tempdb
> go
> create table phone_book
> (
> first_name varchar(10),
> last_name varchar(20),
> phone_number varchar(12)
> )
> go
> insert phone_book values ('Bob','Marley','555-555-')
> insert phone_book values ('Mary','Jane','111-111-')
> insert phone_book values ('Bat','Man','911-911-')
> go
> use tempdb_adhoc
> go
> create table cities
> (
> first_name varchar(10),
> last_name varchar(20),
> city varchar(20)
> )
> go
> insert cities values ('Bob','Marley','San Francisco')
> insert cities values ('Mary','Jane','New York')
> insert cities values ('Bat','Man','Gotham')
> go
> select a.first_name, a.last_name, a.phone_number, b.city
> from tempdb.guest.phone_book a
> join tempdb_adhoc.guest.cities b
> on b.first_name = a.first_name
> and b.last_name = a.last_name
> go
> Returns Back in SYBASE ISQL:
>  first_name last_namephone_number city   
>  --   
>  BobMarley   555-555- San Francisco
>  Mary   Jane 111-111- New York
>  BatMan  911-911- Gotham
> B. Drill JDBC Plugin Setups:
> DEV:
> {
>   "type": "jdbc",
>   "driver": "com.sybase.jdbc4.jdbc.SybDriver",
>   "url": "jdbc:sybase:Tds:my_server:4100",
>   "username": "my_login",
>   "password": "my_password",
>   "enabled": true
> }
> DEV_TEMPDB:
> {
>   "type": "jdbc",
>   "driver": "com.sybase.jdbc4.jdbc.SybDriver",
>   "url": "jdbc:sybase:Tds:my_server:4100/tempdb",
>   "username": "my_login",
>   "password": "my_password",
>   "enabled": true
> }
> DEV_TEMPDB_ADHOC:
> {
>   "type": "jdbc",
>   "driver": "com.sybase.jdbc4.jdbc.SybDriver",
>   "url": "jdbc:sybase:Tds:my_server:4100/tempdb_adhoc",
>   "username": "my_login",
>   "password": "my_password",
>   "enabled": true
> }
> C. Examples of Drill Statements which work and don't work.
> 1. Returns back redundant schemas for each JDBC plugin:
> 0: jdbc:drill:zk=local> show schemas;
> +--+
> | SCHEMA_NAME  |
> +--+
> | DEV.tempdb   |
> | DEV.tempdb_adhoc |
> | DEV_TEMPDB.tempdb|
> | DEV_TEMPDB.tempdb_adhoc  |
> | DEV_TEMPDB_ADHOC.tempdb  |
> | DEV_TEMPDB_ADHOC.tempdb_adhoc|
> +--+
> 2. SQL selects work within schemas and joins across schemas:
> 0: jdbc:drill:zk=local> select * from DEV_TEMPDB.tempdb.guest.phone_book;
> +-++---+
> | first_name  | last_name  | phone_number  |
> +-++---+
> | Bob | Marley | 555-555-  |
> | Mary| Jane   | 111-111-  |
> | Bat | Man| 911-911-  |
> +-++---+
> 3 rows selected (1.585 seconds)
> 0: jdbc:drill:zk=local> select * from 
> DEV_TEMPDB_ADHOC.tempdb_adhoc.guest.cities;
> ;
> +-+++
> | first_name  | last_name  |  city  |
> +-+++
> | Bob | Marley | San Francisco  |
> | Mary| Jane   | New York   |
> | Bat | Man| Gotham |
> +-+++
> 3 rows selected (1.173 seconds)
> 0: jdbc:drill:zk=local> select a.first_name, a.last_name, a.phone_number, 
> b.city
> . . . . . . . . . . .

[jira] [Updated] (DRILL-5427) SQL Execution Syntax incorrect for Sybase RDBMS

2017-04-10 Thread David Lee (JIRA)


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

David Lee updated DRILL-5427:
-
Description: 
The Sybase table syntax should be "database"."owner"."tablename", but "owner" 
is not being added which produces incorrect SQL when executed.

The default owner is "DBO" for most tables. If DBO is omitted then the syntax 
should be just "database".."tablename" 

When SYBASE sees  "database".."tablename" it:

A. Checks if there is a tablename owned by the logged in user.
B. If there is no tablename owned by the logged in user it uses DBO by default

This is what I'm seeing using a JDBC plug-in connection to Sybase ASE:

The following statements work fine:

A. show schemas

SCHEMA_NAME
cp.default
dfs.default
dfs.root
dfs.tmp
INFORMATION_SCHEMA
SYB1U
SYB1U.tempdb

B. use SYB1U.tempdb

ok  summary
trueDefault schema changed to [SYB1U.tempdb]

C. show tables

TABLE_SCHEMATABLE_NAME
SYB1U.tempdbsysalternates
SYB1U.tempdbsysattributes
SYB1U.tempdbsyscolumns
SYB1U.tempdbsyscomments
SYB1U.tempdbsysconstraints
etc.. etc.. etc..

D. SELECT * FROM INFORMATION_SCHEMA.`COLUMNS`
where TABLE_SCHEMA = 'SYB1U.tempdb'
and TABLE_NAME = 'syscolumns'

TABLE_CATALOG   TABLE_SCHEMATABLE_NAME  COLUMN_NAME 
ORDINAL_POSITIONCOLUMN_DEFAULT  IS_NULLABLE DATA_TYPE
DRILL   SYB1U.tempdbsyscolumns  id  1   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  number  2   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  colid   3   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  status  4   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  type5   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  length  6   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  offset  7   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  usertype8   (null)  NO  
SMALLINT
DRILL   SYB1U.tempdbsyscolumns  cdefault9   (null)  NO  
INTEGER
DRILL   SYB1U.tempdbsyscolumns  domain  10  (null)  NO  INTEGER
etc.. etc.. etc..

However, the following statements fail:

A. select * from SYB1U.tempdb.syscolumns
DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL 
query. 
sql SELECT *
FROM "tempdb"."syscolumns"
plugin SYB1U
Fragment 0:0

B. select * from SYB1U.tempdb.dbo.syscolumns
VALIDATION ERROR: From line 1, column 15 to line 1, column 19: Table 
'SYB1U.tempdb.dbo.syscolumns' not found

C. select * from SYB1U.tempdb..syscolumns
PARSE ERROR: Encountered ".." at line 1, column 27.

In A, the execution engine doesn't include the "owner" portion.
In B, adding dbo fails validation
In C, the default behavior in Sybase for ".." isn't recognized

I'm not sure if this is a Drill issue or a Calcite issue.

  was:
The Sybase table syntax should be "database"."owner"."tablename", but "owner" 
is not being added which produces incorrect SQL when executed.

The default owner is "DBO" for most tables. If DBO is omitted then the syntax 
should be just "database".."tablename" 

When SYBASE sees  "database".."tablename" it:

A. Checks if there is a tablename owned by the logged in user.
B. If there is no tablename owned by the logged in user it uses DBO by default

This is what I'm seeing using a JDBC plug-in connection to Sybase ASE:

The following statements work fine:

A. show schemas

SCHEMA_NAME
cp.default
dfs.default
dfs.root
dfs.tmp
INFORMATION_SCHEMA
SYB1U
SYB1U.tempdb

B. use SYB1U.tempdb

ok  summary
trueDefault schema changed to [SYB1U.tempdb]

C. show tables

TABLE_SCHEMATABLE_NAME
SYB1U.tempdbsysalternates
SYB1U.tempdbsysattributes
SYB1U.tempdbsyscolumns
SYB1U.tempdbsyscomments
SYB1U.tempdbsysconstraints
etc.. etc.. etc..

D. SELECT * FROM INFORMATION_SCHEMA.`COLUMNS`
where TABLE_SCHEMA = 'SYB1U.tempdb'
and TABLE_NAME = 'syscolumns'

TABLE_CATALOG   TABLE_SCHEMATABLE_NAME  COLUMN_NAME 
ORDINAL_POSITIONCOLUMN_DEFAULT  IS_NULLABLE DATA_TYPE
DRILL   SYB1U.tempdbsyscolumns  id  1   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  number  2   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  colid   3   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  status  4   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  type5   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  length  6   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  offset  7   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  usertype8   (null)  NO  
SMALLINT
DRILL   SYB1U.tempdbsyscolumns  cdefault9   (null)  NO  
INTEGER
DRILL   SYB1U.tempdbsyscolumns  domain  10  (null)  NO  INTEGER

[jira] [Created] (DRILL-5427) SQL Execution Syntax incorrect for Sybase RDBMS

2017-04-10 Thread David Lee (JIRA)

David Lee created DRILL-5427:


 Summary: SQL Execution Syntax incorrect for Sybase RDBMS
 Key: DRILL-5427
 URL: https://issues.apache.org/jira/browse/DRILL-5427
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - JDBC, SQL Parser, Storage - JDBC
Affects Versions: 1.10.0
 Environment: Windows Linux
Reporter: David Lee
 Fix For: Future, 1.10.0


The Sybase table syntax should be "database"."owner"."tablename", but "owner" 
is not being added which produces incorrect SQL when executed.

The default owner is "DBO" for most tables. If DBO is omitted then the syntax 
should be just "database".."tablename" 

When SYBASE sees  "database".."tablename" it:

A. Checks if there is a tablename owned by the logged in user.
B. If there is no tablename owned by the logged in user it uses DBO by default

This is what I'm seeing using a JDBC plug-in connection to Sybase ASE:

The following statements work fine:

A. show schemas

SCHEMA_NAME
cp.default
dfs.default
dfs.root
dfs.tmp
INFORMATION_SCHEMA
SYB1U
SYB1U.tempdb

B. use SYB1U.tempdb

ok  summary
trueDefault schema changed to [SYB1U.tempdb]

C. show tables

TABLE_SCHEMATABLE_NAME
SYB1U.tempdbsysalternates
SYB1U.tempdbsysattributes
SYB1U.tempdbsyscolumns
SYB1U.tempdbsyscomments
SYB1U.tempdbsysconstraints
etc.. etc.. etc..

D. SELECT * FROM INFORMATION_SCHEMA.`COLUMNS`
where TABLE_SCHEMA = 'SYB1U.tempdb'
and TABLE_NAME = 'syscolumns'

TABLE_CATALOG   TABLE_SCHEMATABLE_NAME  COLUMN_NAME 
ORDINAL_POSITIONCOLUMN_DEFAULT  IS_NULLABLE DATA_TYPE
DRILL   SYB1U.tempdbsyscolumns  id  1   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  number  2   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  colid   3   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  status  4   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  type5   (null)  NO  TINYINT
DRILL   SYB1U.tempdbsyscolumns  length  6   (null)  NO  INTEGER
DRILL   SYB1U.tempdbsyscolumns  offset  7   (null)  NO  SMALLINT
DRILL   SYB1U.tempdbsyscolumns  usertype8   (null)  NO  
SMALLINT
DRILL   SYB1U.tempdbsyscolumns  cdefault9   (null)  NO  
INTEGER
DRILL   SYB1U.tempdbsyscolumns  domain  10  (null)  NO  INTEGER
etc.. etc.. etc..

However, the following statements fail:

A. select * from SYB1U.tempdb.syscolumns
DATA_READ ERROR: The JDBC storage plugin failed while trying setup the SQL 
query. 
sql SELECT *
FROM "tempdb"."syscolumns"
plugin SYB1U
Fragment 0:0

B. select * from SYB1U.tempdb.dbo.syscolumns
VALIDATION ERROR: From line 1, column 15 to line 1, column 19: Table 
'SYB1U.tempdb.dbo.syscolumns' not found

C. select * from SYB1U.tempdb..syscolumns
PARSE ERROR: Encountered ".." at line 1, column 27.

In A, the execution engine doesn't include the "owner" portion.
In B, adding dbo fails validation
In C, the default behavior in Sybase for ".." isn't recognized




use SYB1U.tempdb

show tables

SELECT *
FROM INFORMATION_SCHEMA.`COLUMNS`
where TABLE_SCHEMA = 'SYB1U.tempdb'
and TABLE_NAME = 'syscolumns'

I'm not sure if this is a Drill issue or a Calcite issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (DRILL-5213) Prepared statement for actual query is missing the query text

2017-04-10 Thread Zelaine Fong (JIRA)


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

Zelaine Fong reassigned DRILL-5213:
---

Assignee: Vitalii Diravka
Reviewer: Arina Ielchiieva

Assigned Reviewer to [~arina]

> Prepared statement for actual query is missing the query text
> -
>
> Key: DRILL-5213
> URL: https://issues.apache.org/jira/browse/DRILL-5213
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Affects Versions: 1.10.0
>Reporter: Krystal
>Assignee: Vitalii Diravka
>
> Prepared statement for actual query is missing the query text in the query's 
> profile.  As a result, there is no link for the query profile from the UI.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-5213) Prepared statement for actual query is missing the query text

2017-04-10 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on DRILL-5213:
---

GitHub user vdiravka opened a pull request:

https://github.com/apache/drill/pull/812

DRILL-5213: Prepared statement for actual query is missing the query text



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/vdiravka/drill DRILL-5213

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/drill/pull/812.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #812


commit adc9dad014961063b56644fca8ec8a040895b020
Author: Vitalii Diravka 
Date:   2017-04-10T18:54:21Z

DRILL-5213: Prepared statement for actual query is missing the query text




> Prepared statement for actual query is missing the query text
> -
>
> Key: DRILL-5213
> URL: https://issues.apache.org/jira/browse/DRILL-5213
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Metadata
>Affects Versions: 1.10.0
>Reporter: Krystal
>
> Prepared statement for actual query is missing the query text in the query's 
> profile.  As a result, there is no link for the query profile from the UI.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DRILL-5426) Queries fail with "RESOURCE ERROR: Failed to create schema tree." when Impersonation is enabled

2017-04-10 Thread Abhishek Girish (JIRA)


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

Abhishek Girish updated DRILL-5426:
---
Attachment: drillbit.log.txt

> Queries fail with "RESOURCE ERROR: Failed to create schema tree." when 
> Impersonation is enabled
> ---
>
> Key: DRILL-5426
> URL: https://issues.apache.org/jira/browse/DRILL-5426
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Client - CLI, Client - HTTP, Client - JDBC, Tools, Build 
> & Test
>Affects Versions: 1.9.0, 1.10.0, 1.11.0
> Environment: DFS connected to MapR FileSystem
>Reporter: Abhishek Girish
>Priority: Minor
>  Labels: impersonation, usability
> Attachments: drillbit.log.txt
>
>
> When Drillbit impersonation is enabled and clients connect without specifying 
> the username (and password), queries fails to execute:
> {code}
> # $DRILL_HOME/bin/sqlline -u "jdbc:drill:zk=localhost:5181" 
> sqlline> select * from sys.drillbits;
> User Error Occurred
> org.apache.drill.common.exceptions.UserException: RESOURCE ERROR: Failed to 
> create schema tree.
> {code} 
>  
> The error disappears when username is specified:
> {code}
> # $DRILL_HOME/bin/sqlline -u "jdbc:drill:zk=localhost:5181" -n root -p root
> sqlline> select * from sys.drillbits;
> SUCCESS
> {code}
> Log attached. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (DRILL-5426) Queries fail with "RESOURCE ERROR: Failed to create schema tree." when Impersonation is enabled

2017-04-10 Thread Abhishek Girish (JIRA)

Abhishek Girish created DRILL-5426:
--

 Summary: Queries fail with "RESOURCE ERROR: Failed to create 
schema tree." when Impersonation is enabled
 Key: DRILL-5426
 URL: https://issues.apache.org/jira/browse/DRILL-5426
 Project: Apache Drill
  Issue Type: Bug
  Components: Client - CLI, Client - HTTP, Client - JDBC, Tools, Build 
& Test
Affects Versions: 1.10.0, 1.9.0, 1.11.0
 Environment: DFS connected to MapR FileSystem
Reporter: Abhishek Girish
Priority: Minor


When Drillbit impersonation is enabled and clients connect without specifying 
the username (and password), queries fails to execute:

{code}
# $DRILL_HOME/bin/sqlline -u "jdbc:drill:zk=localhost:5181" 
sqlline> select * from sys.drillbits;
User Error Occurred
org.apache.drill.common.exceptions.UserException: RESOURCE ERROR: Failed to 
create schema tree.
{code} 
 
The error disappears when username is specified:
{code}
# $DRILL_HOME/bin/sqlline -u "jdbc:drill:zk=localhost:5181" -n root -p root
sqlline> select * from sys.drillbits;
SUCCESS
{code}

Log attached. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DRILL-5005) Potential issues with external sort info in query profile

2017-04-10 Thread Kunal Khatua (JIRA)


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

Kunal Khatua updated DRILL-5005:

Reviewer: Rahul Challapalli

> Potential issues with external sort info in query profile
> -
>
> Key: DRILL-5005
> URL: https://issues.apache.org/jira/browse/DRILL-5005
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: Paul Rogers
>Assignee: Paul Rogers
>Priority: Minor
> Fix For: 1.11.0
>
>
> Run a query that will include an external sort.
> Look at the visualized plan. The external sort is shown in the tree as just 
> "Sort". Suggestion: say "External Sort".
> In the operator profiles section, memory use for EXTERNAL_SORT is listed as 
> 26MB. Yet the file being sorted is 388 MB. Even allowing for projects of a 
> subset of column, 26 MB seems awfully small to hold the data set. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (DRILL-5032) Drill query on hive parquet table failed with OutOfMemoryError: Java heap space

2017-04-10 Thread Rahul Challapalli (JIRA)


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

Rahul Challapalli closed DRILL-5032.


Forgot to close the issue

> Drill query on hive parquet table failed with OutOfMemoryError: Java heap 
> space
> ---
>
> Key: DRILL-5032
> URL: https://issues.apache.org/jira/browse/DRILL-5032
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Functions - Hive
>Affects Versions: 1.8.0
>Reporter: Serhii Harnyk
>Assignee: Serhii Harnyk
> Fix For: 1.10.0
>
> Attachments: plan, plan with fix
>
>
> Following query on hive parquet table failed with OOM Java heap space:
> {code}
> select distinct(businessdate) from vmdr_trades where trade_date='2016-04-12'
> 2016-08-31 08:02:03,597 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.drill.exec.work.foreman.Foreman - Query text for query id 
> 283938c3-fde8-0fc6-37e1-9a568c7f5913: select distinct(businessdate) from 
> vmdr_trades where trade_date='2016-04-12'
> 2016-08-31 08:05:58,502 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Beginning partition pruning, pruning 
> class: 
> org.apache.drill.exec.planner.sql.logical.HivePushPartitionFilterIntoScan$2
> 2016-08-31 08:05:58,506 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Total elapsed time to build and analyze 
> filter tree: 1 ms
> 2016-08-31 08:05:58,506 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - No conditions were found eligible for 
> partition pruning.Total pruning elapsed time: 3 ms
> 2016-08-31 08:05:58,663 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Beginning partition pruning, pruning 
> class: 
> org.apache.drill.exec.planner.sql.logical.HivePushPartitionFilterIntoScan$2
> 2016-08-31 08:05:58,663 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Total elapsed time to build and analyze 
> filter tree: 0 ms
> 2016-08-31 08:05:58,663 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - No conditions were found eligible for 
> partition pruning.Total pruning elapsed time: 0 ms
> 2016-08-31 08:05:58,664 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Beginning partition pruning, pruning 
> class: 
> org.apache.drill.exec.planner.sql.logical.HivePushPartitionFilterIntoScan$1
> 2016-08-31 08:05:58,665 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - Total elapsed time to build and analyze 
> filter tree: 0 ms
> 2016-08-31 08:05:58,665 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] INFO  
> o.a.d.e.p.l.partition.PruneScanRule - No conditions were found eligible for 
> partition pruning.Total pruning elapsed time: 0 ms
> 2016-08-31 08:09:42,355 [283938c3-fde8-0fc6-37e1-9a568c7f5913:foreman] ERROR 
> o.a.drill.common.CatastrophicFailure - Catastrophic Failure Occurred, 
> exiting. Information message: Unable to handle out of memory condition in 
> Foreman.
> java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:3332) ~[na:1.8.0_74]
> at 
> java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137)
>  ~[na:1.8.0_74]
> at 
> java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121)
>  ~[na:1.8.0_74]
> at 
> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:421) 
> ~[na:1.8.0_74]
> at java.lang.StringBuilder.append(StringBuilder.java:136) 
> ~[na:1.8.0_74]
> at java.lang.StringBuilder.append(StringBuilder.java:76) 
> ~[na:1.8.0_74]
> at 
> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:457) 
> ~[na:1.8.0_74]
> at java.lang.StringBuilder.append(StringBuilder.java:166) 
> ~[na:1.8.0_74]
> at java.lang.StringBuilder.append(StringBuilder.java:76) 
> ~[na:1.8.0_74]
> at 
> com.google.protobuf.TextFormat$TextGenerator.write(TextFormat.java:538) 
> ~[protobuf-java-2.5.0.jar:na]
> at 
> com.google.protobuf.TextFormat$TextGenerator.print(TextFormat.java:526) 
> ~[protobuf-java-2.5.0.jar:na]
> at 
> com.google.protobuf.TextFormat$Printer.printFieldValue(TextFormat.java:389) 
> ~[protobuf-java-2.5.0.jar:na]
> at 
> com.google.protobuf.TextFormat$Printer.printSingleField(TextFormat.java:327) 
> ~[protobuf-java-2.5.0.jar:na]
> at 
> com.google.protobuf.TextFormat$Printer.printField(TextFormat.java:286) 
> ~[protobuf-java-2.5.0.jar:na]
> at com.google.protobuf.TextFormat$Printer.print(TextFormat.java:273) 
>

[jira] [Closed] (DRILL-5065) Optimize count(*) queries on MapR-DB JSON Tables

2017-04-10 Thread Abhishek Girish (JIRA)


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

Abhishek Girish closed DRILL-5065.
--

> Optimize count(*) queries on MapR-DB JSON Tables
> 
>
> Key: DRILL-5065
> URL: https://issues.apache.org/jira/browse/DRILL-5065
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Storage - MapRDB
>Affects Versions: 1.9.0
> Environment: Clusters with MapR v5.2.0 and above
>Reporter: Abhishek Girish
>Assignee: Smidth Panchamia
>  Labels: ready-to-commit
> Fix For: 1.10.0
>
>
> The JSON FileReader optimizes count(* ) queries, by only counting the number 
> of records in the files and discarding the data. This makes the query 
> execution faster & efficient. 
> We need a similar feature in the MapR format plugin (maprdb) to optimize _id 
> only projection & count(* ) queries on MapR-DB JSON Tables.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (DRILL-5094) Assure Comparator to be transitive

2017-04-10 Thread Abhishek Girish (JIRA)


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

Abhishek Girish closed DRILL-5094.
--

> Assure Comparator to be transitive
> --
>
> Key: DRILL-5094
> URL: https://issues.apache.org/jira/browse/DRILL-5094
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Chunhui Shi
>Assignee: Chunhui Shi
>Priority: Critical
>  Labels: ready-to-commit
> Fix For: 1.10.0
>
>
> In AssignmentCreator.java, one Comparator could break transitive attribute 
> required for a Comparator implementation and the result is not correct.
> E.g. for:
> long IntPlusOne = 0x8000L;
> [0]=2 * IntPlusOne + 5, [1] = 2* IntPlusOne + 8, [2] = 4 * IntPlusOne + 4,
> the compare results will be like:
> compare([0],[1]) = -3,
> compare([1],[2]) = 4,
> compare([0],[2]) = 1 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (DRILL-5304) Queries fail intermittently when there is skew in data distribution

2017-04-10 Thread Abhishek Girish (JIRA)


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

Abhishek Girish closed DRILL-5304.
--

> Queries fail intermittently when there is skew in data distribution
> ---
>
> Key: DRILL-5304
> URL: https://issues.apache.org/jira/browse/DRILL-5304
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Query Planning & Optimization
>Affects Versions: 1.10.0
>Reporter: Abhishek Girish
>Assignee: Padma Penumarthy
>  Labels: ready-to-commit
> Fix For: 1.10.0
>
> Attachments: query1_drillbit.log.txt, query2_drillbit.log.txt
>
>
> In a distributed environment, we've observed certain queries to fail 
> execution intermittently, with an assignment logic issue, when the underlying 
> data is skewed w.r.t distribution. 
> For example the TPC-H [query 
> 7|https://github.com/mapr/drill-test-framework/blob/master/framework/resources/Advanced/tpch/tpch_sf100/parquet/07.q]
>  failed with the below error:
> {code}
> java.sql.SQLException: SYSTEM ERROR: IllegalArgumentException: 
> MinorFragmentId 105 has no read entries assigned
> ...
>   (org.apache.drill.exec.work.foreman.ForemanException) Unexpected exception 
> during fragment initialization: MinorFragmentId 105 has no read entries 
> assigned
> org.apache.drill.exec.work.foreman.Foreman.run():281
> java.util.concurrent.ThreadPoolExecutor.runWorker():1145
> java.util.concurrent.ThreadPoolExecutor$Worker.run():615
> java.lang.Thread.run():744
>   Caused By (java.lang.IllegalArgumentException) MinorFragmentId 105 has no 
> read entries assigned
> {code}
> Log containing full stack trace is attached.
> And for this query, the underlying TPC-H SF100 Parquet dataset was observed 
> to be located mostly only on 2-3 nodes on an 8 node DFS environment. The data 
> distribution skew on this cluster is most likely the triggering factor for 
> this case, as the same query, on the same dataset does not show this failure 
> on a different test cluster (with possibly different data distribution). 
> Also, another 
> [query|https://github.com/mapr/drill-test-framework/blob/master/framework/resources/Functional/limit0/window_functions/bugs/data/drill-3700.sql]
>  failed with a similar error when slice target was set to 1. 
> {code}
> Failed with exception
> java.sql.SQLException: SYSTEM ERROR: IllegalArgumentException: 
> MinorFragmentId 66 has no read entries assigned
> ...
>   (org.apache.drill.exec.work.foreman.ForemanException) Unexpected exception 
> during fragment initialization: MinorFragmentId 66 has no read entries 
> assigned
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (DRILL-4280) Kerberos Authentication

2017-04-10 Thread Sudheesh Katkam (JIRA)


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

Sudheesh Katkam edited comment on DRILL-4280 at 4/10/17 5:20 PM:
-

Hi [~djc0604], Kerberos SPNEGO support was not included as part of resolving 
this ticket, and so Drill cannot be enabled only with Kerberos if web server is 
required. PLAIN also needs to be enabled. Accordingly, I opened DRILL-5425.


was (Author: sudheeshkatkam):
Hi [~djc0604], Kerberos SPNEGO support was not included as part of this ticket, 
and so Drill cannot be enabled only with Kerberos if web server is required. 
PLAIN also needs to be enabled. Accordingly, I opened DRILL-5425.

> Kerberos Authentication
> ---
>
> Key: DRILL-4280
> URL: https://issues.apache.org/jira/browse/DRILL-4280
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: Keys Botzum
>Assignee: Sudheesh Katkam
>  Labels: security
> Fix For: 1.10.0
>
>
> Drill should support Kerberos based authentication from clients. This means 
> that both the ODBC and JDBC drivers as well as the web/REST interfaces should 
> support inbound Kerberos. For Web this would most likely be SPNEGO while for 
> ODBC and JDBC this will be more generic Kerberos.
> Since Hive and much of Hadoop supports Kerberos there is a potential for a 
> lot of reuse of ideas if not implementation.
> Note that this is related to but not the same as 
> https://issues.apache.org/jira/browse/DRILL-3584 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (DRILL-4280) Kerberos Authentication

2017-04-10 Thread Sudheesh Katkam (JIRA)


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

Sudheesh Katkam edited comment on DRILL-4280 at 4/10/17 5:20 PM:
-

Hi [~djc0604], Kerberos SPNEGO support was not included as part of the patch, 
and so Drill cannot be enabled only with Kerberos if web server is required. 
PLAIN also needs to be enabled. Accordingly, I opened DRILL-5425.


was (Author: sudheeshkatkam):
Hi [~djc0604], Kerberos SPNEGO support was not included as part of resolving 
this ticket, and so Drill cannot be enabled only with Kerberos if web server is 
required. PLAIN also needs to be enabled. Accordingly, I opened DRILL-5425.

> Kerberos Authentication
> ---
>
> Key: DRILL-4280
> URL: https://issues.apache.org/jira/browse/DRILL-4280
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: Keys Botzum
>Assignee: Sudheesh Katkam
>  Labels: security
> Fix For: 1.10.0
>
>
> Drill should support Kerberos based authentication from clients. This means 
> that both the ODBC and JDBC drivers as well as the web/REST interfaces should 
> support inbound Kerberos. For Web this would most likely be SPNEGO while for 
> ODBC and JDBC this will be more generic Kerberos.
> Since Hive and much of Hadoop supports Kerberos there is a potential for a 
> lot of reuse of ideas if not implementation.
> Note that this is related to but not the same as 
> https://issues.apache.org/jira/browse/DRILL-3584 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-4280) Kerberos Authentication

2017-04-10 Thread Sudheesh Katkam (JIRA)


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

Sudheesh Katkam commented on DRILL-4280:


Hi [~djc0604], Kerberos SPNEGO support was not included as part of this ticket, 
and so Drill cannot be enabled only with Kerberos if web server is required. 
PLAIN also needs to be enabled. Accordingly, I opened DRILL-5425.

> Kerberos Authentication
> ---
>
> Key: DRILL-4280
> URL: https://issues.apache.org/jira/browse/DRILL-4280
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: Keys Botzum
>Assignee: Sudheesh Katkam
>  Labels: security
> Fix For: 1.10.0
>
>
> Drill should support Kerberos based authentication from clients. This means 
> that both the ODBC and JDBC drivers as well as the web/REST interfaces should 
> support inbound Kerberos. For Web this would most likely be SPNEGO while for 
> ODBC and JDBC this will be more generic Kerberos.
> Since Hive and much of Hadoop supports Kerberos there is a potential for a 
> lot of reuse of ideas if not implementation.
> Note that this is related to but not the same as 
> https://issues.apache.org/jira/browse/DRILL-3584 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (DRILL-5425) Support HTTP Kerberos auth using SPNEGO

2017-04-10 Thread Sudheesh Katkam (JIRA)

Sudheesh Katkam created DRILL-5425:
--

 Summary: Support HTTP Kerberos auth using SPNEGO
 Key: DRILL-5425
 URL: https://issues.apache.org/jira/browse/DRILL-5425
 Project: Apache Drill
  Issue Type: New Feature
  Components: Web Server
Reporter: Sudheesh Katkam


DRILL-4280 supports Kerberos through JDBC and ODBC API. This ticket requests to 
add Kerberos (using [SPENGO|https://en.wikipedia.org/wiki/SPNEGO]) for HTTP 
connections.

This requires creating "direct" web sessions; currently web sessions are 
sessions over Java client sessions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-5005) Potential issues with external sort info in query profile

2017-04-10 Thread Khurram Faraaz (JIRA)


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

Khurram Faraaz commented on DRILL-5005:
---

[~rkins] can you please verify this JIRA, since you already have the tests for 
external sort.

> Potential issues with external sort info in query profile
> -
>
> Key: DRILL-5005
> URL: https://issues.apache.org/jira/browse/DRILL-5005
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.9.0
>Reporter: Paul Rogers
>Assignee: Paul Rogers
>Priority: Minor
> Fix For: 1.11.0
>
>
> Run a query that will include an external sort.
> Look at the visualized plan. The external sort is shown in the tree as just 
> "Sort". Suggestion: say "External Sort".
> In the operator profiles section, memory use for EXTERNAL_SORT is listed as 
> 26MB. Yet the file being sorted is 388 MB. Even allowing for projects of a 
> subset of column, 26 MB seems awfully small to hold the data set. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (DRILL-5424) Fix IOBE for reverse function

2017-04-10 Thread Volodymyr Vysotskyi (JIRA)

Volodymyr Vysotskyi created DRILL-5424:
--

 Summary: Fix IOBE for reverse function
 Key: DRILL-5424
 URL: https://issues.apache.org/jira/browse/DRILL-5424
 Project: Apache Drill
  Issue Type: Bug
  Components: Functions - Drill
Affects Versions: 1.9.0
Reporter: Volodymyr Vysotskyi
Assignee: Volodymyr Vysotskyi
Priority: Minor


Query with reverse function fails:
{code:sql}
0: jdbc:drill:zk=local> select reverse(a) from dfs.`/tmp/test.json`;
Error: SYSTEM ERROR: IndexOutOfBoundsException: index: 259, length: 1 
(expected: range(0, 256))
{code}
for table with several long varchars.
{noformat}
cat /tmp/test.json
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{noformat}
The same query works for the table with less row number:
{code:sql}
0: jdbc:drill:zk=local> select reverse(a) from dfs.`/tmp/test2.json`;
+---+
|EXPR$0 |
+---+
| zyxwvutsrqponmlkjihgfedcbazyxwvutsrqponmlkjihgfedcba  |
| zyxwvutsrqponmlkjihgfedcbazyxwvutsrqponmlkjihgfedcba  |
| zyxwvutsrqponmlkjihgfedcbazyxwvutsrqponmlkjihgfedcba  |
| zyxwvutsrqponmlkjihgfedcbazyxwvutsrqponmlkjihgfedcba  |
+---+
{code}
{noformat}
cat /tmp/test2.json
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{"a": "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz"}
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[jira] [Updated] (DRILL-5409) Update MapR version to 5.2.1-mapr

[jira] [Commented] (DRILL-5409) Update MapR version to 5.2.1-mapr

[jira] [Commented] (DRILL-5409) Update MapR version to 5.2.1-mapr

[jira] [Updated] (DRILL-5415) Improve Fixture Builder to configure client properties and keep collection type properties for server

[jira] [Closed] (DRILL-4908) Unable to setup Sybase JDBC Plugin with access to multiple databases

[jira] [Updated] (DRILL-5427) SQL Execution Syntax incorrect for Sybase RDBMS

[jira] [Created] (DRILL-5427) SQL Execution Syntax incorrect for Sybase RDBMS

[jira] [Assigned] (DRILL-5213) Prepared statement for actual query is missing the query text

[jira] [Commented] (DRILL-5213) Prepared statement for actual query is missing the query text

[jira] [Updated] (DRILL-5426) Queries fail with "RESOURCE ERROR: Failed to create schema tree." when Impersonation is enabled

[jira] [Created] (DRILL-5426) Queries fail with "RESOURCE ERROR: Failed to create schema tree." when Impersonation is enabled

[jira] [Updated] (DRILL-5005) Potential issues with external sort info in query profile

[jira] [Closed] (DRILL-5032) Drill query on hive parquet table failed with OutOfMemoryError: Java heap space

[jira] [Closed] (DRILL-5065) Optimize count(*) queries on MapR-DB JSON Tables

[jira] [Closed] (DRILL-5094) Assure Comparator to be transitive

[jira] [Closed] (DRILL-5304) Queries fail intermittently when there is skew in data distribution

[jira] [Comment Edited] (DRILL-4280) Kerberos Authentication

[jira] [Comment Edited] (DRILL-4280) Kerberos Authentication

[jira] [Commented] (DRILL-4280) Kerberos Authentication

[jira] [Created] (DRILL-5425) Support HTTP Kerberos auth using SPNEGO

[jira] [Commented] (DRILL-5005) Potential issues with external sort info in query profile

[jira] [Created] (DRILL-5424) Fix IOBE for reverse function

23 matches

Site Navigation

Mail list logo

Footer information