Re: [ANNOUNCE] New Committer: Arina Ielchiieva
Thank you all for congratulations! I really appreciate that. Kind regards Arina On Sat, Feb 25, 2017 at 3:30 PM, Parth Chandra wrote: > Congratulations Arina. Welcome and thank you for your great work so far. > > > > On Fri, Feb 24, 2017 at 9:06 AM, Sudheesh Katkam > wrote: > > > The Project Management Committee (PMC) for Apache Drill has invited Arina > > Ielchiieva to become a committer, and we are pleased to announce that she > > has accepted. > > > > Arina has a long list of contributions [1] that have touched many aspects > > of the product. Her work includes features such as dynamic UDF support > and > > temporary tables support. > > > > Welcome Arina, and thank you for your contributions. > > > > - Sudheesh, on behalf of the Apache Drill PMC > > > > [1] https://github.com/apache/drill/commits/master?author= > arina-ielchiieva > > >
[GitHub] drill pull request #763: DRILL-5208: Finding path to java executable should ...
Github user arina-ielchiieva commented on a diff in the pull request: https://github.com/apache/drill/pull/763#discussion_r103110888 --- Diff: distribution/src/resources/drill-config.sh --- @@ -367,12 +375,18 @@ if [ -z "$JAVA_HOME" ]; then fi # Now, verify that 'java' binary exists and is suitable for Drill. -if $is_cygwin; then - JAVA_BIN="java.exe" -else - JAVA_BIN="java" +# If we started with `which java` above, use that path (after replacing +# symlinks. If we started with JAVA_HOME, try in bin. Doing so handles --- End diff -- Close the brace. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] drill pull request #763: DRILL-5208: Finding path to java executable should ...
Github user arina-ielchiieva commented on a diff in the pull request: https://github.com/apache/drill/pull/763#discussion_r103110976 --- Diff: distribution/src/resources/drill-config.sh --- @@ -359,6 +366,7 @@ if [ -z "$JAVA_HOME" ]; then [[ $SOURCE != /* ]] && SOURCE="$DIR/$SOURCE" done JAVA_HOME="$( cd -P "$( dirname "$SOURCE" )" && cd .. && pwd )" +JAVA = $SOURCE/$JAVA_BIN --- End diff -- $SOURCE already includes bin/java, so concatenating with $JAVA_BIN will give you: `/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-1.b15.el7_2.x86_64/jre/bin/java/java`. I guess you should concatenate $JAVA_BIN to $SOURCE dirname. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [ANNOUNCE] New Committer: Arina Ielchiieva
Congratulations Arina, well deserved! On Sun, Feb 26, 2017 at 5:23 AM, Arina Yelchiyeva < arina.yelchiy...@gmail.com> wrote: > Thank you all for congratulations! I really appreciate that. > > Kind regards > Arina > > On Sat, Feb 25, 2017 at 3:30 PM, Parth Chandra wrote: > > > Congratulations Arina. Welcome and thank you for your great work so far. > > > > > > > > On Fri, Feb 24, 2017 at 9:06 AM, Sudheesh Katkam > > wrote: > > > > > The Project Management Committee (PMC) for Apache Drill has invited > Arina > > > Ielchiieva to become a committer, and we are pleased to announce that > she > > > has accepted. > > > > > > Arina has a long list of contributions [1] that have touched many > aspects > > > of the product. Her work includes features such as dynamic UDF support > > and > > > temporary tables support. > > > > > > Welcome Arina, and thank you for your contributions. > > > > > > - Sudheesh, on behalf of the Apache Drill PMC > > > > > > [1] https://github.com/apache/drill/commits/master?author= > > arina-ielchiieva > > > > > >
Excessive Logging Messages
Hello all, I was doing some unrelated work and somehow made it so that every time I execute a query in Drill from the command line, I get all these INFO messages. Could someone please explain how to disable these? Thanks, — Charles : jdbc:drill:zk=local> SELECT `Asking - Sold Delta Percent` AS `Asking - Sold Delta Percent` FROM dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 00:07:38' AND `Close Date` <= '2017-02-24 00:07:38' LIMIT 5; Feb 26, 2017 9:47:25 PM org.apache.drill.exec.work.foreman.Foreman run INFO: Query text for query id 274c6cc2-7e8e-c652-812b-2cd6414e453a: SELECT `Asking - Sold Delta Percent` AS `Asking - Sold Delta Percent` FROM dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 00:07:38' AND `Close Date` <= '2017-02-24 00:07:38' LIMIT 5 Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 11 classes for org.apache.drill.exec.store.dfs.FormatPlugin took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.common.scanner.persistence.ScanResult getImplementations INFO: loading 12 classes for org.apache.drill.common.logical.FormatPluginConfig took 0ms Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection getStatuses INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.schedule.BlockMapBuilder getEndpointByteMap INFO: Failure finding Drillbit running on host localhost. Skipping affinity to that host. Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.TimedRunnable run INFO: Get block maps: Executed 1 out of 1 using 1 threads. Time: 0ms total, 0.729272ms avg, 0ms max. Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.TimedRunnable run INFO: Get block maps: Executed 1 out of 1 using 1 threads. Earliest start: 0.824000 μs, Latest start: 0.824000 μs, Average start: 0.824000 μs . Feb 26, 2017 9:47:25 PM org.apache.drill.exec.planner.logical.partition.PruneScanRule doOnMatch INFO: Beginning partition pruning, pruning class: or
drill's calcite branch
hi Drills: where can I find the calcite branch source code that drill are now self maintaining ?
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 somehow made it so that every time I > execute a query in Drill from the command line, I get all these INFO > messages. Could someone please explain how to disable these? > Thanks, > — Charles > > > > : jdbc:drill:zk=local> SELECT `Asking - Sold Delta Percent` AS `Asking - Sold > Delta Percent` FROM dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 > 00:07:38' AND `Close Date` <= '2017-02-24 00:07:38' LIMIT 5; > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.work.foreman.Foreman run > INFO: Query text for query id 274c6cc2-7e8e-c652-812b-2cd6414e453a: SELECT > `Asking - Sold Delta Percent` AS `Asking - Sold Delta Percent` FROM > dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 00:07:38' AND > `Close Date` <= '2017-02-24 00:07:38' LIMIT 5 > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 11 classes for org.apache.drill.exec.store.dfs.FormatPlugin > took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM > org.apache.drill.common.scanner.persistence.ScanResult getImplementations > INFO: loading 12 classes for > org.apache.drill.common.logical.FormatPluginConfig took 0ms > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection > getStatuses > INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.schedule.BlockMapBuilder > getEndpointByteMap > INFO: Failure finding Drillbit running on host localhost. Skipping affinity > to that host. > Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.TimedRunnable run > INFO: Get block maps: Executed 1 out of 1 using 1
Re: [ANNOUNCE] New Committer: Arina Ielchiieva
Congratulations Arina! On Sun, Feb 26, 2017 at 11:57 AM, Aditya wrote: > Congratulations Arina, well deserved! > > On Sun, Feb 26, 2017 at 5:23 AM, Arina Yelchiyeva < > arina.yelchiy...@gmail.com> wrote: > >> Thank you all for congratulations! I really appreciate that. >> >> Kind regards >> Arina >> >> On Sat, Feb 25, 2017 at 3:30 PM, Parth Chandra wrote: >> >> > Congratulations Arina. Welcome and thank you for your great work so far. >> > >> > >> > >> > On Fri, Feb 24, 2017 at 9:06 AM, Sudheesh Katkam >> > wrote: >> > >> > > The Project Management Committee (PMC) for Apache Drill has invited >> Arina >> > > Ielchiieva to become a committer, and we are pleased to announce that >> she >> > > has accepted. >> > > >> > > Arina has a long list of contributions [1] that have touched many >> aspects >> > > of the product. Her work includes features such as dynamic UDF support >> > and >> > > temporary tables support. >> > > >> > > Welcome Arina, and thank you for your contributions. >> > > >> > > - Sudheesh, on behalf of the Apache Drill PMC >> > > >> > > [1] https://github.com/apache/drill/commits/master?author= >> > arina-ielchiieva >> > > >> > >>
Re: Excessive Logging Messages
Hi Jinfeng, That didn’t seem to do the trick. Any other suggestions? > On Feb 26, 2017, at 23:23, Jinfeng Ni wrote: > > 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 somehow made it so that every time I >> execute a query in Drill from the command line, I get all these INFO >> messages. Could someone please explain how to disable these? >> Thanks, >> — Charles >> >> >> >> : jdbc:drill:zk=local> SELECT `Asking - Sold Delta Percent` AS `Asking - >> Sold Delta Percent` FROM dfs.test.`comps.xlsx` WHERE `Close Date` >= >> '2014-02-24 00:07:38' AND `Close Date` <= '2017-02-24 00:07:38' LIMIT >> 5; >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.work.foreman.Foreman run >> INFO: Query text for query id 274c6cc2-7e8e-c652-812b-2cd6414e453a: SELECT >> `Asking - Sold Delta Percent` AS `Asking - Sold Delta Percent` FROM >> dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 00:07:38' AND >> `Close Date` <= '2017-02-24 00:07:38' LIMIT 5 >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 11 classes for org.apache.drill.exec.store.dfs.FormatPlugin >> took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM >> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >> INFO: loading 12 classes for >> org.apache.drill.common.logical.FormatPluginConfig took 0ms >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >> getStatuses >> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.schedule.BlockMapBuilde
[jira] [Created] (DRILL-5299) Query queues can be split by different users or different businesses
Hongze Zhang created DRILL-5299: --- Summary: Query queues can be split by different users or different businesses Key: DRILL-5299 URL: https://issues.apache.org/jira/browse/DRILL-5299 Project: Apache Drill Issue Type: Improvement Components: Query Planning & Optimization Affects Versions: Future Environment: RH Linux / OpenJDK 8 Reporter: Hongze Zhang So far we can have 2 query queues that are split based on the cost model. For serving multiple users and multiple businesses, Drill cluster maintainers always like to control the query concurrency that are allocated for a concrete user or a concrete businesses. Which means, each user or business can have its own "query pool" defined by a specific "pool size". -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: [ANNOUNCE] New Committer: Arina Ielchiieva
Congratulations Arina!!! From: Arina Yelchiyeva To: dev@drill.apache.org Sent: Sunday, February 26, 2017 5:23 AM Subject: Re: [ANNOUNCE] New Committer: Arina Ielchiieva Thank you all for congratulations! I really appreciate that. Kind regards Arina On Sat, Feb 25, 2017 at 3:30 PM, Parth Chandra wrote: > Congratulations Arina. Welcome and thank you for your great work so far. > > > > On Fri, Feb 24, 2017 at 9:06 AM, Sudheesh Katkam > wrote: > > > The Project Management Committee (PMC) for Apache Drill has invited Arina > > Ielchiieva to become a committer, and we are pleased to announce that she > > has accepted. > > > > Arina has a long list of contributions [1] that have touched many aspects > > of the product. Her work includes features such as dynamic UDF support > and > > temporary tables support. > > > > Welcome Arina, and thank you for your contributions. > > > > - Sudheesh, on behalf of the Apache Drill PMC > > > > [1] https://github.com/apache/drill/commits/master?author= > arina-ielchiieva > > >
[jira] [Resolved] (DRILL-5298) CTAS with 0 records from a SELECT query should create the table with metadata
[ https://issues.apache.org/jira/browse/DRILL-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khurram Faraaz resolved DRILL-5298. --- Resolution: Duplicate > CTAS with 0 records from a SELECT query should create the table with metadata > - > > Key: DRILL-5298 > URL: https://issues.apache.org/jira/browse/DRILL-5298 > Project: Apache Drill > Issue Type: Bug > Components: Metadata, Query Planning & Optimization >Affects Versions: 1.9.0 > Environment: MapR 5.2 >Reporter: Senthilkumar > Fix For: 1.9.0 > > > Hello team, > I create a table in Drill using CTAS as > CREATE TABLE CTAS_TEST AS SELECT * FROM `hive.default`.`test` WHERE 1 = 0 > It runs successfully. > But the table is not getting created as there are 0 records getting returned > from the SELECT query. > CTAS should still go ahead and create the table with the column metadata. > When BI tools fire up multi-pass queries, with CTAS in the first query, the > subsequent queries fail because of a missing table. > In databases like SQL Server, Postgres, CTAS will create the table, even if > the SELECT doesnt return any rows. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: Excessive Logging Messages
I assume what you want is to disable those INFO level log messages in your drillbit.log (or sqlline.log, if it's embedded drill). If that's what you want, when you start sqlline to connect to drillbit, it will show the following information, 23:15:23,654 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/private/etc/drill/conf/logback.xml] 23:15:25,636 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [org.apache.drill] to false 23:15:25,637 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - org.apache.drill level set to WARN The first one tells you which logback.xml is used. Please make sure your modify the one list there. The second/third entries confirm log level for classes in package org.apache.drill. btw: in my previous email, I used cap "INFO", "WARN". Please 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 wrote: > Hi Jinfeng, > That didn’t seem to do the trick. Any other suggestions? > >> On Feb 26, 2017, at 23:23, Jinfeng Ni wrote: >> >> 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 somehow made it so that every time I >>> execute a query in Drill from the command line, I get all these INFO >>> messages. Could someone please explain how to disable these? >>> Thanks, >>> — Charles >>> >>> >>> >>> : jdbc:drill:zk=local> SELECT `Asking - Sold Delta Percent` AS `Asking - >>> Sold Delta Percent` FROM dfs.test.`comps.xlsx` WHERE `Close Date` >= >>> '2014-02-24 00:07:38' AND `Close Date` <= '2017-02-24 00:07:38' LIMIT >>> 5; >>> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.work.foreman.Foreman run >>> INFO: Query text for query id 274c6cc2-7e8e-c652-812b-2cd6414e453a: SELECT >>> `Asking - Sold Delta Percent` AS `Asking - Sold Delta Percent` FROM >>> dfs.test.`comps.xlsx` WHERE `Close Date` >= '2014-02-24 00:07:38' AND >>> `Close Date` <= '2017-02-24 00:07:38' LIMIT 5 >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 11 classes for org.apache.drill.exec.store.dfs.FormatPlugin >>> took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM >>> org.apache.drill.common.scanner.persistence.ScanResult getImplementations >>> INFO: loading 12 classes for >>> org.apache.drill.common.logical.FormatPluginConfig took 0ms >>> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >>> getStatuses >>> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >>> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >>> getStatuses >>> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >>> Feb 26, 2017 9:47:25 PM org.apache.drill.exec.store.dfs.FileSelection >>> getStatuses >>> INFO: FileSelection.getStatuses() took 0 ms, numFiles: 1 >>> Feb 26, 2017 9:47:25 PM org.apa