[GitHub] drill pull request: DRILL-4657: Rank() will return wrong results i...

2016-05-06 Thread asfgit
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] drill pull request: DRILL-4657: Rank() will return wrong results i...

2016-05-06 Thread amansinha100
Github user amansinha100 commented on the pull request:

https://github.com/apache/drill/pull/499#issuecomment-217587650
  
+1.  LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


Re: Manta Object Store Support

2016-05-06 Thread Tomer Shiran
Does Manta have a Hadoop FileSystem API implementation? That's what Drill
uses for S3, HDFS, MapR-FS, Azure Blob Storage, etc. You could potentially
write a Drill storage plugin, but you get a lot for free if you already
have the file system implementation.

On Fri, May 6, 2016 at 9:43 AM, Elijah Zupancic  wrote:

> I'm trying to get started contributing to Apache Drill. I've got the
> project checked out and it is building to my satisfaction. Right now, I'm
> trying to add support for the open source object store Manta (
> https://github.com/joyent/manta). I thought that this would be a good
> learning project.
>
> Initially, I want to add support in the same way that S3 has support.
> However, I can't seem to find a reference to the S3 storage driver in the
> code base. Is the s3 storage driver part of a different project? How would
> you suggest that I get started?
>
> Thank you,
> Elijah Zupancic
>


Getting Started & Adding Manta Object Store Support

2016-05-06 Thread Elijah Zupancic
I'm trying to get started contributing to Apache Drill. I've got the project 
checked out and it is building to my satisfaction. Right now, I'm trying to add 
support for the open source object store Manta (https://github.com/joyent/manta 
). I thought that this would be a good 
learning project.

Initially, I want to add support in the same way that S3 has support. However, 
I can't seem to find a reference to the S3 storage driver in the code base. Is 
the s3 storage driver part of a different project? How would you suggest that I 
get started?

Thank you,
Elijah Zupancic

Manta Object Store Support

2016-05-06 Thread Elijah Zupancic
I'm trying to get started contributing to Apache Drill. I've got the
project checked out and it is building to my satisfaction. Right now, I'm
trying to add support for the open source object store Manta (
https://github.com/joyent/manta). I thought that this would be a good
learning project.

Initially, I want to add support in the same way that S3 has support.
However, I can't seem to find a reference to the S3 storage driver in the
code base. Is the s3 storage driver part of a different project? How would
you suggest that I get started?

Thank you,
Elijah Zupancic


[jira] [Resolved] (DRILL-3763) Cancel (Ctrl-C) one of concurrent queries results in ChannelClosedException

2016-05-06 Thread Deneche A. Hakim (JIRA)

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

Deneche A. Hakim resolved DRILL-3763.
-
Resolution: Fixed

DRILL-3714 should also fix this issue

> Cancel (Ctrl-C) one of concurrent queries results in ChannelClosedException
> ---
>
> Key: DRILL-3763
> URL: https://issues.apache.org/jira/browse/DRILL-3763
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - RPC
>Affects Versions: 1.2.0
> Environment: 4 node cluster CentOS
>Reporter: Khurram Faraaz
>Assignee: Deneche A. Hakim
> Fix For: 1.7.0
>
>
> Canceling a query from a set of concurrent queries executing on the same 
> table, results in ChannelClosedException when one of the queries in Canceled 
> using Ctrl-C from sqlline prompt.
> Steps to reproduce the problem,
> 1. Start, service map-warden start on 4 nodes.
> 2. Start eight sqlline sessions from eight different terminals, ./sqlline -u 
> "jdbc:drill:schema=dfs.tmp"
> 3. Run the below query from the eight sqlline sessions
> select * from `twoKeyJsn.json`;
> 4. While the queries are being executed, Cancel one of the queries on sqlline 
> prompt, issue Ctrl-C on sqlline.
> 5. you will note that after a few seconds/minutes, on one of the other 
> sqlline sessions there is a ChannelClosedException that is reported and that 
> query is reported as FAILED on the query profile on the Web UI.
> {code}
> 0: jdbc:drill:schema=dfs.tmp> select * from `twoKeyJsn.json`;
> ...
> | 1.31643767542E9  | h|
> | 9.02780441562E8  | b|
> | 6.46524413864E8  | l|
> java.lang.RuntimeException: java.sql.SQLException: SYSTEM ERROR: 
> ChannelClosedException: Channel closed /10.10.100.201:31010 <--> 
> /10.10.100.202:58705.
> Fragment 0:0
> [Error Id: bd765bd5-3921-4b58-89a7-cd87482f9088 on centos-01.qa.lab:31010]
>   at sqlline.IncrementalRows.hasNext(IncrementalRows.java:73)
>   at 
> sqlline.TableOutputFormat$ResizingRowsProvider.next(TableOutputFormat.java:87)
>   at sqlline.TableOutputFormat.print(TableOutputFormat.java:118)
>   at sqlline.SqlLine.print(SqlLine.java:1583)
>   at sqlline.Commands.execute(Commands.java:852)
>   at sqlline.Commands.sql(Commands.java:751)
>   at sqlline.SqlLine.dispatch(SqlLine.java:738)
>   at sqlline.SqlLine.begin(SqlLine.java:612)
>   at sqlline.SqlLine.start(SqlLine.java:366)
>   at sqlline.SqlLine.main(SqlLine.java:259)
> 0: jdbc:drill:schema=dfs.tmp> 
> {code}
> Stack trace from drillbit.log
> {code}
> 2015-09-10 23:23:55,019 [UserServer-1] INFO  
> o.a.d.e.w.fragment.FragmentExecutor - 
> 2a0df049-697d-f47b-86b5-1e2697946237:0:0: State change requested RUNNING --> 
> FAILED
> 2015-09-10 23:24:05,319 [2a0df049-697d-f47b-86b5-1e2697946237:frag:0:0] INFO  
> o.a.d.e.w.fragment.FragmentExecutor - 
> 2a0df049-697d-f47b-86b5-1e2697946237:0:0: State change requested FAILED --> 
> FINISHED
> 2015-09-10 23:24:05,331 [2a0df049-697d-f47b-86b5-1e2697946237:frag:0:0] ERROR 
> o.a.d.e.w.fragment.FragmentExecutor - SYSTEM ERROR: ChannelClosedException: 
> Channel closed /10.10.100.201:31010 <--> /10.10.100.202:58705.
> Fragment 0:0
> [Error Id: bd765bd5-3921-4b58-89a7-cd87482f9088 on centos-01.qa.lab:31010]
> org.apache.drill.common.exceptions.UserException: SYSTEM ERROR: 
> ChannelClosedException: Channel closed /10.10.100.201:31010 <--> 
> /10.10.100.202:58705.
> Fragment 0:0
> [Error Id: bd765bd5-3921-4b58-89a7-cd87482f9088 on centos-01.qa.lab:31010]
> at 
> org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:524)
>  ~[drill-common-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> at 
> org.apache.drill.exec.work.fragment.FragmentExecutor.sendFinalState(FragmentExecutor.java:323)
>  [drill-java-exec-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> at 
> org.apache.drill.exec.work.fragment.FragmentExecutor.cleanup(FragmentExecutor.java:178)
>  [drill-java-exec-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> at 
> org.apache.drill.exec.work.fragment.FragmentExecutor.run(FragmentExecutor.java:292)
>  [drill-java-exec-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> at 
> org.apache.drill.common.SelfCleaningRunnable.run(SelfCleaningRunnable.java:38)
>  [drill-common-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>  [na:1.7.0_45]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>  [na:1.7.0_45]
> at java.lang.Thread.run(Thread.java:744) [na:1.7.0_45]
> Caused by: org.apache.drill.exec.rpc.ChannelClosedException: Channel closed 
> /10.10.100.201:31010 <--> /10.10.100.202:58705.
> at 
> org.apache.drill.exec.rpc.RpcBus$ChannelClosedHandler.operationComplete(RpcBus.java:167)
>  ~

[jira] [Created] (DRILL-4658) cannot specify tab as a fieldDelimiter in table function

2016-05-06 Thread Vince Gonzalez (JIRA)
Vince Gonzalez created DRILL-4658:
-

 Summary: cannot specify tab as a fieldDelimiter in table function
 Key: DRILL-4658
 URL: https://issues.apache.org/jira/browse/DRILL-4658
 Project: Apache Drill
  Issue Type: Bug
  Components: SQL Parser
Affects Versions: 1.6.0
 Environment: Mac OS X, Java 8
Reporter: Vince Gonzalez


I can't specify a tab delimiter in the table function because it maybe counts 
the characters rather than trying to interpret as a character escape code?

{code}
0: jdbc:drill:zk=local> select columns[0] as a, cast(columns[1] as bigint) as b 
from table(dfs.tmp.`sample_cast.tsv`(type => 'text', fieldDelimiter => '\t', 
skipFirstLine => true));
Error: PARSE ERROR: Expected single character but was String: \t

table sample_cast.tsv
parameter fieldDelimiter
SQL Query null

[Error Id: 3efa82e1-3810-4d4a-b23c-32d6658dffcf on 172.30.1.144:31010] 
(state=,code=0)
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)