Re: Drill Build Issues

Can some MapR folks help see what happened to the maven repo hosted at http://repository.mapr.com/maven/? Will MapR continue to host such repo? On Thu, Oct 31, 2019 at 5:20 AM Charles Givre wrote: > > Hello all, > I'm having some issues building Drill from source. I'm getting an error >

Re: Questions about bushy join

I'm not sure how you got the conclusion that LoptOptmizeJoinRule would not produce bushy tree join plan. I just tried with tpch Q5 and Q10 on the sample dataset, and seems that the plans that I got are not left-deep join tree. ( I could not upload an image to show the visualized plan for those

Re: Drill Profile Management

two things that might be worth considering. 1. Add an option to persistent the profile to a file, only if query elapse time exceeds a certain threshold (say 10 seconds)? Normally, people will need look into profiles just to figure out performance bottleneck. It probably makes sense to only store

Re: Drill in the distributed compute jungle

The idea of making library in stead of service sounds to me very interesting. If we could abstract Drill's run-time relational operators into an independent library, people could easily leverage it to build their own sql query engine, together with some scheduling service, in stead of starting

Re: Contrib module not in root pom.xml?

Looking at the code change history, seems it's DRILL-1548 that removes 'contrib' models, and put it under 'build-contrib" profile. 1. https://issues.apache.org/jira/browse/DRILL-1548 2. https://github.com/apache/drill/commit/a8b309a792dae2c85d5fa4d368136cd6e45178ea On Tue, Sep 11, 2018 at 6:21

Re: [DISCUSSION] Does schema-free really need

btw: In one project that I'm currently working (an application related to IOT), I'm leveraging Drill's schema-on-read ability, without requiring user to predefine table DDL. On Wed, Aug 15, 2018 at 11:15 PM, Jinfeng Ni wrote: > The use case Weijie described seems to fall into the categ

Re: [DISCUSSION] Does schema-free really need

The use case Weijie described seems to fall into the category of traditional data warehouse, i.e, schemas are predefined by users, data strictly conforms to schema. Certainly this is one important uses, and I agreed that the schema-on-read logic in Drill run-time indeed is a disadvantage for such

Re: [RESULT] [VOTE] Apache Drill release 1.14.0 - RC3

The previously unit test failure (TestImpersonationMetadata) probably was caused by some security setting on the cluster I used. Agreed that it should not block the release. On Fri, Aug 3, 2018 at 6:54 PM, Boaz Ben-Zvi wrote: > The vote on RC3 for the Drill 1.14.0 release passed at last

Re: [VOTE] Apache Drill release 1.14.0 - RC3

efault. Not sure why they fail for > you - are they intermittent or consistent? > > On Fri, Aug 3, 2018 at 3:57 PM Jinfeng Ni wrote: > > > The test case seems to be different, the error seems to be different > > (permission error vs validation error) , also the machine I used is

Re: [VOTE] Apache Drill release 1.14.0 - RC3

ing issues. Possibly same this time ? > > Boaz > > =-=-=-=-=-=-=-= 3 / 2 / 2017 Jinfeng Ni =-=-=-=-=-=-= > > Also, I'm seeing intermittent failures in unit test > TestInBoundImpersonation. Seems to me the failure is caused by the > permission of view file. > >

Re: [VOTE] Apache Drill release 1.14.0 - RC3

I keep seeing multiple unit test failures in TestImpersonationMetadata. If I run the test case individually, still hit the error. I notice those testcases are marked as "SlowTest", "SecurityTest". Did people have a way to skip those tests, or those failures are probably caused by environment

Re: [ANNOUNCE] New PMC Chair of Apache Drill

Congratulations, Arina! Thank you, Aman, for leading the Drill community over the past 1 year! Jinfeng On Thu, Jul 19, 2018 at 1:47 PM, Robert Hou wrote: > Congratulations, Arina! > > --Robert > > On Wed, Jul 18, 2018 at 9:12 PM, Sorabh Hamirwasia > wrote: > > > Congratulations Arina! > > >

Re: "Death of Schema-on-Read"

I feel it's probably premature to cal it "death of schema-on-read" just based on one application case. For one product I have been working on recently, one use case is for IOT related application where data is sent from a variety of small devices (sensors, camera, etc). It would be a hard

Re: [ANNOUNCE] New Committer: Vitalii Diravka

Congratulations and welcome, Vitalii! Jinfeng On Wed, Dec 13, 2017 at 9:55 AM, Vitalii Diravka wrote: > Thank you all for your kind words > > Kind regards > Vitalii > > On Wed, Dec 13, 2017 at 5:38 AM, weijie tong > wrote: > > >

Re: [ANNOUNCE] New Committer: Boaz Ben-Zvi

Congratulations and welcome, Boaz! Jinfeng On Wed, Dec 13, 2017 at 11:17 AM, Robert Hou wrote: > Congratulations, Boaz! > > > --Robert > > > From: Paul Rogers > Sent: Wednesday, December 13, 2017 11:02 AM > To:

Re: [VOTE] Release Apache Drill 1.12.0 - rc1

I also saw failures in TestGracefulShutdown and TestImpersonationMetadata, when run "mvn clean install " on Mac. On Wed, Dec 13, 2017 at 12:01 PM, Parth Chandra wrote: > I've resolved the problem causing TestGracefulShutdown.testRestApiShutdown > to fail for me. ( I had

Re: Implicit columns and maps

I think it would make sense to treat the implicit columns as reserved words, and if user wants to use those names as regular column, or table name, or any objects in the system, they should use quoted identifier. select suffix from t1; // implicit columns takes precedence select `suffix` from

Re: [ANNOUNCE] New Committer: Kamesh Bhallamudi

Congratulations and welcome, Kamesh! -Jinfeng On Thu, Oct 26, 2017 at 1:32 PM, Abhishek Girish wrote: > Congratulations, Kamesh! > > On Thu, Oct 26, 2017 at 1:17 PM, Parth Chandra wrote: > > > The Project Management Committee (PMC) for Apache Drill has

Re: [ANNOUNCE] New Committer: Anil Kumar Batchu

Congratulations and welcome, Anil! Jinfeng On Thu, Oct 26, 2017 at 1:31 PM, Abhishek Girish wrote: > Congratulations, Anil! > > On Thu, Oct 26, 2017 at 1:17 PM, Parth Chandra wrote: > > > The Project Management Committee (PMC) for Apache Drill has

Re: Switch between new parquet reader and old one

That makes sense. We should only check the requested columns, not every column in parquet file, to decide which parquet reader to use. On Wed, Sep 13, 2017 at 4:17 PM, Damien Profeta wrote: > Hi, > > I was looking at the code that read the parquet file and noticed

[jira] [Created] (DRILL-5773) Project pushdown into a subquery with select *

Jinfeng Ni created DRILL-5773: - Summary: Project pushdown into a subquery with select * Key: DRILL-5773 URL: https://issues.apache.org/jira/browse/DRILL-5773 Project: Apache Drill Issue Type

Re: multiple logback.xml in the project

own logback.xml and they all end up > being > >>> on the classpath during unit test. Which one is used during unit test > >>> depends on their order in the classpath and my experience with maven > >>> dependency says that the order is undefined. Do I miss somethi

[jira] [Resolved] (DRILL-4686) Aggregation query over HBase table results in IllegalStateException: Failure while reading vector

[ https://issues.apache.org/jira/browse/DRILL-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4686. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of patch for DRILL-5546. commit id

[jira] [Resolved] (DRILL-4734) Query against HBase table on a 5 node cluster fails with SchemaChangeException

[ https://issues.apache.org/jira/browse/DRILL-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-4734. --- Resolution: Fixed Fix Version/s: 1.12.0 Although I could not get enough information

[jira] [Resolved] (DRILL-5185) Union all not passing type info when the output contains 0 rows

[ https://issues.apache.org/jira/browse/DRILL-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5185. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of DRILL-5546. Commit id

[jira] [Resolved] (DRILL-5464) Fix JSON reader when it deals with empty file

[ https://issues.apache.org/jira/browse/DRILL-5464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5464. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as a part of patch for DRILL-5546, commit id

[jira] [Resolved] (DRILL-5327) Hash aggregate can return empty batch which can cause schema change exception

[ https://issues.apache.org/jira/browse/DRILL-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5327. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed as part of patch for DRILL-5546. Commit id

[jira] [Resolved] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException even when data does not have different schema

[ https://issues.apache.org/jira/browse/DRILL-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5480. --- Resolution: Fixed Fix Version/s: 1.12.0 Mark it resolved, as the issue was fixed as part

[jira] [Resolved] (DRILL-5546) Schema change problems caused by empty batch

[ https://issues.apache.org/jira/browse/DRILL-5546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5546. --- Resolution: Fixed Fix Version/s: 1.12.0 Fixed in commit

[jira] [Created] (DRILL-5768) Drill planer should not allow select * with group by clause

Jinfeng Ni created DRILL-5768: - Summary: Drill planer should not allow select * with group by clause Key: DRILL-5768 URL: https://issues.apache.org/jira/browse/DRILL-5768 Project: Apache Drill

Re: Disable Lilith SOCKET connection by default.

If you run the whole unit test suite, you do not have to open Lilith at the same time. My experience is Lilith will significantly slow down unit test suite running, and even fail testcases, as Drill's code put many DEBUG log which chocked Lilith. Lilith is useful only if you are running

Re: Working on upgrade Drill Calcite version

It's great to hear that someone is working on moving Drill on new Calcite release! As someone who did similar job in last two rebase work, I could see that there would be many regressions to fix. Please let me know if I can provide any help. I thought we have pushed almost Drill specific commits

[jira] [Created] (DRILL-5754) Test framework does not enforce column orders

Jinfeng Ni created DRILL-5754: - Summary: Test framework does not enforce column orders Key: DRILL-5754 URL: https://issues.apache.org/jira/browse/DRILL-5754 Project: Apache Drill Issue Type: Bug

[jira] [Created] (DRILL-5747) Drill should put directory name field in same sequence w.r.t regular column for select * query

Jinfeng Ni created DRILL-5747: - Summary: Drill should put directory name field in same sequence w.r.t regular column for select * query Key: DRILL-5747 URL: https://issues.apache.org/jira/browse/DRILL-5747

Re: Failing Tests In Master

Running on CentOS (JDK1.7) with latest master against those unit testcase, and I did not see errors. Any difference in terms of OS/JDK? git log commit e9065b55ea560e7f737d6fcb4948f9e945b9b14f mvn -DfailIfNoTests=false

[jira] [Resolved] (DRILL-5685) Provide a way to set common environment variable between sqlline and Drillbit differently.

[ https://issues.apache.org/jira/browse/DRILL-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5685. --- Resolution: Fixed Fixed in ae123e166af2ddb22c79b8cb93278a66fccc3be4 > Provide a way to set com

Re: Continuous Integration Tests Failing

I saw that the last commit (9d1d815), which upgrades drill version to 1.12.0-SNAPSHOT, has CI failure, while the two commits before that commit were shown to have successful CI test. Not clear why update the version number would cause such difference. On Mon, Aug 7, 2017 at 8:51 AM, Charles Givre

Re: [ANNOUNCE] New PMC member: Arina Ielchiieva

Congratulations, Arina! On Wed, Aug 2, 2017 at 11:27 AM, Kunal Khatua wrote: > Congratulations, Arina!! > > > Thank you for your contributions to Drill ! > > > ~ Kunal > > > From: Aman Sinha > Sent: Wednesday, August 2,

Re: [VOTE] Release Apache Drill 1.11.0 - rc0

Downloaded src and built with unit test on CentOS 6.4. Deploy to a 2 nodes cluster. Run a couple of tpcds queries over scale factor 1 parquet data. Tried query cancel while running tpcds queries. Run yelp tutorial queries over json data. Verified maven artifacts with a simple Drill application.

[jira] [Created] (DRILL-5683) Incorrect query result when query uses NOT(IS NOT NULL) expression

Jinfeng Ni created DRILL-5683: - Summary: Incorrect query result when query uses NOT(IS NOT NULL) expression Key: DRILL-5683 URL: https://issues.apache.org/jira/browse/DRILL-5683 Project: Apache Drill

[jira] [Created] (DRILL-5681) Incorrect query result when query uses star and correlated subquery

Jinfeng Ni created DRILL-5681: - Summary: Incorrect query result when query uses star and correlated subquery Key: DRILL-5681 URL: https://issues.apache.org/jira/browse/DRILL-5681 Project: Apache Drill

Re: Questions about Drill's multi-thread model

What do you mean by "one query was blocked by the storage"? Are the other queries blocked in query planning time, or execution time? I recalled someone asked the problem related to long query planning. Turns out that if one enabled storage plugin is slow to access, it would affect every query,

Re: Why Drill required a special Calcite fork ?

Getting Drill off the Calcite fork is clearly the best solution. From what I know [1], people have spend quite lots of effort to push the patches in Drill's fork to Calcite master. The next step is to put Drill on top of Calcite master or latest release, and resolve regressions. RomanK spent

Re: [DISCUSS] Drill 1.11.0 release

with that? > > We are seeing some stress test regression failures that, I’m told, will > show up as JIRA entries shortly. > > - Paul > > > On Jul 12, 2017, at 11:05 AM, Jinfeng Ni <j...@apache.org> wrote: > > > > I put some analysis in DRILL-5

Re: [DISCUSS] Drill 1.11.0 release

-5660 where we need to bump up > > > > parquet metadata version. > > > > @Vitalii > > > > Do you have any ETA for the fix? > > > > > > > > Kind regards > > > > Arina > > > > > > > > On Tue, Jul 11, 2017 at 6:02 AM, Boaz B

Re: [DISCUSS] Drill 1.11.0 release

Hi Arina, It has been a while since we discussed 1.11.0 release. Any update on the new release plan? Do we have a cut-off date ? In the past, I believe Drill release is a time-bounded, not feature bounded. If certain fixes/features could not make it within a certain time-frame, we had better

[jira] [Created] (DRILL-5667) Project operator would change output field order if convertfromJSON is used

Jinfeng Ni created DRILL-5667: - Summary: Project operator would change output field order if convertfromJSON is used Key: DRILL-5667 URL: https://issues.apache.org/jira/browse/DRILL-5667 Project: Apache

Re: [ANNOUNCE] New PMC Chair of Apache Drill

Congratulations, Aman! On Fri, Jun 23, 2017 at 12:54 PM, Kunal Khatua wrote: > Congratulations ! > > -Original Message- > From: Arina Yelchiyeva [mailto:arina.yelchiy...@gmail.com] > Sent: Friday, June 23, 2017 12:47 PM > To: dev@drill.apache.org > Subject: Re:

Re: [DISCUSS] Drill 1.11.0 release

+1 do Drill 1.11 release soon, and Arina as the new release manager. On Fri, Jun 23, 2017 at 9:49 AM, Aman Sinha wrote: > Sounds good, Arina and thanks for volunteering! I think it will be a good > experience for you doing the release. Reach out to past release

Re: FindHardDistributionScans throws a NPE while visiting a TableScan

unwrap() essentially is doing a cast. If it returns null for unwrap(DrillTranslatableTable.class) or unwrap(DrillTable.class), it means the table associate with this TableScan does not implement either interface. My suspicion is JDBC storage plugin returns JdbcTable [1], unlikely other storage

[jira] [Created] (DRILL-5586) UnionAll operator does more than necessary value vector allocation and copy

Jinfeng Ni created DRILL-5586: - Summary: UnionAll operator does more than necessary value vector allocation and copy Key: DRILL-5586 URL: https://issues.apache.org/jira/browse/DRILL-5586 Project: Apache

[jira] [Created] (DRILL-5585) UnionAll operator generates run-time code for every incoming batch

Jinfeng Ni created DRILL-5585: - Summary: UnionAll operator generates run-time code for every incoming batch Key: DRILL-5585 URL: https://issues.apache.org/jira/browse/DRILL-5585 Project: Apache Drill

Re: [ANNOUNCE] New Committer: Laurent Goujon

Congratulations, Laurent! On Fri, Jun 9, 2017 at 10:02 AM, Julien Le Dem wrote: > Congrats Laurent! > > On Fri, Jun 9, 2017 at 9:57 AM, rahul challapalli < > challapallira...@gmail.com> wrote: > > > Congratulations Laurent! > > > > On Fri, Jun 9, 2017 at 9:49 AM, Paul

Re: Thinking about Drill 2.0

Agreed with the two items Parth listed: Schema free support and improve Drill's execution architecture. Schema free (or Schema-on-read) is one main feature that differentiates Drill from other similar projects. There seems to be a still long list to improve towards fully support of this feature.

[jira] [Resolved] (DRILL-5485) Remove WebServer dependency on DrillClient

[ https://issues.apache.org/jira/browse/DRILL-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5485. --- Resolution: Fixed Fixed in 874bf6296dcd1a42c7cf7f097c1a6b5458010cbb > Remove WebServer depende

Re: Upgrading Calcite's version

DRILL-3993 is the JIRA for 2nd option. 1. https://issues.apache.org/jira/browse/DRILL-3993 On Fri, Jun 2, 2017 at 11:26 AM, rahul challapalli < challapallira...@gmail.com> wrote: > Yes, drill has its own fork of calcite. You have 2 options here > > 1. Hand pick the specific changes from

[jira] [Created] (DRILL-5559) Incorrect query result when querying json files with schema change

Jinfeng Ni created DRILL-5559: - Summary: Incorrect query result when querying json files with schema change Key: DRILL-5559 URL: https://issues.apache.org/jira/browse/DRILL-5559 Project: Apache Drill

Schema change issues caused by empty batch

Hi all, I created DRILL-5546 to track problems related schema change caused by empty batch last Friday, along with an initial proposal to address the problem. Please put you have suggestion/comments in the JIRA. Thanks, Jinfeng https://issues.apache.org/jira/browse/DRILL-5546

[jira] [Created] (DRILL-5546) Schema change problems caused by empty batch

Jinfeng Ni created DRILL-5546: - Summary: Schema change problems caused by empty batch Key: DRILL-5546 URL: https://issues.apache.org/jira/browse/DRILL-5546 Project: Apache Drill Issue Type: Bug

Re: [ANNOUNCE] New Committer: Paul Rogers

Congratulations, Paul! On Fri, May 19, 2017 at 9:36 AM, Aman Bawa wrote: > Congratulations, Paul! > > On 5/19/17, 8:22 AM, "Aman Sinha" wrote: > > The Project Management Committee (PMC) for Apache Drill has invited > Paul > Rogers to become a

Re: [DRILL HANGOUT] Topics for 5/16/2017

017 at 10:01 AM, Jinfeng Ni <j...@apache.org> wrote: > We will start hangout shortly. > > https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc > > > On Mon, May 15, 2017 at 9:53 PM, Jinfeng Ni <j...@apache.org> wrote: > > My feeling is that e

HBase scan : expected results handling null ?

Hi all, I was looking at HBase scan operator, and noticed one interesting behavior regarding how Drill/HBase reader handling a column with nulll value. 1. Date prepare (HBase shell). A table with 3 rows. one row has 'addr.city' column only, while the other two rows have column 'order.id' only.

Re: [DRILL HANGOUT] Topics for 5/16/2017

We will start hangout shortly. https://plus.google.com/hangouts/_/event/ci4rdiju8bv04a64efj5fedd0lc On Mon, May 15, 2017 at 9:53 PM, Jinfeng Ni <j...@apache.org> wrote: > My feeling is that either temp table or putting 100k values into a > separate parquet files makes more sense

Re: [DRILL HANGOUT] Topics for 5/16/2017

> > Is there any better way to go around this problem or can we just solve this > problem with simple configuration changes ? > > Regards, > Jasbir Singh > > > -Original Message- > From: Jinfeng Ni [mailto:j...@apache.org] > Sent: Tuesday, May 16, 2017 2

[DRILL HANGOUT] Topics for 5/16/2017

Hi All, Out bi-weekly Drill hangout is tomorrow (5/16/2017, 10AM PDT). Please respond with suggestion of topics for discussion. We will also collect topics at the beginning of handout tomorrow. Thanks, Jinfeng

[jira] [Created] (DRILL-5480) Empty batch returning from HBase may cause SchemChangeException or incorrect query result

Jinfeng Ni created DRILL-5480: - Summary: Empty batch returning from HBase may cause SchemChangeException or incorrect query result Key: DRILL-5480 URL: https://issues.apache.org/jira/browse/DRILL-5480

[jira] [Created] (DRILL-5464) Fix JSON reader when it deals with empty file

Jinfeng Ni created DRILL-5464: - Summary: Fix JSON reader when it deals with empty file Key: DRILL-5464 URL: https://issues.apache.org/jira/browse/DRILL-5464 Project: Apache Drill Issue Type: Bug

Re: Parquet, Arrow, and Drill Roadmap

> > - What the two readers are (is one a special drill thing, is the other a > standard reader from the parquet project?) > - What is the eventual goal here... to be able to use and switch between > both? To provide the option? To have code parity with another project? Both readers were for

[jira] [Created] (DRILL-5459) Extend physical operator test framework to test mini plans consisting of multiple operators

Jinfeng Ni created DRILL-5459: - Summary: Extend physical operator test framework to test mini plans consisting of multiple operators Key: DRILL-5459 URL: https://issues.apache.org/jira/browse/DRILL-5459

[jira] [Resolved] (DRILL-5373) Drill JDBC error in the process of connection via SQuirrel: java.lang.NoClassDefFoundError: javax/validation/constraints/NotNull

[ https://issues.apache.org/jira/browse/DRILL-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jinfeng Ni resolved DRILL-5373. --- Resolution: Fixed Fixed in commit d3718a62e2315a601615db8803cdfdcc3cedab82 > Drill JDBC er

Re: Submitting physical plans

There is a "submit_plan" script, under bin/ directory. You may want to take a look and have a try. You are right that we used to use that tool to submit physical plan directly. I'm not sure if that tool is maintained throughout all the releases. On Wed, Mar 29, 2017 at 10:47 AM, rahul challapalli

[jira] [Created] (DRILL-5378) Put more information into SchemaChangeException when HashJoin hit SchemaChangeException

Jinfeng Ni created DRILL-5378: - Summary: Put more information into SchemaChangeException when HashJoin hit SchemaChangeException Key: DRILL-5378 URL: https://issues.apache.org/jira/browse/DRILL-5378

Re: [ANNOUNCE] Apache Drill 1.10.0 Released

nk you for your combined time & effort. It's greatly appreciated! > > On Thu, Mar 16, 2017 at 12:53 PM, Jinfeng Ni <j...@apache.org> wrote: >> Thanks Abhishek for the reminder. >> >> I just pushed 1.10.0 branch to Github. >> >> On Thu, Mar 16, 2017 at 9:

Re: [Drill 1.9.0] : [CONNECTION ERROR] :- (user client) closed unexpectedly. Drillbit down?

Very interesting findings, Francois. Thanks for sharing them with the community. The change of max_per_node and affinity_factor seems to reduce the possibility of one drillbit was hitting overload issue because of either CPU or Network contention. In our in-house testing, we also noticed that

Re: [Drill 1.9.0] : [CONNECTION ERROR] :- (user client) closed unexpectedly. Drillbit down?

Very interesting findings, Francois. Thanks for sharing them with the community. The change of max_per_node and affinity_factor seems to reduce the possibility of one drillbit was hitting overload issue because of either CPU or Network contention. In our in-house testing, we also noticed that

Re: Drill date & time types encoding

and "EXTRACT(HOUR > FROM ts)” and “ts + INTERVAL ‘1’ DAY” all make sense. > > Julian > > > >> On Mar 16, 2017, at 4:54 PM, Jinfeng Ni <j...@apache.org> wrote: >> >> On Thu, Mar 16, 2017 at 4:41 PM, Julian Hyde <jh...@apache.org >> &

Re: Drill date & time types encoding

On Thu, Mar 16, 2017 at 4:41 PM, Julian Hyde <jh...@apache.org> wrote: > >> On Mar 16, 2017, at 4:25 PM, Jinfeng Ni <j...@apache.org> wrote: >> >> Time/Timestamp without t/z should be interpreted as local time. > > > No. > > If I am in pacific time a

Re: Drill date & time types encoding

My understanding is TIME/TIMESTAMP in Drill is TIME/TIMESTAMP without timezone. TimeStampTZ is for TIMESTAMP with timezone, which Drill probably does not fully support. SQL standards has DATE, TIME WITHOUT TIME ZONE, TIMESTAMP WITHOUT TIME ZONE, TIME WITH TIME ZONE, or TIMESTAMP WITH TIME ZONE.

[jira] [Created] (DRILL-5359) ClassCastException when push down filter on the output of flatten into parquet scan

Jinfeng Ni created DRILL-5359: - Summary: ClassCastException when push down filter on the output of flatten into parquet scan Key: DRILL-5359 URL: https://issues.apache.org/jira/browse/DRILL-5359 Project

Re: [ANNOUNCE] Apache Drill 1.10.0 Released

h creation still pending? > > -Abhishek > ________ > From: Jinfeng Ni <j...@apache.org> > Sent: Thursday, March 16, 2017 8:40:07 AM > To: dev; user > Subject: [ANNOUNCE] Apache Drill 1.10.0 Released > > On behalf of the Apache Drill community, I

Re: Reg: Column name is not passed to RDBMS

Can you please first check the EXPLAIN PLAN output for your query? The first step is to figure out whether it's planner issue, or execution issue. On Thu, Mar 16, 2017 at 7:39 AM, Nishith Kumar Nayak wrote: > Hi, > > While trying to run SQL query for RDBMS source like

[ANNOUNCE] Apache Drill 1.10.0 Released

On behalf of the Apache Drill community, I am happy to announce the release of Apache Drill 1.10.0. For information about Apache Drill, and to get involved, visit the project website [1]. This release introduces new features and enhancements, including CREATE TEMPORARY TABLE AS command, Kerberos

[RESULT] [VOTE] Release Apache Drill 1.10.0 rc0

The vote passes. Thanks to everyone who has tested the release candidate and given their comments and votes. Final tally: 3x +1 (binding): Aman, Parth, Jinfeng 2x +1 (non-binding): Arina, Gautam No 0s or -1s. I'll push the release artifacts and send an announcement once propagated. Thanks,

Re: [VOTE] Release Apache Drill 1.10.0 - rc0

found one issue: >> >>https://issues.apache.org/jira/browse/DRILL-5338 >> >> >>Kind regards >>Arina >> >>On Thu, Mar 9, 2017 at 9:31 AM, Jinfeng Ni <j...@apache.org> wrote: >> >>> Hello all, >>

[VOTE] Release Apache Drill 1.10.0 - rc0

Hello all, I'd like to propose the first release candidate (rc0) of Apache Drill, version 1.10.0. The release candidate covers a total of 126 resolved JIRAs [1]. Thanks to everyone who contributed to this release. The tarball artifacts are hosted at [2] and the maven artifacts are hosted at

Re: Time for 1.10 release

I merged the PR for DRILL-5326 to master branch, and will start building RC0 shortly. On Tue, Mar 7, 2017 at 2:13 PM, Jinfeng Ni <j...@apache.org> wrote: > Yes, DRILL-5326 is blocking issue for RC0, if build with unit test fails. > > > On Tue, Mar 7, 2017 at 12:55 PM

Re: Time for 1.10 release

you post a pull request as soon > as you’re ready with the change. > > Thanks. > > -- Zelaine > > On 3/3/17, 2:13 PM, "Jinfeng Ni" <j...@apache.org> wrote: > > Pushed the patch for DRILL-5313, as well as two other patches which > were reviewed be

Re: Time for 1.10 release

Pushed the patch for DRILL-5313, as well as two other patches which were reviewed before 3/1. I will start build RC0 after QA sanity test is completed. On Thu, Mar 2, 2017 at 11:00 PM, Jinfeng Ni <j...@apache.org> wrote: > Looks like the C++ client is not able to built successfully [

Re: Time for 1.10 release

, Jinfeng Ni <j...@apache.org> wrote: > I missed 5208, because it did not show up in Paul's list when he replied to > this thread. > > On Thu, Mar 2, 2017 at 2:58 PM Zelaine Fong <zf...@mapr.com> wrote: >> >> Jinfeng, >> >> I notice the following Jira ha

Re: Time for 1.10 release

LL-5208 > > Was this one overlooked? > > -- Zelaine > > On 3/2/17, 1:04 PM, "Jinfeng Ni" <j...@apache.org> wrote: > > The following PRs have been merged to Apache master. > > DRILL-4994 > DRILL-4730 > DRILL-5301 > DRILL-5167 >

Re: Time for 1.10 release

the vote. Thanks, Jinfeng On Thu, Mar 2, 2017 at 8:30 AM, Jinfeng Ni <j...@apache.org> wrote: > I'm building a merge branch, and hopefully push to master branch today > if things go smoothly. > > > On Wed, Mar 1, 2017 at 7:13 PM, Padma Penumarthy <ppenumar...@mapr.c

Re: Time for 1.10 release

> >> On Feb 22, 2017, at 11:16 PM, Jinfeng Ni <j...@apache.org> wrote: >> >> Hi Drillers, >> >> It has been almost 3 months since we release Drill 1.9. We have >> resolved plenty of fixes and improvements (closed around 88 JIRAs >> [1]). I propose

Re: Time for 1.10 release

nd sanity > checks have been done for all of them. For the escape character fix and the > cancel fix, those have been tested in production like environment for weeks. > > Laurent > > On Mar 1, 2017 13:10, "Jinfeng Ni" <j...@apache.org> wrote: > > Hi Laurent, >

Re: Time for 1.10 release

ar 1, 2017 at 1:10 PM, Jinfeng Ni <j...@apache.org> wrote: > Hi Laurent, > > Thanks for the update. For the C++ client commits (DRILL-5301, > DRILL-5221), did you guys run some sanity check to see if there is any > regression? I know Parth used to build/test with the new C++ chan

Re: Time for 1.10 release

Parser will > recognize ANSI_SQL identifiers), it's my understanding that Vitalii would > wait for DRILL-5301 changes to be merged, and refactor his patch on top of > it, and I guess it will be post 1.10 > > Laurent > > > > On Mon, Feb 27, 2017 at 3:07 PM, Jinfe

Re: Time for 1.10 release

tests >> > * DRILL-5284: Roll-up of final fixes for managed sort >> > >> > Thanks, >> > >> > - Paul >> > >> > > On Feb 23, 2017, at 9:57 AM, Sudheesh Katkam <skat...@mapr.com> wrote: >> > > >> > > I would like to i

Re: Excessive Logging Messages

use low-case ones. I tried the above approach, and it seemed to work. On Sun, Feb 26, 2017 at 8:40 PM, Charles Givre <cgi...@gmail.com> wrote: > Hi Jinfeng, > That didn’t seem to do the trick. Any other suggestions? > >> On Feb 26, 2017, at 23:23, Jinfeng Ni <j...@apache.

Re: Excessive Logging Messages

You can modify logback.xml in your drill conf directory (DRILL_HOME/conf/logback.xml). --> Change INFO to either WARN or ERROR On Sun, Feb 26, 2017 at 7:17 PM, Charles Givre wrote: > Hello all, > I was doing some unrelated work and

Time for 1.10 release

Hi Drillers, It has been almost 3 months since we release Drill 1.9. We have resolved plenty of fixes and improvements (closed around 88 JIRAs [1]). I propose that we start the 1.10 release process, and set Wednesday 3/1 as the cutoff day for code checkin. After 3/1, we should start build a

Re: [ANNOUNCE] New Apache Drill Committer - Abhishek Girish

Congratulations, Abhishek! On Fri, Feb 17, 2017 at 10:30 AM, Abhishek Girish wrote: > Thank you all :) > > On Fri, Feb 17, 2017 at 11:57 PM Sudheesh Katkam wrote: > >> Congratulations, Abhishek. >> >> > On Feb 15, 2017, at 1:22 PM, Aditya

  1   2   3   4   >