Re: Hangout tomorrow (get your tickets now)

We are targeting the next Apache Drill release by the end of this month. Boaz has volunteered to drive the 1.14 release and will send out a separate email about it. Pritesh On 6/12/18, 1:44 PM, "Charles Givre" wrote: Hi Parth, When is the next release of Drill going to be? — C

Re: Hangout tomorrow (get your tickets now)

Hi Parth, When is the next release of Drill going to be? — C > On Jun 12, 2018, at 16:42, Parth Chandra wrote: > > Short summary of the call - > > Attendees: > Abhishek, Aman, Arina, Oleksander, Gautam, Samiksha, Timothy, Vitalii, Parth, > DC, Sorabh, Jyothsna, Chun, Robert, Hau, Boaz, Prites

Re: Hangout tomorrow (get your tickets now)

Short summary of the call - Attendees: Abhishek, Aman, Arina, Oleksander, Gautam, Samiksha, Timothy, Vitalii, Parth, DC, Sorabh, Jyothsna, Chun, Robert, Hau, Boaz, Pritesh, Kunal Arina - case insensitive storage plugin and workspace names General agreement on case insenstive names. Let us im

Re: [DISCUSS] case insensitive storage plugin and workspaces names

Paul, I think this proposal was specific to storage plugin and workspace *names*. And not for the whole of Drill. I agree it makes sense to have these names case insensitive, to improve user experience. The only impact to current users I can think of is if someone created two storage plugins dfs a

Re: [DISCUSS] case insensitive storage plugin and workspaces names

Hi All, As it turns out, this topic has been discussed, in depth, previously. Can't recall if it was on this list, or in a JIRA. We face a number of constraints: * As was noted, for some data sources, the data source itself has case insensitive names. (Windows file systems, RDBMSs, etc.) * In

Re: Hangout tomorrow (get your tickets now)

Is it going on now? On Jun 12, 2018 10:26 PM, "Arina Yelchiyeva" wrote: > You can join the call by the following link: > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc > > Kind regards, > Arina > > On Tue, Jun 12, 2018 at 7:40 PM Samiksha Kapoor < > samikshakapoo...@gmail.c

Re: Hangout tomorrow (get your tickets now)

You can join the call by the following link: https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc Kind regards, Arina On Tue, Jun 12, 2018 at 7:40 PM Samiksha Kapoor wrote: > Hi Parth, > > I tried to join the call but it was not getting connected. I have issue > regarding drill

Re: Hangout tomorrow (get your tickets now)

Hi Parth, I tried to join the call but it was not getting connected. I have issue regarding drill and hive interface. I was not able to query hive tables from drill. Can anyone call me on +91 8367075966 to discuss this? We can also connect on hangout at samikshakapoo...@gmail.com Please help it

Re: [DISCUSS] case insensitive storage plugin and workspaces names

Yes, that seems ok to me...since the plugin name and workspace are logical entities and don't correspond to a path. There could be compatibility issues if certain users have relied on the case-sensitive names, but those would be temporary. Aman On Tue, Jun 12, 2018 at 8:35 AM, Arina Yelchiyeva <

Re: [DISCUSS] case insensitive storage plugin and workspaces names

To make it clear we have three notions here: storage plugin name, workspace (schema) and table name (dfs.root.`/tmp/t`). My suggestion is the following: Storage plugin names to be case insensitive (DFS vs dfs, INFORMATION_SCHEMA vs information_schema). Workspace (schemas) names to be case insensit

Re: [DISCUSS] case insensitive storage plugin and workspaces names

Drill is dependent on the underlying file system's case sensitivity. On HDFS one can create 'hadoop fs -mkdir /tmp/TPCH' and /tmp/tpch which are separate directories. These could be set as workspace in Drill's storage plugin configuration and we would want the ability to query both. If we chan

RE: UnsupportedOperationException: Unsupported type LIST

You are mixing INTs with FLOATs in the list.. 25.42, << float 37.29, << float 10 << int Change 10 to 10.0 -Original Message- From: Paul Rogers [mailto:par0...@yahoo.com.INVALID] Sent: Monday, June 11, 2018 8:48 PM To: user@drill.apache.org Subject: Re: UnsupportedOperationException:

RE: Which perform better JSON or convert JSON to parquet format ?

Python supports tabular structures using pyarrow. https://arrow.apache.org/docs/python/generated/pyarrow.schema.html For nested structures like JSON you have to use C++ (parquet-cpp) https://github.com/apache/parquet-cpp We need more APIs developed to create nested JSON.. -Original Message

Re: Which perform better JSON or convert JSON to parquet format ?

Hi David, How to create the schema first using parquet library ? Can you please give an example? Thanks, Divya On Tue, 12 Jun 2018 at 00:03, Lee, David wrote: > Parquet is faster especially if you are only looking for a subset of json > objects. Every JSON key / array is treated as a column. >

Re: Hangout tomorrow (get your tickets now)

I'd like to discuss case insensitive storage plugin and workspaces names (sent the email to the dev & user mailing lists with the details). Kind regards, Arina On Tue, Jun 12, 2018 at 4:07 AM Timothy Farkas wrote: > Hi, > > I'd like to give the presentation for the resource management proposal.

[DISCUSS] case insensitive storage plugin and workspaces names

Hi all, Currently Drill we treat storage plugin names and workspaces as case-sensitive [1]. Names for storage plugins and workspaces are defined by the user. So we allow to create plugin -> DFS and dfs, workspace -> tmp and TMP. I have a suggestion to move to case insensitive approach and won't al

Re: UnsupportedOperationException: Unsupported type LIST

Hi, Pasting the stack trace here https://pastebin.com/RCK0SrV Yes Kunal , its the similar issue as mentioned in JIRA . Any workaround to create parquet file from JSON file having values as ArrayList ? Thanks, Divya On Tue, 12 Jun 2018 at 11:48, Paul Rogers wrote: