Re: Implementing a custom storage plugin for Drill

[Badrul Chowdhury]

Hi Charles,

That makes sense. I am a new contributor to Drill, so I'll start with a few
small changes to get my feet wet. I will revisit implementing a storage
plugin for elasticsearch in a few weeks once I am comfortable with the
codebase. On another note, my main objective in contributing is to learn,
so the more work that is involved in developing a feature, the better :)


Thanks,
Badrul

On Wed, Jul 24, 2019 at 7:09 PM Charles Givre  wrote:

> Hi Badrul,
> I think this page is seriously out of date.  The copyright at the bottom
> says 2014!   Anyway, I would really like to see more storage plugins added
> to Drill.  With that said, it is not trivial to implement one.  In my
> opinion, an ElasticSearch plugin would be quite valuable. Regarding
> ODBC/JDBC, you can connect TO Drill via ODBC and JDBC, however Drill cannot
> connect to data sources via ODBC, only JDBC.
>
> In theory, there might be situations where you'd want to write a custom
> storage plugin rather than using the generic JDBC connection.  For
> instance, you may have a system which performs much better via its own
> interface rather than JDBC.  I'm not 100% certain that Drill's JDBC storage
> plugin supports pushdown projection as well.  So there may be a use case
> for it. But... it's a lot of work.
>
> -- C
>
>
> > On Jul 24, 2019, at 6:53 PM, Badrul Chowdhury <
> badrulchowdhur...@gmail.com> wrote:
> >
> > Hi,
> >
> > The list of suggested contributions here
> > includes
> > writing a custom storage plugin for SQL databases. Drill already supports
> > ODBC, so I was wondering why we would want to separately write custom
> > plugins for different SQL backends?
> >
> >
> > Thanks,
> > Badrul
>
>

-- 

Cheers,
Badrul

Re: [ANNOUNCE] New Committer: Igor Guzenko

[Vitalii Diravka]

Congratulations Igor! It is well deserved!

Kind regards
Vitalii


On Wed, Jul 24, 2019 at 7:58 PM Gautam Parai  wrote:

> Congratulations Igor!
>
> Gautam
>
> On Tue, Jul 23, 2019 at 12:47 PM Paul Rogers 
> wrote:
>
> > Congrats Igor!
> > Thanks,
> > - Paul
> >
> >
> >
> > On Monday, July 22, 2019, 07:02:44 AM PDT, Arina Ielchiieva <
> > ar...@apache.org> wrote:
> >
> >  The Project Management Committee (PMC) for Apache Drill has invited Igor
> > Guzenko to become a committer, and we are pleased to announce that he has
> > accepted.
> >
> > Igor has been contributing into Drill for 9 months and made a number of
> > significant contributions, including cross join syntax support, Hive
> views
> > support, as well as improving performance for Hive show schema and unit
> > tests. Currently he is working on supporting Hive complex types
> > [DRILL-3290]. He already added support for list type and working on
> struct
> > and canonical map.
> >
> > Welcome Igor, and thank you for your contributions!
> >
> > - Arina
> > (on behalf of the Apache Drill PMC)
> >
>

[jira] [Created] (DRILL-7332) Drill requires parentheses in the empty file for 'LOAD' argument in the 'CREATE SCHEMA' command

[Denys Ordynskiy (JIRA)]

Denys Ordynskiy created DRILL-7332:
--

 Summary: Drill requires parentheses in the empty file for 'LOAD' 
argument in the 'CREATE SCHEMA' command
 Key: DRILL-7332
 URL: https://issues.apache.org/jira/browse/DRILL-7332
 Project: Apache Drill
  Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Denys Ordynskiy
Assignee: Arina Ielchiieva
 Fix For: 1.17.0


Description:
 - created csvh table: {color:#205081}create table dfs.tmp.`test_table` (col1) 
as select full_name from cp.`employee.json` limit 3;{color}
 - created text file on the local file system `for_load` with text without 
parentheses: {color:#14892c}col1 varchar not null{color}
 - created some schema file: {color:#205081}create or replace schema *LOAD* 
'file:///home/user/for_load' for table dfs.tmp.`test_table` properties 
('drill.strict' = 'false');{color} - schema was created successfully;
- remove all text from the `for_load` file and try to create the same schema: 
{color:#205081}create or replace schema *LOAD* 'file:///home/user/for_load' for 
table dfs.tmp.`test_table` properties ('drill.strict' = 'false');{color}

*Actual result:*
Drill throws an error:
{color:#d04437}Error: RESOURCE ERROR: Unable to parse schema []: Line [1], 
position [0], offending symbol [@0,0:-1='',<-1>,1:0]: mismatched input 
'' expecting {'(', ID, QUOTED_ID}

Error while preparing / creating schema for [%s] dfs.tmp.test_table

[Error Id: faad9c09-2e3e-428c-bd7a-6da8832a943b ] (state=,code=0){color}

*Expected result:*
Since Drill doesn't require parentheses for non empty `for_load` file (with 
some columns),
It couldn't require parentheses for the empty file, used in the `LOAD` argument.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)