[jira] [Updated] (DRILL-4649) Drill Authentication in Window Operating System

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4649:

Description: 
I am running drill in embedded mode with
 window 8.1 operating system.
 
My question is how to authenticate drill. I want if any one start
 drill, it will ask for user name and password to start drill. I know that
 drill use PAM Authentication. But I don't know how to use PAM in window 8.1
 operating system & where  and how to store username & password.  Please
 Suggest me or if possible give me some example how to restrict user to
 access drill in window 8.1 operating system. And How to write custom 
authentication in Window Operating System.

  was:
 I am new in Apache Drill.I am running drill in embedded mode with
 window 8.1 operating system.
 
My question is how to authenticate drill. I want if any one start
 drill, it will ask for user name and password to start drill. I know that
 drill use PAM Authentication. But I don't know how to use PAM in window 8.1
 operating system & where  and how to store username & password.  Please
 Suggest me or if possible give me some example how to restrict user to
 access drill in window 8.1 operating system. And How to write custom 
authentication in Window Operating System.


> Drill Authentication in Window Operating System
> ---
>
> Key: DRILL-4649
> URL: https://issues.apache.org/jira/browse/DRILL-4649
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Sanjiv Kumar
>
> I am running drill in embedded mode with
>  window 8.1 operating system.
>  
> My question is how to authenticate drill. I want if any one start
>  drill, it will ask for user name and password to start drill. I know that
>  drill use PAM Authentication. But I don't know how to use PAM in window 8.1
>  operating system & where  and how to store username & password.  Please
>  Suggest me or if possible give me some example how to restrict user to
>  access drill in window 8.1 operating system. And How to write custom 
> authentication in Window Operating System.



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

[jira] [Commented] (DRILL-4132) Ability to submit simple type of physical plan directly to EndPoint DrillBit for execution

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

Github user hnfgns commented on the pull request:

https://github.com/apache/drill/pull/368#issuecomment-216724026
  
+1 if made sure all tests are green.


> Ability to submit simple type of physical plan directly to EndPoint DrillBit 
> for execution
> --
>
> Key: DRILL-4132
> URL: https://issues.apache.org/jira/browse/DRILL-4132
> Project: Apache Drill
>  Issue Type: New Feature
>  Components: Execution - Flow, Execution - RPC, Query Planning & 
> Optimization
>Reporter: Yuliya Feldman
>Assignee: Yuliya Feldman
>
> Today Drill Query execution is optimistic and stateful (at least due to data 
> exchanges) - if any of the stages of query execution fails whole query fails. 
> If query is just simple scan, filter push down and project where no data 
> exchange happens between DrillBits there is no need to fail whole query when 
> one DrillBit fails, as minor fragments running on that DrillBit can be rerun 
> on the other DrillBit. There are probably multiple ways to achieve this. This 
> JIRA is to open discussion on: 
> 1. agreement that we need to support above use case 
> 2. means of achieving it.



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

[jira] [Created] (DRILL-4653) Malformed JSON should not stop the entire query from progressing

2016-05-03 Thread subbu srinivasan (JIRA) 
subbu srinivasan created DRILL-4653:
---

 Summary: Malformed JSON should not stop the entire query from 
progressing
 Key: DRILL-4653
 URL: https://issues.apache.org/jira/browse/DRILL-4653
 Project: Apache Drill
  Issue Type: Improvement
  Components: Storage - JSON
Affects Versions: 1.6.0
Reporter: subbu srinivasan


Currently Drill query terminates upon first encounter of a invalid JSON line.
Drill has to continue progressing after ignoring the bad records. Something 
similar to a setting of (ignore.malformed.json) would help.





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

[jira] [Commented] (DRILL-4653) Malformed JSON should not stop the entire query from progressing

2016-05-03 Thread subbu srinivasan (JIRA) 

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

subbu srinivasan commented on DRILL-4653:
-

