RE: [E] Re: dfs filename

Thanks. I've started a track on that. Do you know of any workaround in the meantime? Thanks, Scott Wilburn -Original Message- From: Abhishek Girish [mailto:abhishek.gir...@gmail.com] Sent: Monday, March 21, 2016 02:40 PM To: user Subject: [E] Re: dfs filename This is currently not

Re: Case-sensitive view names?

Table and view names are case sensitive when using the FileSystemPlugin and a case sensitive filesystem. They are not case sensitive if the filesystem is case insensitive. -- Jacques Nadeau CTO and Co-Founder, Dremio On Mon, Mar 21, 2016 at 2:50 PM, Abhishek Girish

Re: Case-sensitive view names?

I think that part of the doc needs to be updated. Table names & view names are case-sensitive. Also the doc section about double-quoting names is in-correct. Using double quotes gives us a SQL parse error. On Mon, Mar 21, 2016 at 1:27 PM, Christopher Matta wrote: > I’m

Re: dfs filename

This is currently not supported. You could track DRILL-3474 / DRILL-3559 for updates. On Mon, Mar 21, 2016 at 2:13 PM, Wilburn, Scott < scott.wilb...@verizonwireless.com.invalid> wrote: > Hello,

dfs filename

Hello, Is there a way to query dfs csv files in multiple directories and include the filename as a field in the output? I created a view that is able to query over all of my directories, but I really need to know which file each record came from. For example, if my records have two columns,

Re: Moving to HBase 1.1 [DRILL-4199]

With the recent issues that have been discussed on other threads related to correctness issues when using our current client I agree we should upgrade. +1 Jason Altekruse Software Engineer at Dremio Apache Drill Committer On Mon, Mar 21, 2016 at 1:18 PM, Aditya wrote: > Hi, >

Case-sensitive view names?

I’m experiencing case-sensitive view names, the drill documentation here: https://drill.apache.org/docs/lexical-structure/#case-sensitivity doesn't explicitly state weather view names are case-insensitive: 0: jdbc:drill:> select state, count(1) from `yelp/yelp_academic_dataset_business.json`

Moving to HBase 1.1 [DRILL-4199]

Hi, HBase has moved to 1.1 branch as their latest stable release[1] and since it is wire compatible with 0.98 releases, I'd like to propose that Drill updates its supported HBase release to 1.1. Essentially, it means that we update the HBase clients bundled with Drill distribution to latest

Re: Drill query does not return all results from HBase

I did not see any issue when running with HBase 0.98.7 client bundled with Drill against HBase 1.1 servers. I have just assigned DRILL-4199[1] to myself to evaluate moving to HBase 1.1 in next Drill release. [1] https://issues.apache.org/jira/browse/DRILL-4199 On Mon, Mar 21, 2016 at 12:13 PM,

RE: Drill query does not return all results from HBase

Aditya, Looking into the bug we read that the behavior will still occur if the hbase-client version does not include the fix (between a 0.98 client and 1.0 server). The hbase-client used by Drill under jars/3rdparty is hbase-client-0.98.7-hadoop2.jar which does not include the fix. I updated

RE: Drill query does not return all results from HBase

Thanks Aditya, I also see that the bug was backported in CDH 5.4.3: https://archive.cloudera.com/cdh5/cdh/5/hbase-1.0.0-cdh5.4.3.releasenotes.html. I tested Drill on CDH version 5.4.2, 5.4.3, 5.4.7, and 5.5.2 and see the same behavior. Kevin From: Aditya [mailto:adityakish...@gmail.com]

Re: Drill query does not return all results from HBase

Since I suspected that it was a bug in HBase, I tried it with the original version you reported in the first post in this thread, i.e. CDH 5.4.3. If it was back-ported to 5.4.7, upgrading should fix this issue. On Mon, Mar 21, 2016 at 10:18 AM, Kevin Verhoeven wrote:

RE: Drill query does not return all results from HBase

Aditya, Thank you for your help. What version of CDH are you running? I contacted Cloudera and they stated that bug HBASE-13262 is backported into CDH 5.4.7. Thanks, Kevin From: Aditya [mailto:adityakish...@gmail.com] Sent: Sunday, March 20, 2016 10:45 PM To: Kumiko Yada

Re: Making a Drill plugin as "runnable jar"

Thanks! Appreciated feedback. I’m not on that list so I’ll try the Drill slack group instead. Regards, Magnus > 21 mar 2016 kl. 16:34 skrev Andries Engelbrecht : > > Magnus, > > This question may be better to post on the dev list than the user list. > > --Andries

Re: Making a Drill plugin as "runnable jar"

Magnus, This question may be better to post on the dev list than the user list. --Andries > On Mar 21, 2016, at 8:32 AM, Magnus Pierre wrote: > > I am messing about with refining my XML parser for Apache Drill, and I would > like to make a simple cmd-line interface

Making a Drill plugin as "runnable jar"

I am messing about with refining my XML parser for Apache Drill, and I would like to make a simple cmd-line interface towards the XML parser i built (which is not dependent on any Drill code, but used by Drill in my plugin), in the same jar, by providing a simple main making it possible to

Regarding Help

Hello Drill team, I am Pawan Pawar, Can you please help me, I have few questions regarding drill functionality. I have my own in memory database, I want it to make it distributed dbsm, so I need to implement distributed query engine, can I use driil to make it distributed and how? Please help me

IllegalStateException: Memory was leaked by query - Drill error on wide table, but OK on a narrow but longer table.

We are converting some raw CMS data from csv to parquet using Drill, and using partitioning as we go. Query 1 runs OK on a narrower file: size: 13G Mar 16 18:20 out_revenuej_lds_100_201412.csv (Month 12 file) 13G Mar 16 16:37 out_claimsj_lds_100_2014_q1.csv (Quarter 1 file) q1 has 198 columns;