Folks,
I went through the code for JsonParsing. The main call for JSON deserialization 
happens to be
in JSONReader which is called from JSONRecordParser. The issue is that a 
handleAndRaise call is made to all caught exceptions.
Would the proposal below be of acceptance to the community.
The proposal is to catch the IOException and not bail out.
try{
outside: while(recordCount < BaseValueVector.INITIAL_VALUE_ALLOCATION) {
try
{
writer.setPosition(recordCount);
write = jsonReader.write(writer);
if(write == ReadState.WRITE_SUCCEED)
{ // logger.debug("Wrote record."); recordCount++; }
else
{ // logger.debug("Exiting."); break outside; }
}
catch(IOException ex)
{ logger.error("Ignoring record. Error parsing JSON: ", ex); ++parseErrorCount; 
}
}

> Malformed JSON should not stop the entire query from progressing
> 
>
> Key: DRILL-4653
> URL: https://issues.apache.org/jira/browse/DRILL-4653
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Storage - JSON
>Affects Versions: 1.6.0
>Reporter: subbu srinivasan
>
> Currently Drill query terminates upon first encounter of a invalid JSON line.
> Drill has to continue progressing after ignoring the bad records. Something 
> similar to a setting of (ignore.malformed.json) would help.



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

[jira] [Commented] (DRILL-4352) Query fails on single corrupted parquet column

2016-05-03 Thread subbu srinivasan (JIRA) 

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

subbu srinivasan commented on DRILL-4352:
-

Overloaded this bug - Should I open a separate one for Parquet?

> Query fails on single corrupted parquet column
> --
>
> Key: DRILL-4352
> URL: https://issues.apache.org/jira/browse/DRILL-4352
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Execution - Monitoring, Storage - Parquet
>Affects Versions: 1.4.0
>Reporter: F Méthot
>
> Getting this error when querying a corrupted Parquet file.
> Error: SYSTEM ERROR: IOException: FAILED_TO_UNCOMPRESSED(5)
> Fragment 1:9
> A single corrupt file among 1000s will cause a query to break.
> Encountering a corrupt files should be logged and not spoil a query.
> It would have been useful if it was clearly specified in the log which 
> parquet file is causing issue.
> Response from Ted Dunning:
> This is a lot like the problem of encountering bad lines in a line oriented 
> file such as CSV or JSON. 
> Drill doesn't currently have a good mechanism for skipping bad input. Or 
> rather, it has reasonably good mechanisms, but it doesn't use them well.
> I think that this is a very reasonable extension of the problem of dealing 
> with individual bad records and should be handled somehow by the parquet 
> scanner.



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

[jira] [Commented] (DRILL-4352) Query fails on single corrupted parquet column

2016-05-03 Thread subbu srinivasan (JIRA) 

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

subbu srinivasan commented on DRILL-4352:
-

Folks,
I went through the code for JsonParsing.  The main call for JSON 
deserialization happens to be
in JSONReader which is called from JSONRecordParser. The issue is that a 
handleAndRaise call is made to all caught exceptions.

Would the proposal below be of acceptance to the community.

The proposal is to catch the IOException and not bail out. 

 try{
  outside: while(recordCount < BaseValueVector.INITIAL_VALUE_ALLOCATION) {
try
{
writer.setPosition(recordCount);
write = jsonReader.write(writer);

if(write == ReadState.WRITE_SUCCEED) {
//  logger.debug("Wrote record.");
  recordCount++;
}else{
//  logger.debug("Exiting.");
  break outside;
}
}
catch(IOException ex)
{
logger.error("Ignoring record. Error parsing JSON: ", ex);
++parseErrorCount;
}

  }



> Query fails on single corrupted parquet column
> --
>
> Key: DRILL-4352
> URL: https://issues.apache.org/jira/browse/DRILL-4352
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Execution - Monitoring, Storage - Parquet
>Affects Versions: 1.4.0
>Reporter: F Méthot
>
> Getting this error when querying a corrupted Parquet file.
> Error: SYSTEM ERROR: IOException: FAILED_TO_UNCOMPRESSED(5)
> Fragment 1:9
> A single corrupt file among 1000s will cause a query to break.
> Encountering a corrupt files should be logged and not spoil a query.
> It would have been useful if it was clearly specified in the log which 
> parquet file is causing issue.
> Response from Ted Dunning:
> This is a lot like the problem of encountering bad lines in a line oriented 
> file such as CSV or JSON. 
> Drill doesn't currently have a good mechanism for skipping bad input. Or 
> rather, it has reasonably good mechanisms, but it doesn't use them well.
> I think that this is a very reasonable extension of the problem of dealing 
> with individual bad records and should be handled somehow by the parquet 
> scanner.



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

[jira] [Comment Edited] (DRILL-4573) Zero copy LIKE, REGEXP_MATCHES, SUBSTR

2016-05-03 Thread jean-claude (JIRA) 

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

jean-claude edited comment on DRILL-4573 at 5/3/16 11:57 PM:
-

[~seanhychu]
this is ready to be applied. DRILL-4573-3.patch is the one that fixes the issue 
mentioned above and I also added a test case for regexp_replace because there 
were none.



was (Author: jccote):
this is ready to be applied. DRILL-4573-3.patch is the one that fixes the issue 
mentioned above and I also added a test case for regexp_replace because there 
were none.


> Zero copy LIKE, REGEXP_MATCHES, SUBSTR
> --
>
> Key: DRILL-4573
> URL: https://issues.apache.org/jira/browse/DRILL-4573
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: jean-claude
>Priority: Minor
> Fix For: 1.7.0
>
> Attachments: DRILL-4573-3.patch.txt, DRILL-4573.patch.txt
>
>
> All the functions using the java.util.regex.Matcher are currently creating 
> Java string objects to pass into the matcher.reset().
> However this creates unnecessary copy of the bytes and a Java string object.
> The matcher uses a CharSequence, so instead of making a copy we can create an 
> adapter from the DrillBuffer to the CharSequence interface.
> Gains of 25% in execution speed are possible when going over VARCHAR of 36 
> chars. The gain will be proportional to the size of the VARCHAR.



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

[jira] [Commented] (DRILL-4573) Zero copy LIKE, REGEXP_MATCHES, SUBSTR

2016-05-03 Thread jean-claude (JIRA) 

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

jean-claude commented on DRILL-4573:


this is ready to be applied. DRILL-4573-3.patch is the one that fixes the issue 
mentioned above and I also added a test case for regexp_replace because there 
were none.


> Zero copy LIKE, REGEXP_MATCHES, SUBSTR
> --
>
> Key: DRILL-4573
> URL: https://issues.apache.org/jira/browse/DRILL-4573
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: jean-claude
>Priority: Minor
> Fix For: 1.7.0
>
> Attachments: DRILL-4573-3.patch.txt, DRILL-4573.patch.txt
>
>
> All the functions using the java.util.regex.Matcher are currently creating 
> Java string objects to pass into the matcher.reset().
> However this creates unnecessary copy of the bytes and a Java string object.
> The matcher uses a CharSequence, so instead of making a copy we can create an 
> adapter from the DrillBuffer to the CharSequence interface.
> Gains of 25% in execution speed are possible when going over VARCHAR of 36 
> chars. The gain will be proportional to the size of the VARCHAR.



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

[jira] [Resolved] (DRILL-4652) C++ client build breaks when trying to include commit messages with quotes

2016-05-03 Thread Parth Chandra (JIRA) 

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

Parth Chandra resolved DRILL-4652.
--
Resolution: Fixed

> C++ client build breaks when trying to include commit messages with quotes
> --
>
> Key: DRILL-4652
> URL: https://issues.apache.org/jira/browse/DRILL-4652
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Parth Chandra
>
> The C++ client build generates a string based on git commit info to print to 
> the log at startup time. This breaks if the commit message has quotes since 
> the embedded quotes are not escaped.



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

[jira] [Commented] (DRILL-4652) C++ client build breaks when trying to include commit messages with quotes

2016-05-03 Thread Parth Chandra (JIRA) 

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

Parth Chandra commented on DRILL-4652:
--

Fixed in f07f328

> C++ client build breaks when trying to include commit messages with quotes
> --
>
> Key: DRILL-4652
> URL: https://issues.apache.org/jira/browse/DRILL-4652
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Parth Chandra
>
> The C++ client build generates a string based on git commit info to print to 
> the log at startup time. This breaks if the commit message has quotes since 
> the embedded quotes are not escaped.



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

[jira] [Commented] (DRILL-4652) C++ client build breaks when trying to include commit messages with quotes

2016-05-03 Thread Parth Chandra (JIRA) 

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

Parth Chandra commented on DRILL-4652:
--

PR: https://github.com/apache/drill/pull/494

> C++ client build breaks when trying to include commit messages with quotes
> --
>
> Key: DRILL-4652
> URL: https://issues.apache.org/jira/browse/DRILL-4652
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Parth Chandra
>
> The C++ client build generates a string based on git commit info to print to 
> the log at startup time. This breaks if the commit message has quotes since 
> the embedded quotes are not escaped.



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

[jira] [Created] (DRILL-4652) C++ client build breaks when trying to include commit messages with quotes

2016-05-03 Thread Parth Chandra (JIRA) 
Parth Chandra created DRILL-4652:


 Summary: C++ client build breaks when trying to include commit 
messages with quotes
 Key: DRILL-4652
 URL: https://issues.apache.org/jira/browse/DRILL-4652
 Project: Apache Drill
  Issue Type: Bug
Reporter: Parth Chandra


The C++ client build generates a string based on git commit info to print to 
the log at startup time. This breaks if the commit message has quotes since the 
embedded quotes are not escaped.



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

[jira] [Commented] (DRILL-4352) Query fails on single corrupted parquet column

2016-05-03 Thread subbu srinivasan (JIRA) 

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

subbu srinivasan commented on DRILL-4352:
-

This is a valid issue -Anyone working on this.

> Query fails on single corrupted parquet column
> --
>
> Key: DRILL-4352
> URL: https://issues.apache.org/jira/browse/DRILL-4352
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Execution - Monitoring, Storage - Parquet
>Affects Versions: 1.4.0
>Reporter: F Méthot
>
> Getting this error when querying a corrupted Parquet file.
> Error: SYSTEM ERROR: IOException: FAILED_TO_UNCOMPRESSED(5)
> Fragment 1:9
> A single corrupt file among 1000s will cause a query to break.
> Encountering a corrupt files should be logged and not spoil a query.
> It would have been useful if it was clearly specified in the log which 
> parquet file is causing issue.
> Response from Ted Dunning:
> This is a lot like the problem of encountering bad lines in a line oriented 
> file such as CSV or JSON. 
> Drill doesn't currently have a good mechanism for skipping bad input. Or 
> rather, it has reasonably good mechanisms, but it doesn't use them well.
> I think that this is a very reasonable extension of the problem of dealing 
> with individual bad records and should be handled somehow by the parquet 
> scanner.



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

[jira] [Created] (DRILL-4651) S3 connector and empty bucket issue

2016-05-03 Thread subbu srinivasan (JIRA) 
subbu srinivasan created DRILL-4651:
---

 Summary: S3 connector and empty bucket issue
 Key: DRILL-4651
 URL: https://issues.apache.org/jira/browse/DRILL-4651
 Project: Apache Drill
  Issue Type: Bug
  Components: Storage - Information Schema
Affects Versions: 1.6.0
Reporter: subbu srinivasan


show schemas  will not list the  information about a registered s3 plugin if 
the bucket is empty. This is in embedded mode.

Steps to reproduce:

- Go to http://localhost:8047/storage
- Add s3 plugin (make sure bucket empty)
- show schemas will not information about the s3 plugin/workspaces
- Add a test file to bucket and show schemas will show the plugin/workspace



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

[jira] [Commented] (DRILL-4641) Support for lzo compression

2016-05-03 Thread subbu srinivasan (JIRA) 

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

subbu srinivasan commented on DRILL-4641:
-

Can we add this to documentation and resolve the issue?

> Support for lzo compression
> ---
>
> Key: DRILL-4641
> URL: https://issues.apache.org/jira/browse/DRILL-4641
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Storage - Other
>Affects Versions: Future
> Environment: Not specific to platform
>Reporter: subbu srinivasan
>
> Would love support for quering lzo compressed files.



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

[jira] [Commented] (DRILL-2100) Drill not deleting spooling files

2016-05-03 Thread Jason Altekruse (JIRA) 

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

Jason Altekruse commented on DRILL-2100:


[~vitalii] Sorry for missing this during the review, won't using deleteOnExit 
wait until JVM shutdown to delete the directories? This isn't the desired 
behavior is it?

> Drill not deleting spooling files
> -
>
> Key: DRILL-2100
> URL: https://issues.apache.org/jira/browse/DRILL-2100
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Relational Operators
>Affects Versions: 0.8.0
>Reporter: Abhishek Girish
>Assignee: Deneche A. Hakim
> Fix For: 1.7.0
>
>
> Currently, after forcing queries to use an external sort by switching off 
> hash join/agg causes spill-to-disk files accumulating. 
> This causes issues with disk space availability when the spill is configured 
> to be on the local file system (/tmp/drill). Also not optimal when configured 
> to use DFS (custom). 
> Drill must clean up all temporary files created after a query completes or 
> after a drillbit restart. 



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

[jira] [Commented] (DRILL-2656) Add ability to specify options for clean shutdown of a Drillbit

2016-05-03 Thread John Omernik (JIRA) 

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

John Omernik commented on DRILL-2656:
-

This feature would be very important for multi-tenant clusters and clusters 
where say you want to be able to shutdown half of the available drillbits for 
the evening when no one is running queries to be able to free up resources for 
other things in the cluster.   Lots of reasons for this, +1 from me. 

> Add ability to specify options for clean shutdown of a Drillbit
> ---
>
> Key: DRILL-2656
> URL: https://issues.apache.org/jira/browse/DRILL-2656
> Project: Apache Drill
>  Issue Type: New Feature
>  Components: Execution - Flow
>Affects Versions: 0.8.0
>Reporter: Chris Westin
> Fix For: Future
>
>
> When we shut down a Drillbit, we should provide some options similar to those 
> available from Oracle's shutdown command (see 
> https://docs.oracle.com/cd/B28359_01/server.111/b28310/start003.htm#ADMIN11156)
>  .
> At present, in order to avoid problems like DRILL-2654, we try to do a short 
> wait for executing queries, but that times out after 5 seconds, and doesn't 
> help with long-running queries.
> Someone that is running a long query might be unhappy about losing work for 
> something that was near completion, so we can do better.
> And, in order to avoid spurious cleanup problems and exceptions, we should 
> explicitly cancel any remaining queries before we do complete the shutdown.
> As in the Oracle example, we might have shutdown immediate issue 
> cancellations to the running queries.  A clean shutdown might not have a 
> timeout, or might allow the specification of a longer timeout, and even when 
> the timeout goes off, we should still cleanly cancel any remaining queries, 
> and wait for the cancellations to complete.



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

[jira] [Commented] (DRILL-4286) Have an ability to put server in quiescent mode of operation

2016-05-03 Thread John Omernik (JIRA) 

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

John Omernik commented on DRILL-4286:
-

This feature would be very important for multi-tenant clusters and clusters 
where say you want to be able to shutdown half of the available drillbits for 
the evening when no one is running queries to be able to free up resources for 
other things in the cluster.   Lots of reasons for this, (Also going to add to 
DRILL-2656).


> Have an ability to put server in quiescent mode of operation
> 
>
> Key: DRILL-4286
> URL: https://issues.apache.org/jira/browse/DRILL-4286
> Project: Apache Drill
>  Issue Type: New Feature
>  Components: Execution - Flow
>Reporter: Victoria Markman
>
> I think drill will benefit from mode of operation that is called "quiescent" 
> in some databases. 
> From IBM Informix server documentation:
> {code}
> Change gracefully from online to quiescent mode
> Take the database server gracefully from online mode to quiescent mode to 
> restrict access to the database server without interrupting current 
> processing. After you perform this task, the database server sets a flag that 
> prevents new sessions from gaining access to the database server. The current 
> sessions are allowed to finish processing. After you initiate the mode 
> change, it cannot be canceled. During the mode change from online to 
> quiescent, the database server is considered to be in Shutdown mode.
> {code}
> This is different from shutdown, when processes are terminated. 



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

[jira] [Closed] (DRILL-4592) Explain plan statement should show plan in WebUi

2016-05-03 Thread Krystal (JIRA) 

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

Krystal closed DRILL-4592.
--

git.commit.id.abbrev=b8f6ebc

Verified that physical and visualized plans for explain plan queries are 
displayed in the Web UI.

> Explain plan statement should show plan in WebUi
> 
>
> Key: DRILL-4592
> URL: https://issues.apache.org/jira/browse/DRILL-4592
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Jinfeng Ni
>Assignee: Jinfeng Ni
> Fix For: 1.7.0
>
>
> When explain plan statement is run, the physical plan is generated and 
> returned. However, the plan is not put in the profile and does not show up in 
> the physical plan / visual plan tab in WebUI. If someone wants to look at the 
> visual plan, the only way is to execute the query, which sometime requires 
> long execution time. This makes a bit hard to analyze the plan for a 
> problematic query.  
> Similar as regular query and CTAS statement, we should put the plan for 
> EXPLAIN PLAN statement, and display properly in WebUi.



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

[jira] [Commented] (DRILL-2100) Drill not deleting spooling files

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> Drill not deleting spooling files
> -
>
> Key: DRILL-2100
> URL: https://issues.apache.org/jira/browse/DRILL-2100
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Execution - Relational Operators
>Affects Versions: 0.8.0
>Reporter: Abhishek Girish
>Assignee: Deneche A. Hakim
> Fix For: 1.7.0
>
>
> Currently, after forcing queries to use an external sort by switching off 
> hash join/agg causes spill-to-disk files accumulating. 
> This causes issues with disk space availability when the spill is configured 
> to be on the local file system (/tmp/drill). Also not optimal when configured 
> to use DFS (custom). 
> Drill must clean up all temporary files created after a query completes or 
> after a drillbit restart. 



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

[jira] [Commented] (DRILL-4571) Add link to local Drill logs from the web UI

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> Add link to local Drill logs from the web UI
> 
>
> Key: DRILL-4571
> URL: https://issues.apache.org/jira/browse/DRILL-4571
> Project: Apache Drill
>  Issue Type: Improvement
>Reporter: Arina Ielchiieva
>Assignee: Arina Ielchiieva
> Attachments: display_log.JPG, log_list.JPG
>
>
> Now we have link to the profile from the web UI.
> It will be handy for the users to have the link to local logs as well.



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

[jira] [Commented] (DRILL-3894) Directory functions (MaxDir, MinDir ..) should have optional filename parameter

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> Directory functions (MaxDir, MinDir ..) should have optional filename 
> parameter
> ---
>
> Key: DRILL-3894
> URL: https://issues.apache.org/jira/browse/DRILL-3894
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Functions - Drill
>Affects Versions: 1.2.0
>Reporter: Neeraja
>Assignee: Vitalii Diravka
>
> https://drill.apache.org/docs/query-directory-functions/
> The directory functions documented above should provide ability to have 
> second parameter(file name) as optional.



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

[jira] [Commented] (DRILL-4584) JDBC/ODBC Client IP in Drill audit logs

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> JDBC/ODBC Client IP in Drill audit logs
> ---
>
> Key: DRILL-4584
> URL: https://issues.apache.org/jira/browse/DRILL-4584
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Client - JDBC, Client - ODBC
>Reporter: Vitalii Diravka
>Assignee: Vitalii Diravka
>Priority: Minor
> Fix For: 1.7.0
>
>
> Currently Drill audit logs - sqlline_queries.json and drillbit_queries.json 
> provide information about client username who fired the query . It will be 
> good to also have the client IP from where the query was fired .



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

[jira] [Commented] (DRILL-4649) Drill Authentication in Window Operating System

2016-05-03 Thread Venki Korukanti (JIRA) 

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

Venki Korukanti commented on DRILL-4649:


Details for writing custom authenticator are 
[here|https://drill.apache.org/docs/configuring-user-authentication/]

> Drill Authentication in Window Operating System
> ---
>
> Key: DRILL-4649
> URL: https://issues.apache.org/jira/browse/DRILL-4649
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Sanjiv Kumar
>
>  I am new in Apache Drill.I am running drill in embedded mode with
>  window 8.1 operating system.
>  
> My question is how to authenticate drill. I want if any one start
>  drill, it will ask for user name and password to start drill. I know that
>  drill use PAM Authentication. But I don't know how to use PAM in window 8.1
>  operating system & where  and how to store username & password.  Please
>  Suggest me or if possible give me some example how to restrict user to
>  access drill in window 8.1 operating system. And How to write custom 
> authentication in Window Operating System.



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

[jira] [Commented] (DRILL-4649) Drill Authentication in Window Operating System

2016-05-03 Thread Sudheesh Katkam (JIRA) 

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

Sudheesh Katkam commented on DRILL-4649:


Please ask questions on the user list: [mailto:u...@drill.apache.org]

> Drill Authentication in Window Operating System
> ---
>
> Key: DRILL-4649
> URL: https://issues.apache.org/jira/browse/DRILL-4649
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Sanjiv Kumar
>
>  I am new in Apache Drill.I am running drill in embedded mode with
>  window 8.1 operating system.
>  
> My question is how to authenticate drill. I want if any one start
>  drill, it will ask for user name and password to start drill. I know that
>  drill use PAM Authentication. But I don't know how to use PAM in window 8.1
>  operating system & where  and how to store username & password.  Please
>  Suggest me or if possible give me some example how to restrict user to
>  access drill in window 8.1 operating system. And How to write custom 
> authentication in Window Operating System.



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

[jira] [Commented] (DRILL-4552) During inference, treat decimal literals as Double when planner.enable_decimal_data_type is off

2016-05-03 Thread Sean Hsuan-Yi Chu (JIRA) 

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

Sean Hsuan-Yi Chu commented on DRILL-4552:
--

This JIRA needs a calcite issue to be resolved: CALCITE-1219
1. Calcite PR: https://github.com/apache/calcite/pull/222
2. Drill: https://github.com/hsuanyi/incubator-drill/tree/DRILL-4552

Note that the DrillCalcite needs to incorporate the PR first. Otherwise, the 
branch of Drill above won't even compile.

> During inference, treat decimal literals as Double when 
> planner.enable_decimal_data_type is off
> ---
>
> Key: DRILL-4552
> URL: https://issues.apache.org/jira/browse/DRILL-4552
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Query Planning & Optimization
>Reporter: Sean Hsuan-Yi Chu
>Assignee: Sean Hsuan-Yi Chu
>
> In SQL standard, decimal literals (e.g., 1.2, 2.5, etc) are Decimal type. In 
> Drill, when `planner.enable_decimal_data_type` is off, they are treated as 
> Double. 
> However, the current inference mechanism is "not to do any inference if the 
> operand is Decimal type". (To be more exact, treat them as ANY type and defer 
> to the execution to make the decision.)
> The mechanism can be improved by treating decimal literals as Double when 
> `planner.enable_decimal_data_type` is off.



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

[jira] [Commented] (DRILL-4642) Let RexBuilder.ensureType() mechanism take place during Rex conversion.

2016-05-03 Thread Sean Hsuan-Yi Chu (JIRA) 

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

Sean Hsuan-Yi Chu commented on DRILL-4642:
--

Drill PR: https://github.com/apache/drill/pull/489
Calcite: https://github.com/hsuanyi/incubator-calcite/tree/DRILL-4642

Note the calcite change above cannot be pushed back to apache calcite since it 
is a followup patch in DrillCalcite, titled

"[StarColumn] Support select * from schema-less table in execution engine like 
Drill. Include support for view, subquery, CTE.  Enable Drill's support of 
select * in View, SubQuery, CTE.  Skip expanding expression in with clause in 
Expander visitor."

> Let RexBuilder.ensureType() mechanism take place during Rex conversion.
> ---
>
> Key: DRILL-4642
> URL: https://issues.apache.org/jira/browse/DRILL-4642
> Project: Apache Drill
>  Issue Type: Bug
>  Components: Query Planning & Optimization
>Reporter: Sean Hsuan-Yi Chu
>Assignee: Sean Hsuan-Yi Chu
> Fix For: 1.7.0
>
>
> In DRILL-4372, the logic of ensuring same type is removed since, in some case 
> such as below, undesirable cast function will be added and cause failure.
> {code}
> SELECT * 
> FROM T 
> WHERE (cast(col1 as timestamp)  - to_timestamp(col2,'-MM-dd HH:mm:ss') < 
> interval 'X XX:XX:XX' day to second)
> {code}
> The fundamental reason for this behavior roots in Drill-Calcite [1], where 
> SqlNode WHERE is expanded to a new object but is not passed into validation 
> step.
> [1] 
> https://github.com/mapr/incubator-calcite/blob/DrillCalcite1.4.0-mapr-1.4.0/core/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java#L3362



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

[jira] [Commented] (DRILL-4647) C++ client is not propagating a connection failed error when a drillbit goes down

2016-05-03 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user parthchandra opened a pull request:

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

DRILL-4647: C++ client fails to propagate a dead connection error to …

…the application.

Return correct status from the DrillClient API if query submission fails.
Also, propagate error back to the application thru the listener if query 
submission fails or if there is a heartbeat failure before the response to 
query submission is received.

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

$ git pull https://github.com/parthchandra/drill DRILL-4647

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

https://github.com/apache/drill/pull/493.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 #493


commit e39f263eb18fb52d4105dfc8d3131357ca0a19a9
Author: Parth Chandra 
Date:   2016-04-30T00:38:44Z

DRILL-4647: C++ client fails to propagate a dead connection error to the 
application




> C++ client is not propagating a connection failed error when a drillbit goes 
> down
> -
>
> Key: DRILL-4647
> URL: https://issues.apache.org/jira/browse/DRILL-4647
> Project: Apache Drill
>  Issue Type: Bug
>Reporter: Parth Chandra
>
> When a drillbit goes down, there are two conditions under which the client is 
> not propagating the error back to the application -
> 1) The application is in a submitQuery call: the ODBC driver is expecting 
> that the error be reported thru the query results listener which hasn't been 
> registered at the point the error is encountered.
> 2) A submitQuery call succeeded but never reached the drillbit because it was 
> shutdown. In this case the application has a handle to a query and is 
> listening for results which will never arrive. The heartbeat mechanism 
> detects the failure, but is not propagating the error to the query results 
> listener.



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

[jira] [Commented] (DRILL-4456) Hive translate function is not working

2016-05-03 Thread Arina Ielchiieva (JIRA) 

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

Arina Ielchiieva commented on DRILL-4456:
-

Link to Calcite Jira  - https://issues.apache.org/jira/browse/CALCITE-1115

> Hive translate function is not working
> --
>
> Key: DRILL-4456
> URL: https://issues.apache.org/jira/browse/DRILL-4456
> Project: Apache Drill
>  Issue Type: Improvement
>  Components: Functions - Hive
>Affects Versions: 1.5.0
>Reporter: Arina Ielchiieva
> Fix For: Future
>
>
> In Hive "select translate(name, 'A', 'B') from users" works fine.
> But in Drill "select translate(name, 'A', 'B') from hive.`users`" returns the 
> following error:
> org.apache.drill.common.exceptions.UserRemoteException: PARSE ERROR: 
> Encountered "," at line 1, column 22. Was expecting one of: "USING" ... "NOT" 
> ... "IN" ... "BETWEEN" ... "LIKE" ... "SIMILAR" ... "=" ... ">" ... "<" ... 
> "<=" ... ">=" ... "<>" ... "+" ... "-" ... "*" ... "/" ... "||" ... "AND" ... 
> "OR" ... "IS" ... "MEMBER" ... "SUBMULTISET" ... "MULTISET" ... "[" ... "." 
> ... "(" ... while parsing SQL query: select translate(name, 'A', 'B') from 
> hive.users ^ [Error Id: ba21956b-3285-4544-b3b2-fab68b95be1f on 
> localhost:31010]
> Root cause:
> Calcite follows the standard SQL reference.
> SQL reference,  ISO/IEC 9075-2:2011(E), section 6.30
>  ::=
>   TRANSLATE  
> USING  
> To fix:
> 1. add support to translate (expession, from_string, to_string) alternative 
> syntax
> 2. add unit test in org.apache.drill.exec.fn.hive.TestInbuiltHiveUDFs
> Changes can be made directly in Calcite and then upgrade to appropriate 
> Calcite version. 



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

[jira] [Updated] (DRILL-4522) Apache Drill Schema Support for SQL Server

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4522:

Component/s: (was:  Server)

> Apache Drill Schema Support for SQL Server
> --
>
> Key: DRILL-4522
> URL: https://issues.apache.org/jira/browse/DRILL-4522
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
> Environment: Sql Server, Window 8.1 
>Reporter: Sanjiv Kumar
>
> I want to know whether Apache Drill supports only dbo schema?? or will it 
> support all type of schema?
> I am running my system in window 8 and with latest version of Drill(1.6) with 
> embedded mode.
> I am trying to search with same storage plugin.
> My Storage Plugin(for SQLServer):
> {
>   "type" : "jdbc",
>   "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
>   "url" : "jdbc:sqlserver://;databaseName=",
>   "username" : "",
>   "password" : "<>",
>   "enabled" : true
> }
> This Plugin has dbo & core schema (both have same type, no special 
> permission).Its works for dbo schema where core schema is not working.
> DBO Query:-
> select * from SqlServer.dbo.Attribute; //Its working.
> Core Query:-
> select * from SqlServer.core.Users //Its not working
> My question is whether Drill Supports only dbo schemna or all type of schema?



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

[jira] [Updated] (DRILL-4522) Apache Drill Schema Support for SQL Server

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4522:

Affects Version/s: (was: 1.5.0)
   1.6.0

> Apache Drill Schema Support for SQL Server
> --
>
> Key: DRILL-4522
> URL: https://issues.apache.org/jira/browse/DRILL-4522
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
> Environment: Sql Server, Window 8.1 
>Reporter: Sanjiv Kumar
>
> I want to know whether Apache Drill supports only dbo schema?? or will it 
> support all type of schema?
> I am running my system in window 8 and with latest version of Drill(1.6) with 
> embedded mode.
> I am trying to search with same storage plugin.
> My Storage Plugin(for SQLServer):
> {
>   "type" : "jdbc",
>   "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
>   "url" : "jdbc:sqlserver://;databaseName=",
>   "username" : "",
>   "password" : "<>",
>   "enabled" : true
> }
> This Plugin has dbo & core schema (both have same type, no special 
> permission).Its works for dbo schema where core schema is not working.
> DBO Query:-
> select * from SqlServer.dbo.Attribute; //Its working.
> Core Query:-
> select * from SqlServer.core.Users //Its not working
> My question is whether Drill Supports only dbo schemna or all type of schema?



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

[jira] [Updated] (DRILL-4522) Apache Drill Schema Support for SQL Server

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4522:

Fix Version/s: (was: 1.5.0)

> Apache Drill Schema Support for SQL Server
> --
>
> Key: DRILL-4522
> URL: https://issues.apache.org/jira/browse/DRILL-4522
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
> Environment: Sql Server, Window 8.1 
>Reporter: Sanjiv Kumar
>
> I want to know whether Apache Drill supports only dbo schema?? or will it 
> support all type of schema?
> I am running my system in window 8 and with latest version of Drill(1.6) with 
> embedded mode.
> I am trying to search with same storage plugin.
> My Storage Plugin(for SQLServer):
> {
>   "type" : "jdbc",
>   "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
>   "url" : "jdbc:sqlserver://;databaseName=",
>   "username" : "",
>   "password" : "<>",
>   "enabled" : true
> }
> This Plugin has dbo & core schema (both have same type, no special 
> permission).Its works for dbo schema where core schema is not working.
> DBO Query:-
> select * from SqlServer.dbo.Attribute; //Its working.
> Core Query:-
> select * from SqlServer.core.Users //Its not working
> My question is whether Drill Supports only dbo schemna or all type of schema?



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

[jira] [Updated] (DRILL-4522) Apache Drill Schema Support for SQL Server

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4522:

Description: 
I want to know whether Apache Drill supports only dbo schema?? or will it 
support all type of schema?

I am running my system in window 8 and with latest version of Drill(1.6) with 
embedded mode.

I am trying to search with same storage plugin.

My Storage Plugin(for SQLServer):

{
  "type" : "jdbc",
  "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
  "url" : "jdbc:sqlserver://;databaseName=",
  "username" : "",
  "password" : "<>",
  "enabled" : true
}
This Plugin has dbo & core schema (both have same type, no special 
permission).Its works for dbo schema where core schema is not working.

DBO Query:-

select * from SqlServer.dbo.Attribute; //Its working.

Core Query:-

select * from SqlServer.core.Users //Its not working
My question is whether Drill Supports only dbo schemna or all type of schema?

  was:
I want to know whether Apache Drill supports only dbo schema?? or will it 
support all type of schema?

I am running my system in window 8 and with latest version of Drill(1.5) with 
embedded mode.

I am trying to search with same storage plugin.

My Storage Plugin(for SQLServer):

{
  "type" : "jdbc",
  "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
  "url" : "jdbc:sqlserver://;databaseName=",
  "username" : "",
  "password" : "<>",
  "enabled" : true
}
This Plugin has dbo & core schema (both have same type, no special 
permission).Its work for dbo schema where core schema is not working.

DBO Query:

select * from SqlServer.dbo.Attribute; //Its working.
Core Query:

select * from SqlServer.core.Users //Its not working
My question is whether Drill Supports only dbo schemna or all type of schema?


> Apache Drill Schema Support for SQL Server
> --
>
> Key: DRILL-4522
> URL: https://issues.apache.org/jira/browse/DRILL-4522
> Project: Apache Drill
>  Issue Type: Bug
>  Components:  Server
>Affects Versions: 1.5.0
> Environment: Sql Server, Window 8.1 
>Reporter: Sanjiv Kumar
> Fix For: 1.5.0
>
>
> I want to know whether Apache Drill supports only dbo schema?? or will it 
> support all type of schema?
> I am running my system in window 8 and with latest version of Drill(1.6) with 
> embedded mode.
> I am trying to search with same storage plugin.
> My Storage Plugin(for SQLServer):
> {
>   "type" : "jdbc",
>   "driver" : "com.microsoft.sqlserver.jdbc.SQLServerDriver",
>   "url" : "jdbc:sqlserver://;databaseName=",
>   "username" : "",
>   "password" : "<>",
>   "enabled" : true
> }
> This Plugin has dbo & core schema (both have same type, no special 
> permission).Its works for dbo schema where core schema is not working.
> DBO Query:-
> select * from SqlServer.dbo.Attribute; //Its working.
> Core Query:-
> select * from SqlServer.core.Users //Its not working
> My question is whether Drill Supports only dbo schemna or all type of schema?



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

[jira] [Updated] (DRILL-4650) Excel file (.xsl) and Microsoft Access file (.accdb) problem

2016-05-03 Thread Sanjiv Kumar (JIRA) 

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

Sanjiv Kumar updated DRILL-4650:

Description: I am trying to query from excel file(.xsl file) and ms access 
file (.accdb), but i am unable to query from these files in drill. Is there any 
way to query these files. Or any Storage Plugin for query these files.   (was: 
I am trying to query from excel file(.xsl file) and ms access file (.accdb), 
but i am unable to query from excel, but it is not executing. Is there any way 
to query these files. Or any Storage Plugin for query these files. )

>  Excel file (.xsl) and Microsoft Access file (.accdb) problem
> -
>
> Key: DRILL-4650
> URL: https://issues.apache.org/jira/browse/DRILL-4650
> Project: Apache Drill
>  Issue Type: Bug
>Affects Versions: 1.6.0
>Reporter: Sanjiv Kumar
>
> I am trying to query from excel file(.xsl file) and ms access file (.accdb), 
> but i am unable to query from these files in drill. Is there any way to query 
> these files. Or any Storage Plugin for query these files. 



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

[jira] [Created] (DRILL-4650) Excel file (.xsl) and Microsoft Access file (.accdb) problem

2016-05-03 Thread Sanjiv Kumar (JIRA) 
Sanjiv Kumar created DRILL-4650:
---

 Summary:  Excel file (.xsl) and Microsoft Access file (.accdb) 
problem
 Key: DRILL-4650
 URL: https://issues.apache.org/jira/browse/DRILL-4650
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.6.0
Reporter: Sanjiv Kumar


I am trying to query from excel file(.xsl file) and ms access file (.accdb), 
but i am unable to query from excel, but it is not executing. Is there any way 
to query these files. Or any Storage Plugin for query these files. 



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

[jira] [Created] (DRILL-4649) Drill Authentication in Window Operating System

2016-05-03 Thread Sanjiv Kumar (JIRA) 
Sanjiv Kumar created DRILL-4649:
---

 Summary: Drill Authentication in Window Operating System
 Key: DRILL-4649
 URL: https://issues.apache.org/jira/browse/DRILL-4649
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.6.0
Reporter: Sanjiv Kumar


 I am new in Apache Drill.I am running drill in embedded mode with
 window 8.1 operating system.
 
My question is how to authenticate drill. I want if any one start
 drill, it will ask for user name and password to start drill. I know that
 drill use PAM Authentication. But I don't know how to use PAM in window 8.1
 operating system & where  and how to store username & password.  Please
 Suggest me or if possible give me some example how to restrict user to
 access drill in window 8.1 operating system. And How to write custom 
authentication in Window Operating System.



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