[jira] [Closed] (DRILL-7357) Expose Drill Metastore data through INFORMATION_SCHEMA
[
https://issues.apache.org/jira/browse/DRILL-7357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7357.
--
Successfully tested INFORMATION_SCHEMA tables.
New columns in the `*TABLES*` table filling by the 'REFRESH METADATA' command.
In `*COLUMNS*` table all fields gets data from 'REFRESH METADATA' command.
Instead of `COLUMN_DEFAULT`, `COLUMN_FORMAT` columns. Drill will use these
columns later in the future Metastore implementations.
To fill the columns `NDV` and `EST_NUM_NON_NULLS` option
`planner.statistics.use` should be 'true'.
Parquet table with subdirectories was used to fill `*PARTITIONS*` table.
> Expose Drill Metastore data through INFORMATION_SCHEMA
> --
>
> Key: DRILL-7357
> URL: https://issues.apache.org/jira/browse/DRILL-7357
> Project: Apache Drill
> Issue Type: Sub-task
>Reporter: Arina Ielchiieva
>Assignee: Arina Ielchiieva
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.17.0
>
>
> Document:
> https://docs.google.com/document/d/10CkLdrlUJUNRrHKLeo8jTUJB8xAP1D0byTOvn8wNoF0/edit#heading=h.gzj2dj5a4yds
> Sections:
> 5.19 INFORMATION_SCHEMA updates
> 4.3.2 Using the statistics
> information_schema tables will contain data from Metastore only if
> {{metastore.enabled}} is set to true.
> This Jira will add additional columns to TABLES and COLUMNS tables and new
> PARTITIONS table.
> Note: new columns or table are applicable only for Metastore data, for data
> from different sources these columns will be set to null.
> Additional columns
> *TABLES:*
> TABLE_SOURCE - table data type: PARQUET, CSV, JSON
> LOCATION - table location: /tmp/nation
> NUM_ROWS - number of rows in a table if know, null if not known
> LAST_MODIFIED_TIME - table's last modification time
> *COLUMNS:*
> COLUMN_SIZE (already existed but was not included, applicable for all
> sources) - estimated column size, for example for boolean 1, for integer 11
> (sign + 10 digits), etc.
> COLUMN_DEFAULT (already existed but never was filled in) - column default
> value
> COLUMN_FORMAT - usually applicable for date time columns: -MM-dd
> NUM_NULLS - number of nulls in column values
> MIN_VAL - column min value in String representation: aaa
> MAX_VAL - column max value in String representation: zzz
> NDV - number of distinct values in column, expressed in Double
> EST_NUM_NON_NULLS - estimated number of non null values, expressed in Double
> IS_NESTED - if column is nested. Nested columns are extracted from columns
> with struct type.
> *PARTITIONS* table columns:
> TABLE_CATALOG - table catalog (currently we have only one catalog): DRILL
> TABLE_SCHEMA - table schema: dfs.tmp
> TABLE_NAME - table name: nation
> METADATA_KEY - top level segment key, he same for all nested segments and
> partitions: part_int=3
> METADATA_TYPE - SEGMENT or PARTITION
> METADATA_IDENTIFIER - current metadata identifier: part_int=3/part_varchar=g
> PARTITION_COLUMN - partition column name: part_varchar
> PARTITION_VALUE - partition column value: g
> LOCATION - segment location, null for partitions: /tmp/nation/part_int=3
> LAST_MODIFIED_TIME - last modification time
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DRILL-7527) DROP METADATA doesn't work with table name starting with '/' inside workspace
[ https://issues.apache.org/jira/browse/DRILL-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-7527. -- Successfully verified '/' on table names with and without workspace definition. > DROP METADATA doesn't work with table name starting with '/' inside workspace > - > > Key: DRILL-7527 > URL: https://issues.apache.org/jira/browse/DRILL-7527 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.17.0 >Reporter: Denys Ordynskiy >Assignee: Vova Vysotskyi >Priority: Major > Labels: ready-to-commit > Fix For: 1.18.0 > > > *Description:* > - create parquet table with CTAS: CREATE TABLE dfs.tmp.`folder/file` AS > SELECT * FROM cp.`employee.json`; > - refresh metadata for table: ANALYZE TABLE dfs.tmp.`folder/file` REFRESH > METADATA; > - drop metadata: ANALYZE TABLE dfs.tmp.`/folder/file` DROP METADATA [IF > EXISTS]; > *Expexted result:* > Metadata for table [folder/file] dropped. > *Actual result:* > Error: VALIDATION ERROR: Metadata for table [/folder/file] not found. > Shoud work as DROP TABLE: > DROP TABLE dfs.tmp.`/folder/file`; > Table [folder/file] dropped -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DRILL-7184) Set the IDs for the unique HTML tags in the Drill Web UI
[ https://issues.apache.org/jira/browse/DRILL-7184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-7184. -- Resolution: Not A Problem > Set the IDs for the unique HTML tags in the Drill Web UI > > > Key: DRILL-7184 > URL: https://issues.apache.org/jira/browse/DRILL-7184 > Project: Apache Drill > Issue Type: Task >Affects Versions: 1.16.0 >Reporter: Denys Ordynskiy >Priority: Major > > Selenium web pages automation requires identifiers on HTML tags. > We need to find all HTML tags without ID's that are useful for Drill Web UI > automation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7527) DROP METADATA doesn't work with table name starting with '/' inside workspace
Denys Ordynskiy created DRILL-7527: -- Summary: DROP METADATA doesn't work with table name starting with '/' inside workspace Key: DRILL-7527 URL: https://issues.apache.org/jira/browse/DRILL-7527 Project: Apache Drill Issue Type: Bug Affects Versions: 1.17.0 Reporter: Denys Ordynskiy *Description:* - create parquet table with CTAS: CREATE TABLE dfs.tmp.`folder/file` AS SELECT * FROM cp.`employee.json`; - refresh metadata for table: ANALYZE TABLE dfs.tmp.`folder/file` REFRESH METADATA; - drop metadata: ANALYZE TABLE dfs.tmp.`/folder/file` DROP METADATA [IF EXISTS]; *Expexted result:* Metadata for table [folder/file] dropped. *Actual result:* Error: VALIDATION ERROR: Metadata for table [/folder/file] not found. Shoud work as DROP TABLE: DROP TABLE dfs.tmp.`/folder/file`; Table [folder/file] dropped -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7508) Filesystem Implicit Columns Not Returned
[
https://issues.apache.org/jira/browse/DRILL-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17006831#comment-17006831
]
Denys Ordynskiy commented on DRILL-7508:
I successfully tested Implicit Columns in DrillExplorer using this query:
{code:java}
SELECT Year, Month, Day, Hour, Message, Filename FROM
dfs.tmp.`regex/log/simple.log`
{code}
Details in the attachment [^DrillExplorer.png]
Source file is [^simple.log]
My ODBC driver version:
Simba Drill ODBC Driver 1.3.22
> Filesystem Implicit Columns Not Returned
>
>
> Key: DRILL-7508
> URL: https://issues.apache.org/jira/browse/DRILL-7508
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - ODBC
>Affects Versions: 1.17.0
> Environment: Windows Server 2016R2, Drill 1.17, ODBC x86 / x64
> 1.3.22.1055
>Reporter: Daniel Hitchcock
>Priority: Minor
> Attachments: DrillExplorer.png, Drill_Explorer.png, GUI.png,
> Tableau.png, Tableau_Alias.png, simple.log
>
>
> When using the latest ODBC driver with Drill 1.17, the newly added Implicit
> Columns
> ([http://drill.apache.org/docs/querying-a-file-system-introduction/#implicit-columns])
> are not returned when performing a query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (DRILL-7508) Filesystem Implicit Columns Not Returned
[ https://issues.apache.org/jira/browse/DRILL-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-7508: --- Attachment: simple.log > Filesystem Implicit Columns Not Returned > > > Key: DRILL-7508 > URL: https://issues.apache.org/jira/browse/DRILL-7508 > Project: Apache Drill > Issue Type: Bug > Components: Client - ODBC >Affects Versions: 1.17.0 > Environment: Windows Server 2016R2, Drill 1.17, ODBC x86 / x64 > 1.3.22.1055 >Reporter: Daniel Hitchcock >Priority: Minor > Attachments: DrillExplorer.png, Drill_Explorer.png, GUI.png, > Tableau.png, Tableau_Alias.png, simple.log > > > When using the latest ODBC driver with Drill 1.17, the newly added Implicit > Columns > ([http://drill.apache.org/docs/querying-a-file-system-introduction/#implicit-columns]) > are not returned when performing a query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7508) Filesystem Implicit Columns Not Returned
[ https://issues.apache.org/jira/browse/DRILL-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-7508: --- Attachment: DrillExplorer.png > Filesystem Implicit Columns Not Returned > > > Key: DRILL-7508 > URL: https://issues.apache.org/jira/browse/DRILL-7508 > Project: Apache Drill > Issue Type: Bug > Components: Client - ODBC >Affects Versions: 1.17.0 > Environment: Windows Server 2016R2, Drill 1.17, ODBC x86 / x64 > 1.3.22.1055 >Reporter: Daniel Hitchcock >Priority: Minor > Attachments: DrillExplorer.png, GUI.png, Tableau.png, > Tableau_Alias.png > > > When using the latest ODBC driver with Drill 1.17, the newly added Implicit > Columns > ([http://drill.apache.org/docs/querying-a-file-system-introduction/#implicit-columns]) > are not returned when performing a query. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DRILL-7484) Malware found with some antiviruses in the Drill test resources folder
[ https://issues.apache.org/jira/browse/DRILL-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-7484. -- No viruses found in the new .pcap file http://r.virscan.org/language/en/report/097d4edd80770965ea3c1e69333a1065 Successfully downloaded Drill sources zip archive from GitHub and cloned using cmd. > Malware found with some antiviruses in the Drill test resources folder > -- > > Key: DRILL-7484 > URL: https://issues.apache.org/jira/browse/DRILL-7484 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.17.0 >Reporter: Denys Ordynskiy >Assignee: Charles Givre >Priority: Blocker > Labels: ready-to-commit > Fix For: 1.17.0 > > Attachments: photo_2019-12-11_17-07-45.jpg > > > Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill > sources. > File with virus alert: > https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap > OS Windows 10. > Free Avast antivirus v. 19.8.2393 (build 19.8.4793.544) > Steps to reproduce: > Download archive with Drill sources from GitHub > - open Chrome browser; > - go to https://github.com/apache/drill link; > - open the "Clone or download" menu; > - click the "Download ZIP" button and save archive on a disk. > *Expected result* - archive successfully downloaded. > *Actual result* - Chrome browser canceled the download and deleted Drill > sources archive fron the disk. Avast showed an alert window with virus > description. Screenshot is in the attachments. > Clone Drill sources from GitHub using git console version > - open CMD; > - type "git clone https://github.com/apache/drill.git;; > - scan clonned Drill sources folder using Avast antivirus. > *Expected result* - Viruses were absent. > *Actual result* - Avast showed an alert window with virus description. > Here is the link with report from other antiviruses for this > "attack-trace.pcap" file: > https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DRILL-6964) Implement CREATE / DROP TABLE SCHEMA commands
[ https://issues.apache.org/jira/browse/DRILL-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6964. -- Successfully tested CRUD for table schema. Performance tests were passed. > Implement CREATE / DROP TABLE SCHEMA commands > - > > Key: DRILL-6964 > URL: https://issues.apache.org/jira/browse/DRILL-6964 > Project: Apache Drill > Issue Type: Sub-task >Reporter: Arina Ielchiieva >Assignee: Arina Ielchiieva >Priority: Major > Labels: doc-complete, ready-to-commit > Fix For: 1.16.0 > > > Design doc - > https://docs.google.com/document/d/1mp4egSbNs8jFYRbPVbm_l0Y5GjH3HnoqCmOpMTR_g4w/edit -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (DRILL-7409) Remove bigIntDictionary.parquet from project sources
[
https://issues.apache.org/jira/browse/DRILL-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7409.
--
Successfully moved bigIntDictionary.parquet to the drill-test-framework.
> Remove bigIntDictionary.parquet from project sources
>
>
> Key: DRILL-7409
> URL: https://issues.apache.org/jira/browse/DRILL-7409
> Project: Apache Drill
> Issue Type: Task
> Components: Tools, Build Test
>Affects Versions: 1.16.0
>Reporter: Vova Vysotskyi
>Assignee: Denys Ordynskiy
>Priority: Minor
> Labels: ready-to-commit
> Fix For: 1.17.0
>
>
> {{bigIntDictionary.parquet}} file has size of 1.8M, but it is used in single
> unit test {{TestColumnReaderFactory.testBigIntWithDictionary}}. We should
> either move this test to a test-framework or recreate a smaller file that
> will still allow us to verify this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (DRILL-6540) Upgrade to HADOOP-3.0 libraries
[ https://issues.apache.org/jira/browse/DRILL-6540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6540. -- Successfully tested on Hadoop v.3.2.1 > Upgrade to HADOOP-3.0 libraries > > > Key: DRILL-6540 > URL: https://issues.apache.org/jira/browse/DRILL-6540 > Project: Apache Drill > Issue Type: Improvement > Components: Tools, Build Test >Affects Versions: 1.14.0 >Reporter: Vitalii Diravka >Assignee: Anton Gozhiy >Priority: Major > Labels: ready-to-commit > Fix For: 1.17.0 > > > Currently Drill uses 2.7.4 version of hadoop libraries (hadoop-common, > hadoop-hdfs, hadoop-annotations, hadoop-aws, hadoop-yarn-api, hadoop-client, > hadoop-yarn-client). > A year ago the [Hadoop 3.0|https://hadoop.apache.org/docs/r3.0.0/index.html] > was released and recently it was updated to [Hadoop > 3.2.0|https://hadoop.apache.org/docs/r3.2.0/]. > To use Drill under Hadoop3.0 distribution we need this upgrade. Also the > newer version includes new features, which can be useful for Drill. > This upgrade is also needed to leverage the newest version of Zookeeper > libraries and Hive 3.1 version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7484) Malware found with some antiviruses in the Drill test resources folder
[ https://issues.apache.org/jira/browse/DRILL-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-7484: --- Description: Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill sources. File with virus alert: https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap OS Windows 10. Free Avast antivirus v. 19.8.2393 (build 19.8.4793.544) Steps to reproduce: Download archive with Drill sources from GitHub - open Chrome browser; - go to https://github.com/apache/drill link; - open the "Clone or download" menu; - click the "Download ZIP" button and save archive on a disk. *Expected result* - archive successfully downloaded. *Actual result* - Chrome browser canceled the download and deleted Drill sources archive fron the disk. Avast showed an alert window with virus description. Screenshot is in the attachments. Clone Drill sources from GitHub using git console version - open CMD; - type "git clone https://github.com/apache/drill.git;; - scan clonned Drill sources folder using Avast antivirus. *Expected result* - Viruses were absent. *Actual result* - Avast showed an alert window with virus description. Here is the link with report from other antiviruses for this "attack-trace.pcap" file: https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d was: Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill sources. File with virus alert: https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap OS Windows 10. Free Avast antivirus v. Steps to reproduce: Download archive with Drill sources from GitHub - open Chrome browser; - go to https://github.com/apache/drill link; - open the "Clone or download" menu; - click the "Download ZIP" button and save archive on a disk. *Expected result* - archive successfully downloaded. *Actual result* - Chrome browser canceled the download and deleted Drill sources archive fron the disk. Avast showed an alert window with virus description. Screenshot is in the attachments. Clone Drill sources from GitHub using git console version - open CMD; - type "git clone https://github.com/apache/drill.git;; - scan clonned Drill sources folder using Avast antivirus. *Expected result* - Viruses were absent. *Actual result* - Avast showed an alert window with virus description. Here is the link with report from other antiviruses for this "attack-trace.pcap" file: https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d > Malware found with some antiviruses in the Drill test resources folder > -- > > Key: DRILL-7484 > URL: https://issues.apache.org/jira/browse/DRILL-7484 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.17.0 >Reporter: Denys Ordynskiy >Assignee: Charles Givre >Priority: Major > Attachments: photo_2019-12-11_17-07-45.jpg > > > Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill > sources. > File with virus alert: > https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap > OS Windows 10. > Free Avast antivirus v. 19.8.2393 (build 19.8.4793.544) > Steps to reproduce: > Download archive with Drill sources from GitHub > - open Chrome browser; > - go to https://github.com/apache/drill link; > - open the "Clone or download" menu; > - click the "Download ZIP" button and save archive on a disk. > *Expected result* - archive successfully downloaded. > *Actual result* - Chrome browser canceled the download and deleted Drill > sources archive fron the disk. Avast showed an alert window with virus > description. Screenshot is in the attachments. > Clone Drill sources from GitHub using git console version > - open CMD; > - type "git clone https://github.com/apache/drill.git;; > - scan clonned Drill sources folder using Avast antivirus. > *Expected result* - Viruses were absent. > *Actual result* - Avast showed an alert window with virus description. > Here is the link with report from other antiviruses for this > "attack-trace.pcap" file: > https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (DRILL-7484) Malware found with some antiviruses in the Drill test resources folder
[ https://issues.apache.org/jira/browse/DRILL-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy reassigned DRILL-7484: -- Assignee: Charles Givre > Malware found with some antiviruses in the Drill test resources folder > -- > > Key: DRILL-7484 > URL: https://issues.apache.org/jira/browse/DRILL-7484 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.17.0 >Reporter: Denys Ordynskiy >Assignee: Charles Givre >Priority: Major > Attachments: photo_2019-12-11_17-07-45.jpg > > > Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill > sources. > File with virus alert: > https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap > OS Windows 10. > Free Avast antivirus v. > Steps to reproduce: > Download archive with Drill sources from GitHub > - open Chrome browser; > - go to https://github.com/apache/drill link; > - open the "Clone or download" menu; > - click the "Download ZIP" button and save archive on a disk. > *Expected result* - archive successfully downloaded. > *Actual result* - Chrome browser canceled the download and deleted Drill > sources archive fron the disk. Avast showed an alert window with virus > description. Screenshot is in the attachments. > Clone Drill sources from GitHub using git console version > - open CMD; > - type "git clone https://github.com/apache/drill.git;; > - scan clonned Drill sources folder using Avast antivirus. > *Expected result* - Viruses were absent. > *Actual result* - Avast showed an alert window with virus description. > Here is the link with report from other antiviruses for this > "attack-trace.pcap" file: > https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7484) Malware found with some antiviruses in the Drill test resources folder
[ https://issues.apache.org/jira/browse/DRILL-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-7484: --- Description: Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill sources. File with virus alert: https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap OS Windows 10. Free Avast antivirus v. Steps to reproduce: Download archive with Drill sources from GitHub - open Chrome browser; - go to https://github.com/apache/drill link; - open the "Clone or download" menu; - click the "Download ZIP" button and save archive on a disk. *Expected result* - archive successfully downloaded. *Actual result* - Chrome browser canceled the download and deleted Drill sources archive fron the disk. Avast showed an alert window with virus description. Screenshot is in the attachments. Clone Drill sources from GitHub using git console version - open CMD; - type "git clone https://github.com/apache/drill.git;; - scan clonned Drill sources folder using Avast antivirus. *Expected result* - Viruses were absent. *Actual result* - Avast showed an alert window with virus description. Here is the link with report from other antiviruses for this "attack-trace.pcap" file: https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d was: Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill sources. File with virus alert: https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap OS Windows 10. Free Avast antivirus v. Steps to reproduce: Download archive with Drill sources from GitHub - open Chrome browser; - go to https://github.com/apache/drill link; - open the "Clone or download" menu; - click the "Download ZIP" button and save archive on a disk. *Expected result* - archive successfully downloaded. *Actual result* - Chrome browser canceled the download and deleted Drill sources archive fron the disk. Avast showed an alert window with virus description. Screenshot is in the attachments. Clone Drill sources from GitHub using git console version - open CMD; - type "git clone https://github.com/apache/drill.git;; - scan clonned Drill sources folder using Avast antivirus. *Expected result* - Viruses were absent. *Actual result* - Avast showed an alert window with virus description. > Malware found with some antiviruses in the Drill test resources folder > -- > > Key: DRILL-7484 > URL: https://issues.apache.org/jira/browse/DRILL-7484 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.17.0 >Reporter: Denys Ordynskiy >Priority: Major > Attachments: photo_2019-12-11_17-07-45.jpg > > > Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill > sources. > File with virus alert: > https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap > OS Windows 10. > Free Avast antivirus v. > Steps to reproduce: > Download archive with Drill sources from GitHub > - open Chrome browser; > - go to https://github.com/apache/drill link; > - open the "Clone or download" menu; > - click the "Download ZIP" button and save archive on a disk. > *Expected result* - archive successfully downloaded. > *Actual result* - Chrome browser canceled the download and deleted Drill > sources archive fron the disk. Avast showed an alert window with virus > description. Screenshot is in the attachments. > Clone Drill sources from GitHub using git console version > - open CMD; > - type "git clone https://github.com/apache/drill.git;; > - scan clonned Drill sources folder using Avast antivirus. > *Expected result* - Viruses were absent. > *Actual result* - Avast showed an alert window with virus description. > Here is the link with report from other antiviruses for this > "attack-trace.pcap" file: > https://r.virscan.org/language/en/report/4df38505462d3afedbbbff3d9217063d -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (DRILL-7484) Malware found with some antiviruses in the Drill test resources folder
Denys Ordynskiy created DRILL-7484: -- Summary: Malware found with some antiviruses in the Drill test resources folder Key: DRILL-7484 URL: https://issues.apache.org/jira/browse/DRILL-7484 Project: Apache Drill Issue Type: Bug Affects Versions: 1.17.0 Reporter: Denys Ordynskiy Attachments: photo_2019-12-11_17-07-45.jpg Avast antivirus found Threat "MPPT97:ShellCode-O [Expl]" in the Apache Drill sources. File with virus alert: https://github.com/apache/drill/commits/master/exec/java-exec/src/test/resources/store/pcap/attack-trace.pcap OS Windows 10. Free Avast antivirus v. Steps to reproduce: Download archive with Drill sources from GitHub - open Chrome browser; - go to https://github.com/apache/drill link; - open the "Clone or download" menu; - click the "Download ZIP" button and save archive on a disk. *Expected result* - archive successfully downloaded. *Actual result* - Chrome browser canceled the download and deleted Drill sources archive fron the disk. Avast showed an alert window with virus description. Screenshot is in the attachments. Clone Drill sources from GitHub using git console version - open CMD; - type "git clone https://github.com/apache/drill.git;; - scan clonned Drill sources folder using Avast antivirus. *Expected result* - Viruses were absent. *Actual result* - Avast showed an alert window with virus description. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (DRILL-7409) Remove bigIntDictionary.parquet from project sources
[
https://issues.apache.org/jira/browse/DRILL-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7409:
---
Reviewer: Vova Vysotskyi
> Remove bigIntDictionary.parquet from project sources
>
>
> Key: DRILL-7409
> URL: https://issues.apache.org/jira/browse/DRILL-7409
> Project: Apache Drill
> Issue Type: Task
> Components: Tools, Build Test
>Affects Versions: 1.16.0
>Reporter: Vova Vysotskyi
>Assignee: Denys Ordynskiy
>Priority: Minor
> Fix For: 1.17.0
>
>
> {{bigIntDictionary.parquet}} file has size of 1.8M, but it is used in single
> unit test {{TestColumnReaderFactory.testBigIntWithDictionary}}. We should
> either move this test to a test-framework or recreate a smaller file that
> will still allow us to verify this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (DRILL-7409) Remove bigIntDictionary.parquet from project sources
[
https://issues.apache.org/jira/browse/DRILL-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16967508#comment-16967508
]
Denys Ordynskiy commented on DRILL-7409:
Created PR [#1891|https://github.com/apache/drill/pull/1891]
> Remove bigIntDictionary.parquet from project sources
>
>
> Key: DRILL-7409
> URL: https://issues.apache.org/jira/browse/DRILL-7409
> Project: Apache Drill
> Issue Type: Task
> Components: Tools, Build Test
>Affects Versions: 1.16.0
>Reporter: Vova Vysotskyi
>Assignee: Denys Ordynskiy
>Priority: Minor
> Fix For: 1.17.0
>
>
> {{bigIntDictionary.parquet}} file has size of 1.8M, but it is used in single
> unit test {{TestColumnReaderFactory.testBigIntWithDictionary}}. We should
> either move this test to a test-framework or recreate a smaller file that
> will still allow us to verify this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (DRILL-7409) Remove bigIntDictionary.parquet from project sources
[
https://issues.apache.org/jira/browse/DRILL-7409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy reassigned DRILL-7409:
--
Assignee: Denys Ordynskiy
> Remove bigIntDictionary.parquet from project sources
>
>
> Key: DRILL-7409
> URL: https://issues.apache.org/jira/browse/DRILL-7409
> Project: Apache Drill
> Issue Type: Task
> Components: Tools, Build Test
>Reporter: Vova Vysotskyi
>Assignee: Denys Ordynskiy
>Priority: Minor
>
> {{bigIntDictionary.parquet}} file has size of 1.8M, but it is used in single
> unit test {{TestColumnReaderFactory.testBigIntWithDictionary}}. We should
> either move this test to a test-framework or recreate a smaller file that
> will still allow us to verify this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (DRILL-7342) Drill replacing spaces with underlines in the column names of text files with headers
[
https://issues.apache.org/jira/browse/DRILL-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903943#comment-16903943
]
Denys Ordynskiy edited comment on DRILL-7342 at 8/9/19 3:51 PM:
Drill allows spaces in the column names for *parquet tables*:
Update Drill ctas format option to generate parquet table:
{noformat}
set `store.format` = 'parquet';
{noformat}
Create parquet table with column names having spaces:
{noformat}
create table dfs.tmp.`parquet table with spaces` (`Full Name`) as select 'James
Bond' from (values(1));
{noformat}
Try to query this table without column name:
{noformat}
select * from dfs.tmp.`parquet table with spaces`;
{noformat}
|{color:green}*Full Name*{color}|
|James Bond|
Try to query this table with column name:
{noformat}
select `Full Name` from dfs.tmp.`parquet table with spaces`;
{noformat}
|Full Name|
|{color:green}*James Bond*{color}|
was (Author: denysord88):
Drill allows spaces in the column names for parquet tables:
Update Drill ctas format option to generate parquet table:
{noformat}
set `store.format` = 'parquet';
{noformat}
Create parquet table with column names having spaces:
{noformat}
create table dfs.tmp.`parquet table with spaces` (`Full Name`) as select 'James
Bond' from (values(1));
{noformat}
Try to query this table without column name:
{noformat}
select * from dfs.tmp.`parquet table with spaces`;
{noformat}
|{color:green}*Full Name*{color}|
|James Bond|
Try to query this table with column name:
{noformat}
select `Full Name` from dfs.tmp.`parquet table with spaces`;
{noformat}
|Full Name|
|{color:green}*James Bond*{color}|
> Drill replacing spaces with underlines in the column names of text files with
> headers
> -
>
> Key: DRILL-7342
> URL: https://issues.apache.org/jira/browse/DRILL-7342
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Drill doesn't allow to query csvh columns with spaces.
> *Description:*
> Update Drill ctas format option to generate text file with header:
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create table with column names having spaces:
> {noformat}
> create table dfs.tmp.`csv table with spaces` (`Full Name`) as select 'James
> Bond' from (values(1));
> {noformat}
> Drill wrote column name with space:
> {noformat}
> hadoop fs -cat '/tmp/csv table with spaces/0_0_0.csvh'
> {noformat}
> |Full Name|
> |James Bond|
> Try to query this table without column name:
> {noformat}
> select * from dfs.tmp.`csv table with spaces`;
> {noformat}
> |{color:#ff}*Full_Name*{color}|
> |James Bond|
> {color:#ff}*Drill replaced space with underline.*{color}
> Try to select `Full Name` column with space:
> {noformat}
> select `Full Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> Drill
> |Full Name|
> | |
> When I changed space to underline, query returned the data:
> {noformat}
> select `Full_Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> |Full_Name|
> |James Bond|
> Drill can create csvh text files with spaces in the column names. But it's
> impossible to request data using the original column name.
> *Expected result*
> Space should be available character in the column names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DRILL-7342) Drill replacing spaces with underlines in the column names of text files with headers
[
https://issues.apache.org/jira/browse/DRILL-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903995#comment-16903995
]
Denys Ordynskiy commented on DRILL-7342:
*PostgreSQL* allows to create column name with spaces and select the data by
this names.
test.csv
|text 1.1|text 2.1|
|text 1.2|text 2.2|
|text 1.3|text 2.3|
{noformat}
postgres=# CREATE TABLE "my table"("column 1" varchar(100), "column 2"
varchar(100));
{noformat}
{noformat}
postgres=# COPY "my table" FROM '/test.csv' DELIMITERS ',' CSV;
{noformat}
{noformat}
postgres=# SELECT "column 2", "column 1" FROM "my table";
{noformat}
|{color:#14892c}*column 2*{color}|{color:#14892c}*column 1*{color}|
|text 2.1|text 1.1|
|text 2.2|text 1.2|
|text 2.3|text 1.3|
> Drill replacing spaces with underlines in the column names of text files with
> headers
> -
>
> Key: DRILL-7342
> URL: https://issues.apache.org/jira/browse/DRILL-7342
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Drill doesn't allow to query csvh columns with spaces.
> *Description:*
> Update Drill ctas format option to generate text file with header:
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create table with column names having spaces:
> {noformat}
> create table dfs.tmp.`csv table with spaces` (`Full Name`) as select 'James
> Bond' from (values(1));
> {noformat}
> Drill wrote column name with space:
> {noformat}
> hadoop fs -cat '/tmp/csv table with spaces/0_0_0.csvh'
> {noformat}
> |Full Name|
> |James Bond|
> Try to query this table without column name:
> {noformat}
> select * from dfs.tmp.`csv table with spaces`;
> {noformat}
> |{color:#ff}*Full_Name*{color}|
> |James Bond|
> {color:#ff}*Drill replaced space with underline.*{color}
> Try to select `Full Name` column with space:
> {noformat}
> select `Full Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> Drill
> |Full Name|
> | |
> When I changed space to underline, query returned the data:
> {noformat}
> select `Full_Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> |Full_Name|
> |James Bond|
> Drill can create csvh text files with spaces in the column names. But it's
> impossible to request data using the original column name.
> *Expected result*
> Space should be available character in the column names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DRILL-7342) Drill replacing spaces with underlines in the column names of text files with headers
[
https://issues.apache.org/jira/browse/DRILL-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903953#comment-16903953
]
Denys Ordynskiy commented on DRILL-7342:
*MySQL* allows to create column name with spaces and select the data by this
names.
test.csvh
|my column 1|my column 2|
|val 1.1|val 2.1|
|val 1.2|val 2.2|
{noformat}
mysql> CREATE DATABASE my_test_db;
{noformat}
{noformat}
mysql> USE my_test_db;
{noformat}
{noformat}
mysql> CREATE TABLE `table name`(`column 1` VARCHAR(100), `column 2`
VARCHAR(100));
{noformat}
{noformat}
mysql> SHOW VARIABLES LIKE "secure_file_priv";
{noformat}
|Variable_name|Value|
|secure_file_priv|/var/lib/mysql-files/|
{noformat}
cp test.csvh /var/lib/mysql-files/
{noformat}
{noformat}
mysql> LOAD DATA INFILE '/var/lib/mysql-files/test.csvh'
INTO TABLE `table name`
FIELDS TERMINATED BY ','
LINES TERMINATED BY '\n'
IGNORE 1 LINES;
{noformat}
{noformat}
mysql> SELECT * FROM `table name`;
{noformat}
Result contains spaces in the column names and cell values:
|column 1|column 2|
|val 1.1|val 2.1|
|val 1.2|val 2.2|
> Drill replacing spaces with underlines in the column names of text files with
> headers
> -
>
> Key: DRILL-7342
> URL: https://issues.apache.org/jira/browse/DRILL-7342
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Drill doesn't allow to query csvh columns with spaces.
> *Description:*
> Update Drill ctas format option to generate text file with header:
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create table with column names having spaces:
> {noformat}
> create table dfs.tmp.`csv table with spaces` (`Full Name`) as select 'James
> Bond' from (values(1));
> {noformat}
> Drill wrote column name with space:
> {noformat}
> hadoop fs -cat '/tmp/csv table with spaces/0_0_0.csvh'
> {noformat}
> |Full Name|
> |James Bond|
> Try to query this table without column name:
> {noformat}
> select * from dfs.tmp.`csv table with spaces`;
> {noformat}
> |{color:#ff}*Full_Name*{color}|
> |James Bond|
> {color:#ff}*Drill replaced space with underline.*{color}
> Try to select `Full Name` column with space:
> {noformat}
> select `Full Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> Drill
> |Full Name|
> | |
> When I changed space to underline, query returned the data:
> {noformat}
> select `Full_Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> |Full_Name|
> |James Bond|
> Drill can create csvh text files with spaces in the column names. But it's
> impossible to request data using the original column name.
> *Expected result*
> Space should be available character in the column names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DRILL-7342) Drill replacing spaces with underlines in the column names of text files with headers
[
https://issues.apache.org/jira/browse/DRILL-7342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903943#comment-16903943
]
Denys Ordynskiy commented on DRILL-7342:
Drill allows spaces in the column names for parquet tables:
Update Drill ctas format option to generate parquet table:
{noformat}
set `store.format` = 'parquet';
{noformat}
Create parquet table with column names having spaces:
{noformat}
create table dfs.tmp.`parquet table with spaces` (`Full Name`) as select 'James
Bond' from (values(1));
{noformat}
Try to query this table without column name:
{noformat}
select * from dfs.tmp.`parquet table with spaces`;
{noformat}
|{color:green}*Full Name*{color}|
|James Bond|
Try to query this table with column name:
{noformat}
select `Full Name` from dfs.tmp.`parquet table with spaces`;
{noformat}
|Full Name|
|{color:green}*James Bond*{color}|
> Drill replacing spaces with underlines in the column names of text files with
> headers
> -
>
> Key: DRILL-7342
> URL: https://issues.apache.org/jira/browse/DRILL-7342
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Drill doesn't allow to query csvh columns with spaces.
> *Description:*
> Update Drill ctas format option to generate text file with header:
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create table with column names having spaces:
> {noformat}
> create table dfs.tmp.`csv table with spaces` (`Full Name`) as select 'James
> Bond' from (values(1));
> {noformat}
> Drill wrote column name with space:
> {noformat}
> hadoop fs -cat '/tmp/csv table with spaces/0_0_0.csvh'
> {noformat}
> |Full Name|
> |James Bond|
> Try to query this table without column name:
> {noformat}
> select * from dfs.tmp.`csv table with spaces`;
> {noformat}
> |{color:#ff}*Full_Name*{color}|
> |James Bond|
> {color:#ff}*Drill replaced space with underline.*{color}
> Try to select `Full Name` column with space:
> {noformat}
> select `Full Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> Drill
> |Full Name|
> | |
> When I changed space to underline, query returned the data:
> {noformat}
> select `Full_Name` from dfs.tmp.`csv table with spaces`;
> {noformat}
> |Full_Name|
> |James Bond|
> Drill can create csvh text files with spaces in the column names. But it's
> impossible to request data using the original column name.
> *Expected result*
> Space should be available character in the column names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (DRILL-7342) Drill replacing spaces with underlines in the column names of text files with headers
Denys Ordynskiy created DRILL-7342:
--
Summary: Drill replacing spaces with underlines in the column
names of text files with headers
Key: DRILL-7342
URL: https://issues.apache.org/jira/browse/DRILL-7342
Project: Apache Drill
Issue Type: Bug
Reporter: Denys Ordynskiy
Drill doesn't allow to query csvh columns with spaces.
*Description:*
Update Drill ctas format option to generate text file with header:
{noformat}
set `store.format` = 'csvh';
{noformat}
Create table with column names having spaces:
{noformat}
create table dfs.tmp.`csv table with spaces` (`Full Name`) as select 'James
Bond' from (values(1));
{noformat}
Drill wrote column name with space:
{noformat}
hadoop fs -cat '/tmp/csv table with spaces/0_0_0.csvh'
{noformat}
|Full Name|
|James Bond|
Try to query this table without column name:
{noformat}
select * from dfs.tmp.`csv table with spaces`;
{noformat}
|{color:#ff}*Full_Name*{color}|
|James Bond|
{color:#ff}*Drill replaced space with underline.*{color}
Try to select `Full Name` column with space:
{noformat}
select `Full Name` from dfs.tmp.`csv table with spaces`;
{noformat}
Drill
|Full Name|
| |
When I changed space to underline, query returned the data:
{noformat}
select `Full_Name` from dfs.tmp.`csv table with spaces`;
{noformat}
|Full_Name|
|James Bond|
Drill can create csvh text files with spaces in the column names. But it's
impossible to request data using the original column name.
*Expected result*
Space should be available character in the column names.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DRILL-7322) Align cast boolean and schema boolean conversion
[
https://issues.apache.org/jira/browse/DRILL-7322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902982#comment-16902982
]
Denys Ordynskiy commented on DRILL-7322:
I found 3 another data types that have differences between the Drill internal
casting using schema and external casting by cast( as ) function.
*Float*
all_types.csvh
|float_col|varchar_float_col|
|340282356779733661637539395458142568447|340282356779733661637539395458142568447|
|-340282356779733661637539395458142568447|-340282356779733661637539395458142568447|
{noformat}
create schema (
float_col float not null,
varchar_float_col varchar not null
) for table dfs.tmp.`ischema/all_types`;
{noformat}
{noformat}
select
float_col,
sqlTypeOf(float_col) float_col_type,
cast(varchar_float_col as float) casted_float,
sqlTypeOf(cast(varchar_float_col as float)) casted_float_type,
varchar_float_col
from dfs.tmp.`ischema/all_types`;
{noformat}
Result:
|float_col|float_col_type|casted_float|casted_float_type|varchar_float_col|
|{color:red}*Infinity*{color}|FLOAT|{color:red}*3.4028235E38*{color}|FLOAT|340282356779733661637539395458142568447|
|{color:red}*-Infinity*{color}|FLOAT|{color:red}*-3.4028235E38*{color}|FLOAT|-340282356779733661637539395458142568447|
--
*Date*
all_types.csvh
|date_col|varchar_date_col|
|1-1-1|1-1-1|
{noformat}
create schema (
date_col date not null,
varchar_date_col varchar not null
) for table dfs.tmp.`ischema/all_types`;
{noformat}
{noformat}
select
date_col,
sqlTypeOf(date_col) date_col_type,
cast(varchar_date_col as date) casted_date_col,
sqlTypeOf(cast(varchar_date_col as date)) casted_date_col_type,
TO_DATE(varchar_date_col, '-MM-dd') to_date_col,
sqlTypeOf(TO_DATE(varchar_date_col, '-MM-dd')) to_date_col_type,
varchar_date_col
from dfs.tmp.`ischema/all_types`;
{noformat}
Result:
|date_col|date_col_type|casted_date_col|casted_date_col_type|to_date_col|to_date_col_type|varchar_date_col|
|{color:red}*0001-01-01*{color}|DATE|{color:red}*2001-01-01*{color}|DATE|{color:red}*0001-01-01*{color}|DATE|1-1-1|
--
*Time*
all_types.csvh
|time_col|varchar_time_col|
|01:01:001|01:01:001|
|01:001:001|01:001:001|
|001:001:001|001:001:001|
|1:1:1.|1:1:1.|
{noformat}
create schema (
time_col time not null,
varchar_time_col varchar not null
) for table dfs.tmp.`ischema/all_types`;
{noformat}
{noformat}
select
varchar_time_col,
time_col,
sqlTypeOf(time_col) time_col_type,
cast(varchar_time_col as time) casted_time_col,
sqlTypeOf(cast(varchar_time_col as time)) casted_time_col_type
from dfs.tmp.`ischema/all_types`;
{noformat}
|varchar_time_col|time_col|time_col_type|casted_time_col|casted_time_col_type|
|01:01:001|{color:red}*ERROR*{color}|{color:red}*ERROR*{color}|01:01:01|TIME|
|01:001:001|{color:red}*ERROR*{color}|{color:red}*ERROR*{color}|01:01:01|TIME|
|001:001:001|{color:red}*ERROR*{color}|{color:red}*ERROR*{color}|01:01:01|TIME|
|1:1:1.|{color:red}*ERROR*{color}|{color:red}*ERROR*{color}|01:01:01|TIME|
'01:01:001' - Error: DATA_READ ERROR: Invalid format:
"01:01:{color:red}*001*{color}" is malformed at "1"
'01:001:001'- Error: DATA_READ ERROR: Invalid format:
"01:{color:red}*001:001*{color}" is malformed at "1:001"
'001:001:001' - Error: DATA_READ ERROR: Invalid format:
"{color:red}*001:001:001*{color}" is malformed at "1:001:001"
'1:1:1.'- Error: DATA_READ ERROR: Invalid format:
"{color:red}*1:1:1.*{color}" is malformed at "."
Schema file reading and to_time() function throws an error if there are > 2
digits in the time unit. But cast( as time) works fine with '001' time literals.
> Align cast boolean and schema boolean conversion
>
>
> Key: DRILL-7322
> URL: https://issues.apache.org/jira/browse/DRILL-7322
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Information schema file allows converting any string to the boolean data type.
> But "case(.. as boolean)" statement throws an error:
> {color:#d04437}UserRemoteException : SYSTEM ERROR: IllegalArgumentException:
> Invalid value for boolean: a
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> IllegalArgumentException: Invalid value for boolean: a{color}
> *Information Schema file should allow using the same range of boolean
> literals as cast statement.*
> *Steps to reproduce:*
> Upload text file all_types.csvh to the DFS /tmp/ischema/all_types:
> {noformat}
> boolean_col,boolean_col_for_cast
> true,true
> 1,1
> t,t
> y,y
> yes,yes
> on,on
> false,false
> 0,0
> f,f
> n,n
> no,no
> off,off
> a,a
> -,-
> !,!
> `,`
> 7,7
> @,@
> ^,^
> *,*
> {noformat}
> *Create schema:*
> {noformat}
> create
[jira] [Created] (DRILL-7336) `cast_empty_string_to_null` option doesn't work when text file has > 1 column
Denys Ordynskiy created DRILL-7336:
--
Summary: `cast_empty_string_to_null` option doesn't work when text
file has > 1 column
Key: DRILL-7336
URL: https://issues.apache.org/jira/browse/DRILL-7336
Project: Apache Drill
Issue Type: Bug
Reporter: Denys Ordynskiy
*Description:*
1 - create 2 nullable csv files with 1 and 2 columns:
_one_col.csv_
{noformat}
1
2
4
{noformat}
_two_col.csv_
{noformat}
1,1
2,
,3
4,4
{noformat}
2 - enable option:
{noformat}
alter system set `drill.exec.functions.cast_empty_string_to_null`=true;
{noformat}
3 - query file with 1 column:
{noformat}
select columns[0] from dfs.tmp.`one_col.csv`;
{noformat}
| EXPR$0 |
| 1 |
| 2 |
| null|
| 4 |
4 - query file with 2 columns:
{noformat}
select columns[0] from dfs.tmp.`two_col.csv`;
{noformat}
*Expected result:*
Table with NULL in the 3-rd row:
| EXPR$0 |
| 1 |
| 2 |
| null|
| 4 |
*Actual result:*
{color:#d04437}Drill returns an empty string in the 3-rd row:{color}
| EXPR$0 |
| 1 |
| 2 |
| |
| 4 |
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (DRILL-7332) Drill requires parentheses in the empty file for 'LOAD' argument in the 'CREATE SCHEMA' command
[
https://issues.apache.org/jira/browse/DRILL-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16897139#comment-16897139
]
Denys Ordynskiy commented on DRILL-7332:
Successfully tested with Drill commit 5df449530b9165fbf77607170057e3ac5eb2116f
Tested queries (file:///home/user/for_load is an empty file):
|create or replace schema LOAD 'file:///home/user/for_load' for table
dfs.tmp.`test_table` properties ('drill.strict' = 'false');|
|create schema LOAD 'file:///home/user/for_load' for table dfs.tmp.`test_table`
properties ('drill.strict' = 'false');|
|create schema () for table dfs.tmp.`test_table` properties ('drill.strict' =
'false');|
|create or replace schema () for table dfs.tmp.`test_table` properties
('drill.strict' = 'false');|
Result is the same for every query:
{noformat}
describe schema for table dfs.tmp.`test_table`;
+--+
| schema
|
+--+
| {
"table" : "dfs.tmp.`test_table`",
"schema" : {
"type" : "tuple_schema",
"properties" : {
"drill.strict" : "false"
}
},
"version" : 1
} |
+--+
{noformat}
> 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
>Priority: Major
> Labels: ready-to-commit
> 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)
[jira] [Closed] (DRILL-7332) Drill requires parentheses in the empty file for 'LOAD' argument in the 'CREATE SCHEMA' command
[
https://issues.apache.org/jira/browse/DRILL-7332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7332.
--
> 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
>Priority: Major
> Labels: ready-to-commit
> 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)
[jira] [Created] (DRILL-7332) Drill requires parentheses in the empty file for 'LOAD' argument in the 'CREATE SCHEMA' command
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)
[jira] [Created] (DRILL-7323) Error scaling query results table in Drill Web UI
Denys Ordynskiy created DRILL-7323: -- Summary: Error scaling query results table in Drill Web UI Key: DRILL-7323 URL: https://issues.apache.org/jira/browse/DRILL-7323 Project: Apache Drill Issue Type: Bug Reporter: Denys Ordynskiy Attachments: 1_expanded_Drill_tab.png, 2_resized_Drill_tab.png, 3_maximized_Drill_tab.png *Steps to reproduce:* 1. In the Chrome browser open Drill Web UI "Query" page. 2. Maximize the browser window. 3. Run the sample query "SELECT employee_id FROM cp.`employee.json` LIMIT 20". 4. Query results table expands on all window "1_expanded_Drill_tab.png". 5. Resize the browser window "2_resized_Drill_tab.png". 6. Open a new browser tab and open some web page there. 7. Expand the browser window to the fullscreen. 8. Open Drill tab with query results table. *Expected result:* Query results table body should expand like the table header. *Actual result:* Query results table body didn't expand "3_maximized_Drill_tab.png". *Environment details:* OS - Ubuntu 16.04 Browser - Chrome v.75.0.3770.100 (Official Build) (64-bit) Apache Drill version: commit 66e8dd9f05ea068e27b272ed1b787004213c29e6 Author: Paul Rogers Date: Sun Jun 23 22:10:54 2019 -0700 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (DRILL-7322) Align cast boolean and schema boolean conversion
Denys Ordynskiy created DRILL-7322:
--
Summary: Align cast boolean and schema boolean conversion
Key: DRILL-7322
URL: https://issues.apache.org/jira/browse/DRILL-7322
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Denys Ordynskiy
Information schema file allows converting any string to the boolean data type.
But "case(.. as boolean)" statement throws an error:
{color:#d04437}UserRemoteException :SYSTEM ERROR: IllegalArgumentException:
Invalid value for boolean: a
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalArgumentException: Invalid value for boolean: a{color}
*Information Schema file should allow using the same range of boolean literals
as cast statement.*
*Steps to reproduce:*
Upload text file all_types.csvh to the DFS /tmp/ischema/all_types:
{noformat}
boolean_col,boolean_col_for_cast
true,true
1,1
t,t
y,y
yes,yes
on,on
false,false
0,0
f,f
n,n
no,no
off,off
a,a
-,-
!,!
`,`
7,7
@,@
^,^
*,*
{noformat}
*Create schema:*
{noformat}
create schema (boolean_col boolean, boolean_col_for_cast varchar) for table
dfs.tmp.`ischema/all_types`
{noformat}
*Run the query without cast:*
select boolean_col, sqlTypeOf(boolean_col) boolean_col_type,
boolean_col_for_cast, sqlTypeOf(boolean_col_for_cast) boolean_col_for_cast_type
from dfs.tmp.`ischema/all_types`
|boolean_col|boolean_col_type|boolean_col_for_cast|boolean_col_for_cast_type|
|true|BOOLEAN|true|CHARACTER VARYING|
|true|BOOLEAN|1|CHARACTER VARYING|
|true|BOOLEAN|t|CHARACTER VARYING|
|true|BOOLEAN|y|CHARACTER VARYING|
|true|BOOLEAN|yes|CHARACTER VARYING|
|true|BOOLEAN|on|CHARACTER VARYING|
|false|BOOLEAN|false|CHARACTER VARYING|
|false|BOOLEAN|0|CHARACTER VARYING|
|false|BOOLEAN|f|CHARACTER VARYING|
|false|BOOLEAN|n|CHARACTER VARYING|
|false|BOOLEAN|no|CHARACTER VARYING|
|false|BOOLEAN|off|CHARACTER VARYING|
|false|BOOLEAN|a|CHARACTER VARYING|
|false|BOOLEAN|-|CHARACTER VARYING|
|false|BOOLEAN|!|CHARACTER VARYING|
|false|BOOLEAN|`|CHARACTER VARYING|
|false|BOOLEAN|7|CHARACTER VARYING|
|false|BOOLEAN|@|CHARACTER VARYING|
|false|BOOLEAN|^|CHARACTER VARYING|
|false|BOOLEAN|*|CHARACTER VARYING|
*Run the query with cast:*
select boolean_col, sqlTypeOf(boolean_col) boolean_col_type,
cast(boolean_col_for_cast as boolean) boolean_col_for_cast,
sqlTypeOf(cast(boolean_col_for_cast as boolean)) boolean_col_for_cast_type from
dfs.tmp.`ischema/all_types`
{color:#d04437}UserRemoteException :SYSTEM ERROR: IllegalArgumentException:
Invalid value for boolean: a
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalArgumentException: Invalid value for boolean: *a*
Fragment 0:0
Please, refer to logs for more information.
[Error Id: b9deab6f-7fd4-40c0-acdf-b2e31747e16f on cv1:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-7079) Drill can't query views from the S3 storage when plain authentication is enabled
[
https://issues.apache.org/jira/browse/DRILL-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7079.
--
Successfully tested on Drill with commit id
be73250e68ffd836541223cf4aca395896362866.
> Drill can't query views from the S3 storage when plain authentication is
> enabled
>
>
> Key: DRILL-7079
> URL: https://issues.apache.org/jira/browse/DRILL-7079
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
>
> Enable plain authentication in Drill.
> Create the view on the S3 storage:
> create view s3.tmp.`testview` as select * from cp.`employee.json` limit 20;
> Try to select data from the created view:
> select * from s3.tmp.`testview`;
> *Actual result*:
> {noformat}
> 2019-02-27 17:01:09,202 [Client-1] INFO
> o.a.d.j.i.DrillCursor$ResultsListener - [#4] Query failed:
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> IllegalArgumentException: A valid userName is expected
> Please, refer to logs for more information.
> [Error Id: 2271c3aa-6d09-4b51-a585-0e0e954b46eb on maprhost:31010]
> at
> org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(QueryResultHandler.java:123)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:422)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:96)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:273)
> [drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:243)
> [drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:287)
> [netty-handler-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:312)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:286)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
>
[jira] [Closed] (DRILL-6562) Plugin Management improvements
[
https://issues.apache.org/jira/browse/DRILL-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6562.
--
Successfully tested on the Drill with commit id -
494c2060a385408f27185949e6899a9017b6b7ff
Checked scenarios for the JSON and HOCON formats.
More than one disabled and enabled plugins:
- export all plugins;
- export enabled plugins;
- export disabled plugins.
No enabled plugins:
- export all plugins;
- export enabled plugins;
- export disabled plugins.
No disabled plugins:
- export all plugins;
- export enabled plugins;
- export disabled plugins;
Exporting single plugin in the different state.
Exporting plugins after modify them on the other browser tab.
> Plugin Management improvements
> --
>
> Key: DRILL-6562
> URL: https://issues.apache.org/jira/browse/DRILL-6562
> Project: Apache Drill
> Issue Type: Improvement
> Components: Client - HTTP, Web Server
>Affects Versions: 1.14.0
>Reporter: Abhishek Girish
>Assignee: Vitalii Diravka
>Priority: Major
> Labels: doc-complete, ready-to-commit
> Fix For: 1.16.0
>
> Attachments: Export.png, ExportAll.png, Screenshot from 2019-03-21
> 01-18-17.png, Screenshot from 2019-03-21 02-52-50.png, Storage.png,
> UpdateExport.png, create.png, image-2018-07-23-02-55-02-024.png,
> image-2018-10-22-20-20-24-658.png, image-2018-10-22-20-20-59-105.png
>
>
> Follow-up to DRILL-4580.
> Drill Storage UI improvements are shown in attached screenshots.
> The changes for this ticket also provide Drill REST API improvements:
> [https://drill.apache.org/docs/rest-api-introduction/#get-storage-json]
> export all plugins: {{/storage.json}} or {{/storage/all-plugins.json}}
> export enabled plugins: {{/storage/enabled-plugins.json}}
> export disabled plugins: {{/storage/disabled-plugins.json}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-7115) Improve Hive schema show tables performance
[
https://issues.apache.org/jira/browse/DRILL-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7115.
--
Successfully tested on the release Drill v1.16 rc2
Created 8136 tables in hive.
In sqlline:
{noformat}
use hive;
show tables;
{noformat}
On the Drill before fix (commit id - 4627973bde9847a4eb2672c44941136c167326a1)
8,136 rows selected (106.361 seconds)
8,136 rows selected (113.649 seconds)
8,136 rows selected (110.421 seconds)
8,136 rows selected (106.415 seconds)
8,136 rows selected (106.863 seconds)
On the release Drill v1.16 rc2:
8,136 rows selected (6.578 seconds)
8,136 rows selected (6.387 seconds)
8,136 rows selected (6.461 seconds)
8,136 rows selected (7.123 seconds)
8,136 rows selected (6.303 seconds)
On the hive shell:
{noformat}
show tables;
{noformat}
Time taken: 0.867 seconds, Fetched: 8136 row(s)
Time taken: 0.049 seconds, Fetched: 8136 row(s)
Time taken: 0.05 seconds, Fetched: 8136 row(s)
Time taken: 0.047 seconds, Fetched: 8136 row(s)
Time taken: 0.045 seconds, Fetched: 8136 row(s)
> Improve Hive schema show tables performance
> ---
>
> Key: DRILL-7115
> URL: https://issues.apache.org/jira/browse/DRILL-7115
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Hive, Storage - Information Schema
>Affects Versions: 1.15.0
>Reporter: Igor Guzenko
>Assignee: Igor Guzenko
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
>
> In Sqlline(Drill), "show tables" on a Hive schema is taking nearly 15mins to
> 20mins. The schema has nearly ~8000 tables.
> Whereas the same in beeline(Hive) is throwing the result in a split second(~
> 0.2 secs).
> I tested the same in my test cluster by creating 6000 tables(empty!) in Hive
> and then doing "show tables" in Drill. It took more than 2 mins(~140 secs).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6811) Fix type inference to return correct data mode for boolean functions
[
https://issues.apache.org/jira/browse/DRILL-6811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6811.
--
Tested with Drill version 1.16.0-SNAPSHOT (commit
0f05f53e0e34ccc0606a561f44d82b794be32b83).
Cases verified in the SQuirreL SQL client:
- IS NULL;
- IS NOT NULL;
- NOT;
- IS TRUE;
- IS NOT TRUE.
The result of this functions is not nullable.
> Fix type inference to return correct data mode for boolean functions
>
>
> Key: DRILL-6811
> URL: https://issues.apache.org/jira/browse/DRILL-6811
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> For some functions which return a boolean result and cannot return null
> values {{DrillDefaultSqlReturnTypeInference.inferReturnType()}} returns type
> with nullable data mode.
> Examples of the functions which cannot return nulls:
> * {{IS NULL}}
> * {{IS NOT NULL}}
> * {{NOT}}
> * {{IS TRUE}}
> and other.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-1248) Add support for using aliases in group by
[
https://issues.apache.org/jira/browse/DRILL-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-1248.
--
Tested with Drill version 1.16.0-SNAPSHOT (commit
0f05f53e0e34ccc0606a561f44d82b794be32b83).
Cases verified:
- GROUP BY with the alias;
- GROUP BY with the column index;
- HAVING with the alias;
- ORDER BY with the alias;
- ORDER BY with the column index.
> Add support for using aliases in group by
> -
>
> Key: DRILL-1248
> URL: https://issues.apache.org/jira/browse/DRILL-1248
> Project: Apache Drill
> Issue Type: Improvement
> Components: SQL Parser
>Reporter: Jim Scott
>Assignee: Arina Ielchiieva
>Priority: Major
> Labels: doc-complete, ready-to-commit
> Fix For: 1.15.0
>
>
> when I select using a function and alias the resultant function value it
> won't parse properly saying the alias is ambiguous. I know that this is a
> debatable / questionable topic, but with this engine being so flexible it
> seems that in order to support all of the formatting, casting, etc.. that
> will likely occur having the group by support an alias would be a big deal.
> This in my opinion is nothing like an ordinal group by.
> This works:
> select extract(year from to_date(crimes.datetime, 'MM/DD/ hh:mm:ss a'))
> from BLAH group by extract(year from to_date(crimes.datetime, 'MM/DD/
> hh:mm:ss a'));
> This doesn't:
> select extract(year from to_date(crimes.datetime, 'MM/DD/ hh:mm:ss a'))
> as mygroup from BLAH group by mygroup
> *For documentation*
> Positional / named alias are allowed in group by / order by / having clauses:
> {noformat}
> select length(n_name), n_regionkey from cp.`tpch/nation.parquet` group by 1,
> 2;
> select length(n_name) as len, n_regionkey as key from
> cp.`tpch/nation.parquet` group by len, key;
> select length(n_name) as len, count(*) as cnt from cp.`tpch/nation.parquet`
> group by length(n_name) having cnt > 1;
> select n_regionkey, n_name from cp.`tpch/nation.parquet` order by 1, 2;
> select n_regionkey as r, n_name as n from cp.`tpch/nation.parquet` order by
> r, n;
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6814. -- Resolution: Cannot Reproduce > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > Attachments: S3investigate.txt > > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6783) CAST string literal as INTERVAL MONTH/YEAR works inconsistently when selecting from a table with multiple rows
[
https://issues.apache.org/jira/browse/DRILL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6783.
--
Tested with Drill version 1.16.0-SNAPSHOT (commit
172dc7cb4c3323e9650db2bf7fe1eab76c2fbbe1).
Cases verified:
- casting string month interval literal as "interval month";
- casting string month interval literal as "interval year";
- casting string month interval literal as "interval day";
- casting string day interval literal as "interval month";
- casting string day interval literal as "interval day".
> CAST string literal as INTERVAL MONTH/YEAR works inconsistently when
> selecting from a table with multiple rows
> --
>
> Key: DRILL-6783
> URL: https://issues.apache.org/jira/browse/DRILL-6783
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Bohdan Kazydub
>Assignee: Bohdan Kazydub
>Priority: Critical
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> Casting string literal as INTERVAL MONTH or INTERVAL YEAR produces different
> values for each row (actually, with period of 4) when selecting data from
> table with more than one row.
> For example:
> {code}
> 0: jdbc:drill:zk=local> select cast('P314M' as interval month) from
> cp.`employee.json` limit 10;
> +--+
> | EXPR$0 |
> +--+
> | 26 years 2 months |
> | 81089877 years 5 months |
> | 1714858 years 8 months |
> | 6698 years 8 months |
> | 26 years 2 months |
> | 81089877 years 5 months |
> | 1714858 years 8 months |
> | 6698 years 8 months |
> | 26 years 2 months |
> | 81089877 years 5 months |
> +--+
> 10 rows selected (0.186 seconds)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6713) Infinite loop when retrieving decimal value with scale = -1
[
https://issues.apache.org/jira/browse/DRILL-6713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6713.
--
Successfully verified.
Queries like {color:red}./querySubmitter query='select
cast('99' as decimal(38,0)) + cast('99' as
decimal(38,0)) from (values(1))' type=sql connectStr=local=localhost:31010
api=async logLevel=trace user=usr password=passw{color} going to the infinite
loop on Drill before fix and successfully returns the result on the Drill with
this fix.
> Infinite loop when retrieving decimal value with scale = -1
> ---
>
> Key: DRILL-6713
> URL: https://issues.apache.org/jira/browse/DRILL-6713
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - C++
>Affects Versions: 1.14.0
>Reporter: Rob Wu
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Fix For: 1.15.0
>
>
>
> The server returns scale value of -1 for this query
> select cast('99' as decimal(18,0)) +
> cast('9' as decimal(38,0)) from
> (values(1))
>
> The getValueAt() function did not take into account of the possibility of -1
> scale and will go into infinite loop of appending 0 to the string buffer.
> [https://github.com/apache/drill/blob/1.14.0/contrib/native/client/src/include/drill/recordBatch.hpp#L752]
>
> This can be reproduced query submitter.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6612) Query fails with AssertionError when joining persistent and temporary tables
[
https://issues.apache.org/jira/browse/DRILL-6612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6612.
--
> Query fails with AssertionError when joining persistent and temporary tables
>
>
> Key: DRILL-6612
> URL: https://issues.apache.org/jira/browse/DRILL-6612
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.12.0
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.14.0
>
>
> *Problem description*
> When joining persistent and temporary tables:
> {code:sql}
> create TEMPORARY table temp_tab as select '12312' as c2;
> create table pers_tab as select '12312' as c1;
> select * from `%s` a join `%s` b on a.c1 = b.c2
> {code}
> Query fails with AssertionError:
> {noformat}
> [Error Id: 85663e83-d7f0-4f84-92ea-fb329e31aec5 on user515050-pc:31013]
> org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
> AssertionError: Field ordinal 1 is invalid for type '(DrillRecordRow[**])'
> [Error Id: 85663e83-d7f0-4f84-92ea-fb329e31aec5 on user515050-pc:31013]
> at
> org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:633)
> ~[classes/:na]
> at
> org.apache.drill.exec.work.foreman.Foreman$ForemanResult.close(Foreman.java:761)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.checkCommonStates(QueryStateProcessor.java:325)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.planning(QueryStateProcessor.java:221)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.moveToState(QueryStateProcessor.java:83)
> [classes/:na]
> at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:293)
> [classes/:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [na:1.8.0_171]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [na:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_171]
> Caused by: org.apache.drill.exec.work.foreman.ForemanException: Unexpected
> exception during fragment initialization: while converting CAST(`a`.`colA2`
> AS VARCHAR) = CAST(`b`.`colB2` AS VARCHAR)
> at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:294)
> [classes/:na]
> ... 3 common frames omitted
> Caused by: java.lang.RuntimeException: while converting CAST(`a`.`colA2` AS
> VARCHAR) = CAST(`b`.`colB2` AS VARCHAR)
> at
> org.apache.calcite.sql2rel.ReflectiveConvertletTable$1.convertCall(ReflectiveConvertletTable.java:90)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:63)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4656)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:3994)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:138)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4558)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertJoinCondition(SqlToRelConverter.java:2601)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertFrom(SqlToRelConverter.java:2048)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectImpl(SqlToRelConverter.java:643)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelect(SqlToRelConverter.java:624)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3058)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQuery(SqlToRelConverter.java:560)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.drill.exec.planner.sql.SqlConverter.toRel(SqlConverter.java:384)
> ~[classes/:na]
> at
> org.apache.drill.exec.planner.sql.handlers.DefaultSqlHandler.convertToRel(DefaultSqlHandler.java:664)
> ~[classes/:na]
> at
>
[jira] [Closed] (DRILL-6624) Fix loss of the table row type when the same schema name was specified as single path and as a complex path in the same query
[
https://issues.apache.org/jira/browse/DRILL-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6624.
--
> Fix loss of the table row type when the same schema name was specified as
> single path and as a complex path in the same query
> -
>
> Key: DRILL-6624
> URL: https://issues.apache.org/jira/browse/DRILL-6624
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Volodymyr Vysotskyi
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.14.0
>
>
> Current Drill behavior is to threat schema with different combinations of
> quotes in the same way: {{`dfs.tmp`, dfs.tmp, `dfs`.`tmp`}}.
> After the fix for DRILL-5089, table information is lost when these different
> combinations of schema paths were used.
> For example, query:
> {code:sql}
> create table `dfs.tmp`.t1 as select 1 as c1
> create table dfs.tmp.t2 as select 1 as c2
> create table dfs.tmp.`t3` as SELECT 1 as c2,1 as c1
> select a.c2 from dfs.tmp.`t2` a
> join dfs.tmp.`t3` b ON b.c2 = a.c2
> join `dfs.tmp`.t1 c ON b.c1 = c.c1
> {code}
> fails with error:
> {noformat}
> 14:49:24.508 [24ae33bb-41be-f9c2-c0f0-4d8901becf62:foreman] ERROR
> o.a.drill.exec.work.foreman.Foreman - SYSTEM ERROR: AssertionError: Field
> ordinal 1 is invalid for type '(DrillRecordRow[**])'
> [Error Id: 52254f1e-eefb-4de7-b8bd-2adff296a799 on user515050-pc:31010]
> org.apache.drill.common.exceptions.UserException: SYSTEM ERROR:
> AssertionError: Field ordinal 1 is invalid for type '(DrillRecordRow[**])'
> [Error Id: 52254f1e-eefb-4de7-b8bd-2adff296a799 on user515050-pc:31010]
> at
> org.apache.drill.common.exceptions.UserException$Builder.build(UserException.java:633)
> ~[classes/:na]
> at
> org.apache.drill.exec.work.foreman.Foreman$ForemanResult.close(Foreman.java:761)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.checkCommonStates(QueryStateProcessor.java:325)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.planning(QueryStateProcessor.java:221)
> [classes/:na]
> at
> org.apache.drill.exec.work.foreman.QueryStateProcessor.moveToState(QueryStateProcessor.java:83)
> [classes/:na]
> at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:293)
> [classes/:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [na:1.8.0_171]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [na:1.8.0_171]
> at java.lang.Thread.run(Thread.java:748) [na:1.8.0_171]
> Caused by: org.apache.drill.exec.work.foreman.ForemanException: Unexpected
> exception during fragment initialization: while converting `b`.`c1` = `a`.`c1`
> at org.apache.drill.exec.work.foreman.Foreman.run(Foreman.java:294)
> [classes/:na]
> ... 3 common frames omitted
> Caused by: java.lang.RuntimeException: while converting `b`.`c1` = `a`.`c1`
> at
> org.apache.calcite.sql2rel.ReflectiveConvertletTable$1.convertCall(ReflectiveConvertletTable.java:90)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlNodeToRexConverterImpl.convertCall(SqlNodeToRexConverterImpl.java:63)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:4656)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.visit(SqlToRelConverter.java:3994)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at org.apache.calcite.sql.SqlCall.accept(SqlCall.java:138)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter$Blackboard.convertExpression(SqlToRelConverter.java:4558)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertJoinCondition(SqlToRelConverter.java:2601)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertFrom(SqlToRelConverter.java:2048)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelectImpl(SqlToRelConverter.java:643)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertSelect(SqlToRelConverter.java:624)
> ~[calcite-core-1.16.0-drill-r6.jar:1.16.0-drill-r6]
> at
> org.apache.calcite.sql2rel.SqlToRelConverter.convertQueryRecursive(SqlToRelConverter.java:3058)
>
[jira] [Closed] (DRILL-6819) Remove invisible "back" link on query results page in Drill WebUI
[ https://issues.apache.org/jira/browse/DRILL-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6819. -- > Remove invisible "back" link on query results page in Drill WebUI > - > > Key: DRILL-6819 > URL: https://issues.apache.org/jira/browse/DRILL-6819 > Project: Apache Drill > Issue Type: Bug > Components: Web Server >Affects Versions: 1.10.0 >Reporter: Denys Ordynskiy >Assignee: Denys Ordynskiy >Priority: Minor > Labels: ready-to-commit > Fix For: 1.15.0 > > Attachments: image.png > > > In Drill WebUI on page with query results and some other pages we have > invisible link with text - "back" and URL - "/queries". Since we have visible > link "Query" on navigation tab with the same URL, we don't need "back" link > on query results page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6869) Drill allows to create views outside workspace
[
https://issues.apache.org/jira/browse/DRILL-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6869.
--
> Drill allows to create views outside workspace
> --
>
> Key: DRILL-6869
> URL: https://issues.apache.org/jira/browse/DRILL-6869
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Minor
> Fix For: 1.16.0
>
> Attachments: Amazon_S3_FS_stor_plugin.json,
> FileSystem_stor_plugin.json, MapR_FS_stor_plugin.json
>
>
> Parameter 'allowAccessOutsideWorkspace' is false for tested workspaces.
> On MaprFS and S3 storages Drill allows to create views outside workspace.
> *Example on MapRFS:*
> create view dfs.tmp.`{color:#d04437}*/*{color}testbugonmfs` as SELECT * FROM
> cp.`employee.json` LIMIT 20;
> |ok|summary|
> |true|View '/testbugonmfs' *created successfully in 'dfs.tmp' schema*|
> 1 row selected (0.93 seconds)
> The file "testbugonmfs.view.drill" was *created* in the *root "/" folder,*
> but not in used workspace "/tmp" folder.
> Select query works with root "/" folder {color:#d04437}*outside*{color} the
> dfs.tmp workspace:
> select count * from dfs.tmp.`{color:#d04437}*/*{color}testbugonmfs`;
> |EXPR$0|
> |20|
> 1 row selected (1.813 seconds)
>
> *Example on S3*:
> create view s3.tmp.`{color:#d04437}*/*{color}testbugons3` as SELECT * FROM
> cp.`employee.json` LIMIT 20;
> |ok|summary|
> |true|View '/testbugons3' *created successfully in 's3.tmp' schema*|
> 1 row selected (3.455 seconds)
>
> The file "testbugons3.view.drill" was *created* in the *root "/" bucket
> folder*, but not in used workspace "/tmp" folder.
> Select query also works with root "/" bucket folder
> {color:#d04437}*outside*{color} the s3.tmp workspace:
> select count * from s3.tmp.`/testbugons3`;
> |EXPR$0|
> |20|
> 1 row selected (3.209 seconds)
>
> *Expected result:*
> View should be created within workspace
> On FileSystem storage plugin Drill doesn't allow to create views outside
> workspace.
> Query "create view dfs.tmp.`/testbugonfs` as SELECT * FROM
> cp.`employee.json` LIMIT 20;"
> Returns an error: "{color:#d04437}Error: SYSTEM ERROR:
> FileNotFoundException: /testbugonfs.view.drill (Permission denied){color}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6931) Drill "SHOW FILES" command duplicates empty S3 folders as subfolders
[ https://issues.apache.org/jira/browse/DRILL-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6931. -- > Drill "SHOW FILES" command duplicates empty S3 folders as subfolders > > > Key: DRILL-6931 > URL: https://issues.apache.org/jira/browse/DRILL-6931 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Denys Ordynskiy >Assignee: Arina Ielchiieva >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > *Description:* > If folder was created by pressing "+ Create folder" button on the S3 > management console, > Drill "SHOW FILES" command showing in this folder another subfolder with the > same name. > But this subfolder doesn't exist. > *Example:* > - login to the S3 management console; > - open your bucket `some_bucket`; > - create an empty folder `my_test_folder` by pressing "+ Create folder" > button; > - run Drill and open sqlline client; > - exec query "show files in s3.tmp.`my_test_folder`;" > *Actual result:* > |name|isDirectory|isFile|length|owner|group|permissions|accessTime|modificationTime| > |my_test_folder|true|false|0| | |rwxrwxrwx|1970-01-01 03:00:00.0|1970-01-01 > 03:00:00.0| > 1 row selected (1.318 seconds) > *Expected result:* > an empty result set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6894) CTAS and CTTAS are not working on S3 storage when cache is disabled
[
https://issues.apache.org/jira/browse/DRILL-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6894.
--
> CTAS and CTTAS are not working on S3 storage when cache is disabled
> ---
>
> Key: DRILL-6894
> URL: https://issues.apache.org/jira/browse/DRILL-6894
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
> Attachments: CTAS_drillbit.log, CTAS_drillbit_queries.json,
> CTAS_sqlline.log, CTTAS_drillbit.log, CTTAS_drillbit_queries.json,
> CTTAS_sqlline.log, s3.json
>
>
> When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the
> config section and Drill is restarted,
> CTAS and CTTAS queries throwing error in Sqlline:
> *create temporary table s3.tmp.`cttastblwithcache2` as select * from
> cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
> (state=,code=0){color}
> *create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
> (state=,code=0){color}
> Logs and my storage plugin are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6875.
--
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6874) CTAS from json to parquet is not working on S3 storage
[
https://issues.apache.org/jira/browse/DRILL-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6874.
--
Successfully tested on parquet, json and csv files in CTAS.
> CTAS from json to parquet is not working on S3 storage
> --
>
> Key: DRILL-6874
> URL: https://issues.apache.org/jira/browse/DRILL-6874
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.15.0
>
> Attachments: ctasjsontoparquet.zip, drillbit.log,
> drillbit_queries.json, s3src.json, sqlline.log
>
>
> Json file "s3src.json" was uploaded to the s3 storage.
> Query from Json works fine:
> select * from s3.tmp.`s3src.json`;
> | id | first_name | last_name |
> | 1 | first_name1 | last_name1 |
> | 2 | first_name2 | last_name2 |
> | 3 | first_name3 | last_name3 |
> | 4 | first_name4 | last_name4 |
> | 5 | first_name5 | last_name5 |
> 5 rows selected (2.803 seconds)
> CTAS from this json file returns successfully result:
> create table s3.tmp.`ctasjsontoparquet` as select * from s3.tmp.`s3src.json`;
> | Fragment | Number of records written |
> | 0_0 | 5 |
> 1 row selected (9.264 seconds)
> *Query from the created parquet table {color:#d04437}throws an error:{color}*
> select * from s3.tmp.`ctasjsontoparquet`;
> {code:java}
> Error: INTERNAL_ERROR ERROR: Error in parquet record reader.
> Message: Failure in setting up reader
> Parquet Metadata: ParquetMetaData{FileMetaData{schema: message root {
> optional int64 id;
> optional binary first_name (UTF8);
> optional binary last_name (UTF8);
> }
> , metadata: {drill-writer.version=2, drill.version=1.15.0-SNAPSHOT}}, blocks:
> [BlockMetaData{5, 360 [ColumnMetaData{UNCOMPRESSED [id] optional int64 id
> [BIT_PACKED, RLE, PLAIN], 4}, ColumnMetaData{UNCOMPRESSED [first_name]
> optional binary first_name (UTF8) [BIT_PACKED, RLE, PLAIN], 111},
> ColumnMetaData{UNCOMPRESSED [last_name] optional binary last_name (UTF8)
> [BIT_PACKED, RLE, PLAIN], 241}]}]}
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 885723e4-8385-4fb0-87dd-c08b0570db95 on maprhost:31010]
> (state=,code=0)
> {code}
> The same CTAS query works fine on MapRFS and FileSystem storages.
> Log files, json file and created parquet file from S3 are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6863) Drop table is not working if path within workspace starts with '/'
[
https://issues.apache.org/jira/browse/DRILL-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6863.
--
Successfully tested on S3, DFS and FileSystem storage plugins on CTAS and CTTAS.
> Drop table is not working if path within workspace starts with '/'
> --
>
> Key: DRILL-6863
> URL: https://issues.apache.org/jira/browse/DRILL-6863
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> Drill works incorrectly if path to the table within workspace starts with '/'
> Request "drop table s3.tmp.`drill/transitive_closure/tab1`" works fine,
> but if I add '/' in the begining of the tables path "drop table
> s3.tmp.`{color:#d04437}/{color}drill/transitive_closure/tab1`", Drill is
> trying to find table in the root directory but not in workspace path.
> *Actual result:*
> Drill returns successfully response
> "Table [/drill/transitive_closure/tab1] dropped"
> but table was not dropped.
>
> *Expected result:*
> Table was droped.
> Bug can be reproduced on S3 and DFS storages. On FileSystem storage Drill
> successfully returns error message if "drop table" query starts with '/' in
> table path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6662) Access AWS access key ID and secret access key using Credential Provider API for S3 storage plugin
[ https://issues.apache.org/jira/browse/DRILL-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6662. -- Successfully tested on Drill storage plugin and Drill core-site.xml > Access AWS access key ID and secret access key using Credential Provider API > for S3 storage plugin > -- > > Key: DRILL-6662 > URL: https://issues.apache.org/jira/browse/DRILL-6662 > Project: Apache Drill > Issue Type: Improvement >Reporter: Bohdan Kazydub >Assignee: Bohdan Kazydub >Priority: Major > Labels: doc-complete, ready-to-commit > Fix For: 1.15.0 > > > Hadoop provides [CredentialProvider > API|[https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html]] > which allows passwords and other sensitive secrets to be stored in an > external provider rather than in configuration files in plaintext. > Currently S3 storage plugin is accessing passwords, namely > 'fs.s3a.access.key' and 'fs.s3a.secret.key', stored in clear text in > Configuration with get() method. To give users an ability to remove clear > text passwords for S3 from configuration files Configuration.getPassword() > method should be used, given they configure > 'hadoop.security.credential.provider.path' property which points to a file > containing encrypted passwords instead of configuring two aforementioned > properties. > By using this approach, credential providers will be checked first and if the > secret is not provided or providers are not configured there will be a > fallback to secrets configured in clear text (unless > 'hadoop.security.credential.clear-text-fallback' is configured to be > "false"), thus making new change backwards-compatible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6680) Expose SHOW FILES command into INFORMATION_SCHEMA
[ https://issues.apache.org/jira/browse/DRILL-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6680. -- Successfully tested on S3, FileSystem and DFS. > Expose SHOW FILES command into INFORMATION_SCHEMA > - > > Key: DRILL-6680 > URL: https://issues.apache.org/jira/browse/DRILL-6680 > Project: Apache Drill > Issue Type: New Feature >Affects Versions: 1.14.0 >Reporter: Arina Ielchiieva >Assignee: Arina Ielchiieva >Priority: Major > Labels: doc-complete, ready-to-commit > Fix For: 1.15.0 > > > Link to design document - > https://docs.google.com/document/d/1UnvATwH4obn1-XsA83xMz3LtylbMu867eBLN9r3eV3k/edit# -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6094) Decimal data type enhancements
[ https://issues.apache.org/jira/browse/DRILL-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy closed DRILL-6094. -- > Decimal data type enhancements > -- > > Key: DRILL-6094 > URL: https://issues.apache.org/jira/browse/DRILL-6094 > Project: Apache Drill > Issue Type: Improvement >Affects Versions: 1.12.0 >Reporter: Volodymyr Vysotskyi >Assignee: Volodymyr Vysotskyi >Priority: Major > Labels: doc-complete > Fix For: 1.14.0 > > > Currently, Decimal types are disabled by default since existing Decimal > implementation has a lot of flaws and performance problems. The goal of this > Jira to describe majority of them and possible ways of improving existing > implementation to be able to enable Decimal data types by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (DRILL-6472) Drill allows to use decimal zero precision in CAST function for CTAS
[
https://issues.apache.org/jira/browse/DRILL-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6472.
--
> Drill allows to use decimal zero precision in CAST function for CTAS
>
>
> Key: DRILL-6472
> URL: https://issues.apache.org/jira/browse/DRILL-6472
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.14.0
>
>
> I can run query with casting data for decimal with zero precision in SELECT
> statement
> {code:java}
> select cast(.05 as decimal(0,5));
> {code}
> {code:java}
> +-+
> | EXPR$0 |
> +-+
> | .05000 |
> +-+
> {code}
> Also I can use this query for CTAS
> {code:java}
> create table dfs.tmp.`zero_pr` as select cast(.05 as decimal(0,5));
> {code}
> {code:java}
> +--+---+
> | Fragment | Number of records written |
> +--+---+
> | 0_0 | 1 |
> +--+---+
> {code}
> But when I try to select data from this table, I get an error:
> {code:java}
> create table dfs.tmp.`zero_pr` as select cast(.05 as decimal(0,5));
> {code}
> {code:java}
> Error: SYSTEM ERROR: IllegalArgumentException: Invalid DECIMAL precision: 0
> [Error Id: 2e320f55-aa65-4127-82be-6256e0744bdc on maprhost:31010]
> (state=,code=0){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-6471) Different result for CAST String and Decimal literals as Decimal
[
https://issues.apache.org/jira/browse/DRILL-6471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-6471.
--
> Different result for CAST String and Decimal literals as Decimal
>
>
> Key: DRILL-6471
> URL: https://issues.apache.org/jira/browse/DRILL-6471
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Volodymyr Vysotskyi
>Priority: Major
> Fix For: 1.14.0
>
>
> If I cast String and Decimal literals as Decimal and literal precision is
> more than I casting to,
> I see different results for the same literal data in String and Decimal
> formats
> SELECT cast('1234.5678' as DECIMAL(2, 2));
> {code:java}
> +--+
> | EXPR$0 |
> +--+
> | 1200.00 |
> +--+
> {code}
> SELECT cast(1234.5678 as DECIMAL(2, 2));
> {code:java}
> +-+
> | EXPR$0 |
> +-+
> | 0.12|
> +-+
> {code}
> CAST result for one number in String and Decimal formats should be the same.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-7320) DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision file
[
https://issues.apache.org/jira/browse/DRILL-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7320.
--
Resolution: Invalid
> DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision
> file
> --
>
> Key: DRILL-7320
> URL: https://issues.apache.org/jira/browse/DRILL-7320
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Denys Ordynskiy
>Assignee: Denys Ordynskiy
>Priority: Major
>
> *Description:*
> Set CTAS output format to 'csvh':
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create csvh table with timestamp string:
> {noformat}
> drop table if exists dfs.tmp.`employee_test`;
> create table dfs.tmp.`employee_test` as select
> hire_date
> from cp.`employee.json` LIMIT 2;
> {noformat}
> Run the query without INFORMATION SCHEMA file using cast():
> {noformat}
> set `store.table.use_schema_file` = false;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> Create Schema Provision file:
> {noformat}
> create schema (
> hire_date TIMESTAMP
> ) for table dfs.tmp.`employee_test`;
> {noformat}
> Run the query using Schema Provision file:
> {noformat}
> alter system set `store.table.use_schema_file` = true;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> *Expected result:*
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> *Actual result:*
> {color:#d04437}UserRemoteException : DATA_READ ERROR: Invalid format:
> "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
>
> org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
> Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
> Line 2
> Record 0
> Fragment 0:0
> [Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (DRILL-7320) DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision file
[
https://issues.apache.org/jira/browse/DRILL-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy reopened DRILL-7320:
Assignee: Denys Ordynskiy (was: Arina Ielchiieva)
> DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision
> file
> --
>
> Key: DRILL-7320
> URL: https://issues.apache.org/jira/browse/DRILL-7320
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Denys Ordynskiy
>Assignee: Denys Ordynskiy
>Priority: Major
>
> *Description:*
> Set CTAS output format to 'csvh':
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create csvh table with timestamp string:
> {noformat}
> drop table if exists dfs.tmp.`employee_test`;
> create table dfs.tmp.`employee_test` as select
> hire_date
> from cp.`employee.json` LIMIT 2;
> {noformat}
> Run the query without INFORMATION SCHEMA file using cast():
> {noformat}
> set `store.table.use_schema_file` = false;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> Create Schema Provision file:
> {noformat}
> create schema (
> hire_date TIMESTAMP
> ) for table dfs.tmp.`employee_test`;
> {noformat}
> Run the query using Schema Provision file:
> {noformat}
> alter system set `store.table.use_schema_file` = true;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> *Expected result:*
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> *Actual result:*
> {color:#d04437}UserRemoteException : DATA_READ ERROR: Invalid format:
> "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
>
> org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
> Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
> Line 2
> Record 0
> Fragment 0:0
> [Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7320) DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision file
[
https://issues.apache.org/jira/browse/DRILL-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7320:
---
Description:
*Description:*
Set CTAS output format to 'csvh':
{noformat}
set `store.format` = 'csvh';
{noformat}
Create csvh table with timestamp string:
{noformat}
drop table if exists dfs.tmp.`employee_test`;
create table dfs.tmp.`employee_test` as select
hire_date
from cp.`employee.json` LIMIT 2;
{noformat}
Run the query without INFORMATION SCHEMA file using cast():
{noformat}
set `store.table.use_schema_file` = false;
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`;
{noformat}
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
Create Schema Provision file:
{noformat}
create schema (
hire_date TIMESTAMP
) for table dfs.tmp.`employee_test`;
{noformat}
Run the query using Schema Provision file:
{noformat}
alter system set `store.table.use_schema_file` = true;
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`;
{noformat}
*Expected result:*
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
*Actual result:*
{color:#d04437}UserRemoteException :DATA_READ ERROR: Invalid format:
"1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
Line 2
Record 0
Fragment 0:0
[Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
was:
*Description:*
Set CTAS output format to 'csvh':
{noformat}
set `store.format` = 'csvh'
{noformat}
Create csvh table with timestamp string:
{noformat}
drop table if exists dfs.tmp.`employee_test`
create table dfs.tmp.`employee_test` as select
hire_date
from cp.`employee.json` LIMIT 2
{noformat}
Run the query without INFORMATION SCHEMA file using cast():
{noformat}
set `store.table.use_schema_file` = false
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`
{noformat}
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
Create Schema Provision file:
{noformat}
create schema (
hire_date TIMESTAMP
) for table dfs.tmp.`employee_test`
{noformat}
Run the query using Schema Provision file:
{noformat}
alter system set `store.table.use_schema_file` = true
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`
{noformat}
*Expected result:*
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
*Actual result:*
{color:#d04437}UserRemoteException :DATA_READ ERROR: Invalid format:
"1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
Line 2
Record 0
Fragment 0:0
[Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
> DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision
> file
> --
>
> Key: DRILL-7320
> URL: https://issues.apache.org/jira/browse/DRILL-7320
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Denys Ordynskiy
>Assignee: Arina Ielchiieva
>Priority: Major
>
> *Description:*
> Set CTAS output format to 'csvh':
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create csvh table with timestamp string:
> {noformat}
> drop table if exists dfs.tmp.`employee_test`;
> create table dfs.tmp.`employee_test` as select
> hire_date
> from cp.`employee.json` LIMIT 2;
> {noformat}
> Run the query without INFORMATION SCHEMA file using cast():
> {noformat}
> set `store.table.use_schema_file` = false;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> Create Schema Provision file:
> {noformat}
> create schema (
> hire_date TIMESTAMP
> ) for table dfs.tmp.`employee_test`;
> {noformat}
> Run the query using Schema Provision file:
> {noformat}
> alter system set `store.table.use_schema_file` = true;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> *Expected result:*
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> *Actual result:*
> {color:#d04437}UserRemoteException : DATA_READ ERROR: Invalid format:
> "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
>
> org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
> Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
> Line 2
> Record 0
> Fragment 0:0
> [Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (DRILL-7320) DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision file
[
https://issues.apache.org/jira/browse/DRILL-7320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy closed DRILL-7320.
--
Resolution: Invalid
> DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision
> file
> --
>
> Key: DRILL-7320
> URL: https://issues.apache.org/jira/browse/DRILL-7320
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.16.0
>Reporter: Denys Ordynskiy
>Assignee: Arina Ielchiieva
>Priority: Major
>
> *Description:*
> Set CTAS output format to 'csvh':
> {noformat}
> set `store.format` = 'csvh';
> {noformat}
> Create csvh table with timestamp string:
> {noformat}
> drop table if exists dfs.tmp.`employee_test`;
> create table dfs.tmp.`employee_test` as select
> hire_date
> from cp.`employee.json` LIMIT 2;
> {noformat}
> Run the query without INFORMATION SCHEMA file using cast():
> {noformat}
> set `store.table.use_schema_file` = false;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> Create Schema Provision file:
> {noformat}
> create schema (
> hire_date TIMESTAMP
> ) for table dfs.tmp.`employee_test`;
> {noformat}
> Run the query using Schema Provision file:
> {noformat}
> alter system set `store.table.use_schema_file` = true;
> select
> cast(hire_date as TIMESTAMP) as hire_date
> from dfs.tmp.`employee_test`;
> {noformat}
> *Expected result:*
> |hire_date|
> |1994-12-01T00:00|
> |1994-12-01T00:00|
> *Actual result:*
> {color:#d04437}UserRemoteException : DATA_READ ERROR: Invalid format:
> "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
>
> org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
> Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
> Line 2
> Record 0
> Fragment 0:0
> [Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7320) DATA_READ ERROR when querying TIMESTAMP data from csvh using Schema Provision file
Denys Ordynskiy created DRILL-7320:
--
Summary: DATA_READ ERROR when querying TIMESTAMP data from csvh
using Schema Provision file
Key: DRILL-7320
URL: https://issues.apache.org/jira/browse/DRILL-7320
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.16.0
Reporter: Denys Ordynskiy
Assignee: Arina Ielchiieva
*Description:*
Set CTAS output format to 'csvh':
{noformat}
set `store.format` = 'csvh'
{noformat}
Create csvh table with timestamp string:
{noformat}
drop table if exists dfs.tmp.`employee_test`
create table dfs.tmp.`employee_test` as select
hire_date
from cp.`employee.json` LIMIT 2
{noformat}
Run the query without INFORMATION SCHEMA file using cast():
{noformat}
set `store.table.use_schema_file` = false
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`
{noformat}
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
Create Schema Provision file:
{noformat}
create schema (
hire_date TIMESTAMP
) for table dfs.tmp.`employee_test`
{noformat}
Run the query using Schema Provision file:
{noformat}
alter system set `store.table.use_schema_file` = true
select
cast(hire_date as TIMESTAMP) as hire_date
from dfs.tmp.`employee_test`
{noformat}
*Expected result:*
|hire_date|
|1994-12-01T00:00|
|1994-12-01T00:00|
*Actual result:*
{color:#d04437}UserRemoteException :DATA_READ ERROR: Invalid format:
"1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
org.apache.drill.common.exceptions.UserRemoteException: DATA_READ ERROR:
Invalid format: "1994-12-01 00:00:00.0" is malformed at " 00:00:00.0"
Line 2
Record 0
Fragment 0:0
[Error Id: 06965d3f-55ba-4c76-9c41-c4095f0c4445 on localhost:31010]{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-7302) Bump Apache Avro from 1.8.2 to 1.9.0
[ https://issues.apache.org/jira/browse/DRILL-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy reassigned DRILL-7302: -- Assignee: (was: Denys Ordynskiy) > Bump Apache Avro from 1.8.2 to 1.9.0 > > > Key: DRILL-7302 > URL: https://issues.apache.org/jira/browse/DRILL-7302 > Project: Apache Drill > Issue Type: Improvement >Reporter: Fokko Driesprong >Priority: Major > Labels: ready-to-commit > Fix For: 1.17.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (DRILL-7302) Bump Apache Avro from 1.8.2 to 1.9.0
[ https://issues.apache.org/jira/browse/DRILL-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy reassigned DRILL-7302: -- Assignee: Denys Ordynskiy > Bump Apache Avro from 1.8.2 to 1.9.0 > > > Key: DRILL-7302 > URL: https://issues.apache.org/jira/browse/DRILL-7302 > Project: Apache Drill > Issue Type: Improvement >Reporter: Fokko Driesprong >Assignee: Denys Ordynskiy >Priority: Major > Labels: ready-to-commit > Fix For: 1.17.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DRILL-7237) IllegalStateException in aggregation function 'single_value' when there is a varchar datatype in the subquery results
Denys Ordynskiy created DRILL-7237:
--
Summary: IllegalStateException in aggregation function
'single_value' when there is a varchar datatype in the subquery results
Key: DRILL-7237
URL: https://issues.apache.org/jira/browse/DRILL-7237
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0, 1.14.0
Reporter: Denys Ordynskiy
Assignee: Volodymyr Vysotskyi
Attachments: drillbit.log
*Description:*
The following issue can be reproduced on the EBF for the
[DRILL-7050|https://issues.apache.org/jira/browse/DRILL-7050].
_For the query with > 1 row in subquery results where the data type of these
results *is not varchar*:_
{noformat}
SELECT
e.full_name,
(
SELECT
ine.employee_id
FROM
cp.`employee.json` ine
WHERE
ine.position_id = e.position_id
) as empl_id
FROM
cp.`employee.json` e
LIMIT 20
{noformat}
_We have the following correct and informative error:_
{noformat}
Query Failed: An Error Occurred
org.apache.drill.common.exceptions.UserRemoteException: FUNCTION ERROR: Input
for single_value function has more than one row Fragment 0:0 [Error Id:
b770098f-b1c7-4647-9f41-9e986a0e47b7 on maprhost:31010]
{noformat}
_But when in the result set of the subquery we have *a varchar data type*:_
{noformat}
SELECT
e.full_name,
(
SELECT
ine.first_name
FROM
cp.`employee.json` ine
WHERE
ine.position_id = e.position_id
) as empl_id
FROM
cp.`employee.json` e
LIMIT 20
{noformat}
*Actual result:*
_Drill throws the following error:_
{noformat}
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalStateException: Workspace variable 'value' in aggregation function
'single_value' is not allowed to have variable length type. Fragment 0:0
Please, refer to logs for more information. [Error Id:
32325ba9-d2b3-4216-acf6-8e80dfe4a56a on maprhost:31010]
{noformat}
Log file is in the attachment "drillbit.log"
*Expected result:*
Drill should return the same informative error to any of a data types in the
subquery result set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy reassigned DRILL-7226:
--
Assignee: Bridget Bevens (was: Kunal Khatua)
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7226:
---
Labels: doc-impacting (was: )
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831214#comment-16831214
]
Denys Ordynskiy commented on DRILL-7226:
Successfully built and ran Drill in the embedded mode from the tarball.
The problem was with my archive manager 7Zip.
To solve this problem we can use built-in "tar" command on Windows 10.
For example in "cmd.exe" just run the following command:
tar -xzvf apache-drill-1.16.0-src.tar.gz
[~bbevens] could you please update documentation for Drill on Windows?
On this page - https://drill.apache.org/docs/installing-drill-on-windows/
It would be better to change this text:
"Download and install a utility for unzipping a tar.gz file, such as 7-zip."
To something like this:
"Use a built-in "tar" command in a default Windows CLI for unzipping a tar.gz
files.".
In the "Download and Install Drill" section, it would be better to change this
text:
"1. Download the latest version of Apache Drill here."
To this:
"1. Download zip or tar.gz archive with the latest version of Apache Drill."
Where "zip" is a link to a zip archive and "tar.gz" is a link to a tarball.
And this text:
"3. Unzip the GZ file using a third-party tool. If the tool you use does not
unzip the underlying TAR file as well as the GZ file, perform a second unzip to
extract the Drill software. The extraction process creates the installation
directory containing the Drill software."
To something like this:
"3. Extract data from a zip archive or unzip the tar.gz file using a built-in
"tar" command with options "-xzvf" and tarball filename, if tar.gz format was
chosen instead of zip. The extraction process creates the installation
directory containing the Drill software."
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830980#comment-16830980
]
Denys Ordynskiy edited comment on DRILL-7226 at 5/1/19 12:56 PM:
-
Maven version:
```
C:\Users\denysord88>mvn -version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T21:41:47+03:00)
Maven home: D:\mvn\bin\..
Java version: 1.8.0_201, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_201\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
```
Java version:
```
C:\Users\denysord88>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
```
Protoc is not installed.
There is the same error with ApacheRelease profile.
was (Author: denysord88):
Maven version:
```C:\Users\denysord88>mvn -version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T21:41:47+03:00)
Maven home: D:\mvn\bin\..
Java version: 1.8.0_201, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_201\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"```
Java version:
```C:\Users\denysord88>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)```
Protoc is not installed.
There is the same error with ApacheRelease profile.
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830980#comment-16830980
]
Denys Ordynskiy commented on DRILL-7226:
Maven version:
```C:\Users\denysord88>mvn -version
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3;
2018-10-24T21:41:47+03:00)
Maven home: D:\mvn\bin\..
Java version: 1.8.0_201, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_201\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"```
Java version:
```C:\Users\denysord88>java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)```
Protoc is not installed.
There is the same error with ApacheRelease profile.
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7226:
---
Attachment: 7z_version.png
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7226:
---
Attachment: broken_filenames.png
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: 7z_version.png, broken_filenames.png,
> tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16830976#comment-16830976
]
Denys Ordynskiy commented on DRILL-7226:
There is a problem with unpacking .tar.gz archive on Windows using 7Zip
archiver.
My version of 7Zip is in the attachment "7z_version.png"
Broken filenames after unpacking the .tar.gz archive are in the attachment
"broken_filenames.png"
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Fix For: 1.17.0
>
> Attachments: tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
[
https://issues.apache.org/jira/browse/DRILL-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy reassigned DRILL-7226:
--
Assignee: Kunal Khatua (was: Pritesh Maker)
> Compilation error on Windows when building from the release tarball sources
> ---
>
> Key: DRILL-7226
> URL: https://issues.apache.org/jira/browse/DRILL-7226
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Kunal Khatua
>Priority: Major
> Attachments: tarball_building.log
>
>
> *Description:*
> OS - Windows.
> Downloaded tarball with sources for the
> [1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
> or
> [1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
> Drill release.
> Extracted the sources.
> Built sources using the following command:
> {noformat}
> mvn clean install -DskipTests -Pmapr
> {noformat}
> *Expected result:*
> BUILD SUCCESS
> *Actual result:*
> {noformat}
> ...
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
> error: cannot find symbol
> symbol: class SerializedField
> location: class RecordBatchDef
> ...
> BUILD FAILURE
> {noformat}
> See "tarball_building.log"
> There are no errors when building sources on Windows from the GitHub release
> [branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7226) Compilation error on Windows when building from the release tarball sources
Denys Ordynskiy created DRILL-7226:
--
Summary: Compilation error on Windows when building from the
release tarball sources
Key: DRILL-7226
URL: https://issues.apache.org/jira/browse/DRILL-7226
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Denys Ordynskiy
Assignee: Pritesh Maker
Attachments: tarball_building.log
*Description:*
OS - Windows.
Downloaded tarball with sources for the
[1.15|http://home.apache.org/~vitalii/drill/releases/1.15.0/rc2/apache-drill-1.15.0-src.tar.gz]
or
[1.16|http://home.apache.org/~sorabh/drill/releases/1.16.0/rc2/apache-drill-1.16.0-src.tar.gz]
Drill release.
Extracted the sources.
Built sources using the following command:
{noformat}
mvn clean install -DskipTests -Pmapr
{noformat}
*Expected result:*
BUILD SUCCESS
*Actual result:*
{noformat}
...
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
D:\src\rc2\apache-drill-1.16.0-src\protocol\src\main\java\org\apache\drill\exec\proto\beans\RecordBatchDef.java:[53,17]
error: cannot find symbol
symbol: class SerializedField
location: class RecordBatchDef
...
BUILD FAILURE
{noformat}
See "tarball_building.log"
There are no errors when building sources on Windows from the GitHub release
[branch|https://github.com/sohami/drill/commits/drill-1.16.0].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-7184) Set the IDs for the unique HTML tags in the Drill Web UI
Denys Ordynskiy created DRILL-7184: -- Summary: Set the IDs for the unique HTML tags in the Drill Web UI Key: DRILL-7184 URL: https://issues.apache.org/jira/browse/DRILL-7184 Project: Apache Drill Issue Type: Task Reporter: Denys Ordynskiy Assignee: Denys Ordynskiy Selenium web pages automation requires identifiers on HTML tags. We need to find all HTML tags without ID's that are useful for Drill Web UI automation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-7079) Drill can't query views from the S3 storage when plain authentication is enabled
[
https://issues.apache.org/jira/browse/DRILL-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-7079:
---
Affects Version/s: 1.15.0
> Drill can't query views from the S3 storage when plain authentication is
> enabled
>
>
> Key: DRILL-7079
> URL: https://issues.apache.org/jira/browse/DRILL-7079
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Priority: Major
>
> Enable plain authentication in Drill.
> Create the view on the S3 storage:
> create view s3.tmp.`testview` as select * from cp.`employee.json` limit 20;
> Try to select data from the created view:
> select * from s3.tmp.`testview`;
> *Actual result*:
> {noformat}
> 2019-02-27 17:01:09,202 [Client-1] INFO
> o.a.d.j.i.DrillCursor$ResultsListener - [#4] Query failed:
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> IllegalArgumentException: A valid userName is expected
> Please, refer to logs for more information.
> [Error Id: 2271c3aa-6d09-4b51-a585-0e0e954b46eb on maprhost:31010]
> at
> org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(QueryResultHandler.java:123)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:422)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:96)
> [drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:273)
> [drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:243)
> [drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:287)
> [netty-handler-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:312)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:286)
> [netty-codec-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
> io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
> [netty-transport-4.0.48.Final.jar:4.0.48.Final]
> at
>
[jira] [Created] (DRILL-7079) Drill can't query views from the S3 storage when plain authentication is enabled
Denys Ordynskiy created DRILL-7079:
--
Summary: Drill can't query views from the S3 storage when plain
authentication is enabled
Key: DRILL-7079
URL: https://issues.apache.org/jira/browse/DRILL-7079
Project: Apache Drill
Issue Type: Bug
Reporter: Denys Ordynskiy
Enable plain authentication in Drill.
Create the view on the S3 storage:
create view s3.tmp.`testview` as select * from cp.`employee.json` limit 20;
Try to select data from the created view:
select * from s3.tmp.`testview`;
*Actual result*:
{noformat}
2019-02-27 17:01:09,202 [Client-1] INFO o.a.d.j.i.DrillCursor$ResultsListener
- [#4] Query failed:
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalArgumentException: A valid userName is expected
Please, refer to logs for more information.
[Error Id: 2271c3aa-6d09-4b51-a585-0e0e954b46eb on maprhost:31010]
at
org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(QueryResultHandler.java:123)
[drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
at
org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:422)
[drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
at org.apache.drill.exec.rpc.user.UserClient.handle(UserClient.java:96)
[drill-java-exec-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
at
org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:273)
[drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
at
org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:243)
[drill-rpc-1.16.0-SNAPSHOT.jar:1.16.0-SNAPSHOT]
at
io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
[netty-codec-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:287)
[netty-handler-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
[netty-codec-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:312)
[netty-codec-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:286)
[netty-codec-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:356)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:342)
[netty-transport-4.0.48.Final.jar:4.0.48.Final]
at
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:335)
[jira] [Commented] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755897#comment-16755897
]
Denys Ordynskiy commented on DRILL-6911:
Thanks [~bbevens] for the documentation update.
I think this "*Note: ...*" also should be deleted because Drill doesn't see the
Hadoop core-site.xml file.
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6995) Count() function is not working with columns alias
Denys Ordynskiy created DRILL-6995:
--
Summary: Count() function is not working with columns alias
Key: DRILL-6995
URL: https://issues.apache.org/jira/browse/DRILL-6995
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Denys Ordynskiy
The query works correctly if I use column name in the count() function:
{code:java}
select department_id c from cp.`employee.json` group by c having
count(department_id) > 1
{code}
|c|
|1|
|2|
|3|
|11|
|5|
|4|
|19|
|14|
|15|
|16|
But when I set column alias "c" in the count() function, Drill returns *an
empty result set*:
{code:java}
select department_id c from cp.`employee.json` group by c having count(c) > 1
{code}
|c|
| |
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6783) CAST string literal as INTERVAL MONTH/YEAR works inconsistently when selecting from a table with multiple rows
[
https://issues.apache.org/jira/browse/DRILL-6783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16746137#comment-16746137
]
Denys Ordynskiy commented on DRILL-6783:
Tested with Drill version 1.16.0-SNAPSHOT (commit
172dc7cb4c3323e9650db2bf7fe1eab76c2fbbe1).
Cases verified:
- casting string month interval literal as "interval month";
- casting string month interval literal as "interval year";
- casting string month interval literal as "interval day";
- casting string day interval literal as "interval month";
- casting string day interval literal as "interval day".
> CAST string literal as INTERVAL MONTH/YEAR works inconsistently when
> selecting from a table with multiple rows
> --
>
> Key: DRILL-6783
> URL: https://issues.apache.org/jira/browse/DRILL-6783
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Bohdan Kazydub
>Assignee: Bohdan Kazydub
>Priority: Critical
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> Casting string literal as INTERVAL MONTH or INTERVAL YEAR produces different
> values for each row (actually, with period of 4) when selecting data from
> table with more than one row.
> For example:
> {code}
> 0: jdbc:drill:zk=local> select cast('P314M' as interval month) from
> cp.`employee.json` limit 10;
> +--+
> | EXPR$0 |
> +--+
> | 26 years 2 months |
> | 81089877 years 5 months |
> | 1714858 years 8 months |
> | 6698 years 8 months |
> | 26 years 2 months |
> | 81089877 years 5 months |
> | 1714858 years 8 months |
> | 6698 years 8 months |
> | 26 years 2 months |
> | 81089877 years 5 months |
> +--+
> 10 rows selected (0.186 seconds)
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6894) CTAS and CTTAS are not working on S3 storage when cache is disabled
[
https://issues.apache.org/jira/browse/DRILL-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737522#comment-16737522
]
Denys Ordynskiy commented on DRILL-6894:
Successfully tested on S3 for CTAS and CTTAS
> CTAS and CTTAS are not working on S3 storage when cache is disabled
> ---
>
> Key: DRILL-6894
> URL: https://issues.apache.org/jira/browse/DRILL-6894
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
> Attachments: CTAS_drillbit.log, CTAS_drillbit_queries.json,
> CTAS_sqlline.log, CTTAS_drillbit.log, CTTAS_drillbit_queries.json,
> CTTAS_sqlline.log, s3.json
>
>
> When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the
> config section and Drill is restarted,
> CTAS and CTTAS queries throwing error in Sqlline:
> *create temporary table s3.tmp.`cttastblwithcache2` as select * from
> cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
> (state=,code=0){color}
> *create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
> (state=,code=0){color}
> Logs and my storage plugin are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6931) Drill "SHOW FILES" command duplicates empty S3 folders as subfolders
[ https://issues.apache.org/jira/browse/DRILL-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16737491#comment-16737491 ] Denys Ordynskiy commented on DRILL-6931: Successfully tested on Drill Explorer and Sqlline for storages: - MapRFS - S3 - FileSystem > Drill "SHOW FILES" command duplicates empty S3 folders as subfolders > > > Key: DRILL-6931 > URL: https://issues.apache.org/jira/browse/DRILL-6931 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Denys Ordynskiy >Assignee: Arina Ielchiieva >Priority: Major > Labels: ready-to-commit > Fix For: 1.16.0 > > > *Description:* > If folder was created by pressing "+ Create folder" button on the S3 > management console, > Drill "SHOW FILES" command showing in this folder another subfolder with the > same name. > But this subfolder doesn't exist. > *Example:* > - login to the S3 management console; > - open your bucket `some_bucket`; > - create an empty folder `my_test_folder` by pressing "+ Create folder" > button; > - run Drill and open sqlline client; > - exec query "show files in s3.tmp.`my_test_folder`;" > *Actual result:* > |name|isDirectory|isFile|length|owner|group|permissions|accessTime|modificationTime| > |my_test_folder|true|false|0| | |rwxrwxrwx|1970-01-01 03:00:00.0|1970-01-01 > 03:00:00.0| > 1 row selected (1.318 seconds) > *Expected result:* > an empty result set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-6814: --- Attachment: S3investigate.txt > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > Attachments: S3investigate.txt > > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735852#comment-16735852 ] Denys Ordynskiy commented on DRILL-6814: Comparison of the response time for querying tables on S3 and MapRFS storage. Drill setups were on my local virtual machine "KVM" and EC2 instance. *Response time for querying big parquet tables on S3 is not longer then on MapRFS storage.* Querying text files: KVM S3 avg time - 369.22 seconds KVM MapRFS avg time - 74.54 seconds EC2 S3 avg time - 102.94 seconds EC2 MapRFS avg time - 94.65 seconds Querying parquet files: KVM S3 avg time - 356.36 seconds KVM MapRFS avg time - 79.54 seconds EC2 S3 avg time - 114.47 seconds EC2 MapRFS avg time - 105.46 seconds | File format | EC2 MapRFS | EC2 S3 | KVM MapRFS | KVM S3 | | CSV | 94.65 seconds | 102.94 seconds | 74.54 seconds | 369.22 seconds | | PARQUET | 105.46 seconds | 114.47 seconds | 79.54 seconds | 356.36 seconds | More details, profiles, in the attachment "S3investigate.txt" > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735855#comment-16735855 ] Denys Ordynskiy edited comment on DRILL-6814 at 1/7/19 2:05 PM: Tests from the drill-test-framework for Drill fragments were passed. Drill successfully created major and minor fragments for a S3 storage. was (Author: denysord88): Tests from the drill-test-framework for Drill fragments were passed. Drill successfully creating major and minor fragments for a S3 storage. > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > Attachments: S3investigate.txt > > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735855#comment-16735855 ] Denys Ordynskiy commented on DRILL-6814: Tests from the drill-test-framework for Drill fragments were passed. Drill successfully creating major and minor fragments for a S3 storage. > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > Attachments: S3investigate.txt > > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735851#comment-16735851 ] Denys Ordynskiy commented on DRILL-6814: Successfully tested Drill profiles with Partition Pruning on S3 storage. > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6814) Query performance on S3 files
[ https://issues.apache.org/jira/browse/DRILL-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16735848#comment-16735848 ] Denys Ordynskiy commented on DRILL-6814: Successfully passed on S3 tests "Fltr_Pshdwn*.sql" from [drill-test-framework|https://github.com/mapr/drill-test-framework] in folder [framework/resources/Functional/filter/pushdown/plan/regex|https://github.com/mapr/drill-test-framework/tree/master/framework/resources/Functional/filter/pushdown/plan/regex] for Transitive Closure and Filter Pushdown. > Query performance on S3 files > - > > Key: DRILL-6814 > URL: https://issues.apache.org/jira/browse/DRILL-6814 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - Other >Affects Versions: 1.14.0 > Environment: Amazon EC2 instances- > 4 Linux Redhat machines -version 7.5 > RAM- 32GB >Reporter: Ashish Shukla >Assignee: Denys Ordynskiy >Priority: Major > > I have installed 4 Node drill cluster on Amazon EC2 and trying to execute a > simple count on one Amazon S3 file. File type is CSV and size is approx- 14GB. > The query returns expected count after the execution of approx 30 minutes. > If we keep the same file in hdfs or create a table in postgres, execution > time is relatively very less (approx 2-3 minutes). > Is it normal behavior or something can be done for S3 files to make > execution time comparable ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6932) Drill can't submit Physical plan returned by submitting Logical plan
[
https://issues.apache.org/jira/browse/DRILL-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-6932:
---
Summary: Drill can't submit Physical plan returned by submitting Logical
plan (was: Drill can't submit Physical plan, returned by submitting Logical
plan)
> Drill can't submit Physical plan returned by submitting Logical plan
>
>
> Key: DRILL-6932
> URL: https://issues.apache.org/jira/browse/DRILL-6932
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Priority: Major
>
> *Description:*
> Drill WebUI allows to submit Logical plan and returns 2 types of a result:
> - "resultMode" : "EXEC" - to get query result set
> - "resultMode" : "PHYSICAL" - to get Physical plan of the query
> If I get Physical plan by submiting Logical plan with "resultMode" :
> "PHYSICAL",
> this Physical plan throws an error after submiting it.
> *Steps to reproduce issue in a Drill WebUI:*
> - get Logical plan by running query "EXPLAIN PLAN WITHOUT IMPLEMENTATION FOR
> SELECT * FROM cp.`employee.json` LIMIT 2";
> - change "resultMode" from "LOGICAL" to "PHYSICAL";
> - select "Query Type" - "LOGICAL" and submit Logical plan and get Physical
> plan;
> - select "Query Type" - "PHYSICAL" and submit Physical plan;
> *Actual result:*
> {color:#d04437}*Query Failed: An Error Occurred*
> org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
> IllegalStateException: Already had POJO for id (java.lang.Integer)
> [[ObjectId: key=0,
> type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator,
> scope=java.lang.Object]] Please, refer to logs for more information. [Error
> Id: f7a2422f-55e8-4478-9e22-1008175ce9b6 on maprhost:31010]{color}
> *Expected result:*
> result set for the original query "SELECT * FROM cp.`employee.json` LIMIT 2"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6932) Drill can't submit Physical plan, returned by submitting Logical plan
Denys Ordynskiy created DRILL-6932:
--
Summary: Drill can't submit Physical plan, returned by submitting
Logical plan
Key: DRILL-6932
URL: https://issues.apache.org/jira/browse/DRILL-6932
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Denys Ordynskiy
*Description:*
Drill WebUI allows to submit Logical plan and returns 2 types of a result:
- "resultMode" : "EXEC" - to get query result set
- "resultMode" : "PHYSICAL" - to get Physical plan of the query
If I get Physical plan by submiting Logical plan with "resultMode" : "PHYSICAL",
this Physical plan throws an error after submiting it.
*Steps to reproduce issue in a Drill WebUI:*
- get Logical plan by running query "EXPLAIN PLAN WITHOUT IMPLEMENTATION FOR
SELECT * FROM cp.`employee.json` LIMIT 2";
- change "resultMode" from "LOGICAL" to "PHYSICAL";
- select "Query Type" - "LOGICAL" and submit Logical plan and get Physical plan;
- select "Query Type" - "PHYSICAL" and submit Physical plan;
*Actual result:*
{color:#d04437}*Query Failed: An Error Occurred*
org.apache.drill.common.exceptions.UserRemoteException: SYSTEM ERROR:
IllegalStateException: Already had POJO for id (java.lang.Integer) [[ObjectId:
key=0,
type=com.fasterxml.jackson.databind.deser.impl.PropertyBasedObjectIdGenerator,
scope=java.lang.Object]] Please, refer to logs for more information. [Error Id:
f7a2422f-55e8-4478-9e22-1008175ce9b6 on maprhost:31010]{color}
*Expected result:*
result set for the original query "SELECT * FROM cp.`employee.json` LIMIT 2"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6931) Drill "SHOW FILES" command duplicates empty S3 folders as subfolders
Denys Ordynskiy created DRILL-6931: -- Summary: Drill "SHOW FILES" command duplicates empty S3 folders as subfolders Key: DRILL-6931 URL: https://issues.apache.org/jira/browse/DRILL-6931 Project: Apache Drill Issue Type: Bug Affects Versions: 1.14.0 Reporter: Denys Ordynskiy *Description:* If folder was created by pressing "+ Create folder" button on the S3 management console, Drill "SHOW FILES" command showing in this folder another subfolder with the same name. But this folder doesn't exist. *Example:* - login to the S3 management console; - open your bucket `some_bucket`; - create an empty folder `my_test_folder` by pressing "+ Create folder" button; - run Drill and open sqlline client; - exec query "show files in s3.tmp.`my_test_folder`;" *Actual result:* | name | isDirectory | isFile | length | owner | group | permissions | accessTime |modificationTime| | my_test_folder | true | false | 0 ||| rwxrwxrwx| 1970-01-01 03:00:00.0 | 1970-01-01 03:00:00.0 | 1 row selected (1.318 seconds) *Expected result:* an empty result set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DRILL-6931) Drill "SHOW FILES" command duplicates empty S3 folders as subfolders
[ https://issues.apache.org/jira/browse/DRILL-6931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denys Ordynskiy updated DRILL-6931: --- Description: *Description:* If folder was created by pressing "+ Create folder" button on the S3 management console, Drill "SHOW FILES" command showing in this folder another subfolder with the same name. But this subfolder doesn't exist. *Example:* - login to the S3 management console; - open your bucket `some_bucket`; - create an empty folder `my_test_folder` by pressing "+ Create folder" button; - run Drill and open sqlline client; - exec query "show files in s3.tmp.`my_test_folder`;" *Actual result:* |name|isDirectory|isFile|length|owner|group|permissions|accessTime|modificationTime| |my_test_folder|true|false|0| | |rwxrwxrwx|1970-01-01 03:00:00.0|1970-01-01 03:00:00.0| 1 row selected (1.318 seconds) *Expected result:* an empty result set. was: *Description:* If folder was created by pressing "+ Create folder" button on the S3 management console, Drill "SHOW FILES" command showing in this folder another subfolder with the same name. But this folder doesn't exist. *Example:* - login to the S3 management console; - open your bucket `some_bucket`; - create an empty folder `my_test_folder` by pressing "+ Create folder" button; - run Drill and open sqlline client; - exec query "show files in s3.tmp.`my_test_folder`;" *Actual result:* | name | isDirectory | isFile | length | owner | group | permissions | accessTime |modificationTime| | my_test_folder | true | false | 0 ||| rwxrwxrwx| 1970-01-01 03:00:00.0 | 1970-01-01 03:00:00.0 | 1 row selected (1.318 seconds) *Expected result:* an empty result set. > Drill "SHOW FILES" command duplicates empty S3 folders as subfolders > > > Key: DRILL-6931 > URL: https://issues.apache.org/jira/browse/DRILL-6931 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 1.14.0 >Reporter: Denys Ordynskiy >Priority: Major > > *Description:* > If folder was created by pressing "+ Create folder" button on the S3 > management console, > Drill "SHOW FILES" command showing in this folder another subfolder with the > same name. > But this subfolder doesn't exist. > *Example:* > - login to the S3 management console; > - open your bucket `some_bucket`; > - create an empty folder `my_test_folder` by pressing "+ Create folder" > button; > - run Drill and open sqlline client; > - exec query "show files in s3.tmp.`my_test_folder`;" > *Actual result:* > |name|isDirectory|isFile|length|owner|group|permissions|accessTime|modificationTime| > |my_test_folder|true|false|0| | |rwxrwxrwx|1970-01-01 03:00:00.0|1970-01-01 > 03:00:00.0| > 1 row selected (1.318 seconds) > *Expected result:* > an empty result set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6919) Error: cannot find symbol in class ServerSocketUtil
[
https://issues.apache.org/jira/browse/DRILL-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16728332#comment-16728332
]
Denys Ordynskiy commented on DRILL-6919:
Successfully tested with mapr profile.
> Error: cannot find symbol in class ServerSocketUtil
> ---
>
> Key: DRILL-6919
> URL: https://issues.apache.org/jira/browse/DRILL-6919
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Volodymyr Vysotskyi
>Priority: Blocker
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> Compilation error when building Drill with mapr profile:
> {color:#d04437}[ERROR]
> /home/mapr/git_repo/drill/exec/java-exec/src/test/java/org/apache/drill/test/TestGracefulShutdown.java:[24,28]
> error: cannot find symbol
> symbol: class ServerSocketUtil
> location: package org.apache.hadoop.net{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6919) Error: cannot find symbol in class ServerSocketUtil
Denys Ordynskiy created DRILL-6919:
--
Summary: Error: cannot find symbol in class ServerSocketUtil
Key: DRILL-6919
URL: https://issues.apache.org/jira/browse/DRILL-6919
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Denys Ordynskiy
Assignee: Volodymyr Vysotskyi
Compilation error when building Drill with mapr profile:
{color:#d04437}[ERROR]
/home/mapr/git_repo/drill/exec/java-exec/src/test/java/org/apache/drill/test/TestGracefulShutdown.java:[24,28]
error: cannot find symbol
symbol: class ServerSocketUtil
location: package org.apache.hadoop.net{color}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6662) Access AWS access key ID and secret access key using Credential Provider API for S3 storage plugin
[ https://issues.apache.org/jira/browse/DRILL-6662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724177#comment-16724177 ] Denys Ordynskiy commented on DRILL-6662: Successfully tested on Drill storage plugin and Drill core-site.xml > Access AWS access key ID and secret access key using Credential Provider API > for S3 storage plugin > -- > > Key: DRILL-6662 > URL: https://issues.apache.org/jira/browse/DRILL-6662 > Project: Apache Drill > Issue Type: Improvement >Reporter: Bohdan Kazydub >Assignee: Bohdan Kazydub >Priority: Major > Labels: doc-impacting, ready-to-commit > Fix For: 1.15.0 > > > Hadoop provides [CredentialProvider > API|[https://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/CredentialProviderAPI.html]] > which allows passwords and other sensitive secrets to be stored in an > external provider rather than in configuration files in plaintext. > Currently S3 storage plugin is accessing passwords, namely > 'fs.s3a.access.key' and 'fs.s3a.secret.key', stored in clear text in > Configuration with get() method. To give users an ability to remove clear > text passwords for S3 from configuration files Configuration.getPassword() > method should be used, given they configure > 'hadoop.security.credential.provider.path' property which points to a file > containing encrypted passwords instead of configuring two aforementioned > properties. > By using this approach, credential providers will be checked first and if the > secret is not provided or providers are not configured there will be a > fallback to secrets configured in clear text (unless > 'hadoop.security.credential.clear-text-fallback' is configured to be > "false"), thus making new change backwards-compatible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
[
https://issues.apache.org/jira/browse/DRILL-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724171#comment-16724171
]
Denys Ordynskiy commented on DRILL-6911:
cc [~KazydubB]
> Documentation issue - Hadoop core-site.xml is not supported by Drill to read
> S3 credentials
> ---
>
> Key: DRILL-6911
> URL: https://issues.apache.org/jira/browse/DRILL-6911
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bridget Bevens
>Priority: Major
> Labels: doc-impacting
> Fix For: 1.16.0
>
>
> In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
> Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
> credentials in Drill:
> - storage plugin;
> - Drill-specific core-site.xml;
> - existing S3 configuration for Hadoop.
> Third item is not supported by Drill. Hadoop core-site.xml config file may
> contains S3 credentials, but Drill doesn't read any S3 parameters directly
> from Hadoop config file.
> Third item
> {code:java}
> In a Hadoop environment, you can use the existing S3 configuration for
> Hadoop. The AWS credentials should already be defined. All you need to do is
> configure the S3 storage plugin.
> {code}
> should be removed from the document
> https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6911) Documentation issue - Hadoop core-site.xml is not supported by Drill to read S3 credentials
Denys Ordynskiy created DRILL-6911:
--
Summary: Documentation issue - Hadoop core-site.xml is not
supported by Drill to read S3 credentials
Key: DRILL-6911
URL: https://issues.apache.org/jira/browse/DRILL-6911
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.14.0
Reporter: Denys Ordynskiy
Assignee: Bridget Bevens
In the Drill S3 documentation https://drill.apache.org/docs/s3-storage-plugin/
Section "Providing AWS Credentials" describing 3 ways to setup AWS S3
credentials in Drill:
- storage plugin;
- Drill-specific core-site.xml;
- existing S3 configuration for Hadoop.
Third item is not supported by Drill. Hadoop core-site.xml config file may
contains S3 credentials, but Drill doesn't read any S3 parameters directly from
Hadoop config file.
Third item
{code:java}
In a Hadoop environment, you can use the existing S3 configuration for Hadoop.
The AWS credentials should already be defined. All you need to do is configure
the S3 storage plugin.
{code}
should be removed from the document
https://drill.apache.org/docs/s3-storage-plugin/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723859#comment-16723859
]
Denys Ordynskiy commented on DRILL-6875:
When I actualized time on my virtual machine, bug was fixed.
Successfully log in the attachment "not_a_bug_drillbit.log"
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6875) Drill doesn't try to update connection for S3 after session expired
[
https://issues.apache.org/jira/browse/DRILL-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-6875:
---
Attachment: not_a_bug_drillbit.log
> Drill doesn't try to update connection for S3 after session expired
> ---
>
> Key: DRILL-6875
> URL: https://issues.apache.org/jira/browse/DRILL-6875
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Fix For: 1.16.0
>
> Attachments: drillbit.log, not_a_bug_drillbit.log
>
>
> *Steps to reproduce:*
> - Drill has S3 storage plugin.
> - Open sqlline and run query to S3.
> - Leave sqlline opened for more than 12 hours.
> - In opened sqlline run query to S3.
> *Expected result:*
> Drill should update authorization session and successfully execute query.
> *Actual result:*
> Sqlline returns an error:
> *{color:#d04437}Error: VALIDATION ERROR: Forbidden (Service: Amazon S3;
> Status Code: 403; Error Code: 403 Forbidden; Request ID: 4A94DD331A035625; S3
> Extended Request ID:
> uy94YdRpQ3ZriCz9xbnDi0yinB4O9kGrH7XPAURhjh8WZoxsbawojQA6v7mfvu920yOYbEI5WP8=)
> [Error Id: 4b44a83b-0e47-45a4-92e3-75f94f5a70cb on maprhost:31010]
> (state=,code=0){color}*
> *Reopening sqlline doesn't help to get S3 access.*
> *Access problem can be solved only by restarting Drill.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (DRILL-6894) CTAS and CTTAS are not working on S3 storage when cache is disabled
[
https://issues.apache.org/jira/browse/DRILL-6894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denys Ordynskiy updated DRILL-6894:
---
Description:
When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the config
section and Drill is restarted,
CTAS and CTTAS queries throwing error in Sqlline:
*create temporary table s3.tmp.`cttastblwithcache2` as select * from
cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
(state=,code=0){color}
*create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
(state=,code=0){color}
Logs and my storage plugin are in the attachments.
was:
When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the config
section,
CTAS and CTTAS queries throwing error in Sqlline:
*create temporary table s3.tmp.`cttastblwithcache2` as select * from
cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
(state=,code=0){color}
*create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
(state=,code=0){color}
Logs and my storage plugin are in the attachments.
> CTAS and CTTAS are not working on S3 storage when cache is disabled
> ---
>
> Key: DRILL-6894
> URL: https://issues.apache.org/jira/browse/DRILL-6894
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Attachments: CTAS_drillbit.log, CTAS_drillbit_queries.json,
> CTAS_sqlline.log, CTTAS_drillbit.log, CTTAS_drillbit_queries.json,
> CTTAS_sqlline.log, s3.json
>
>
> When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the
> config section and Drill is restarted,
> CTAS and CTTAS queries throwing error in Sqlline:
> *create temporary table s3.tmp.`cttastblwithcache2` as select * from
> cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
> (state=,code=0){color}
> *create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
> {color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
> credentials from any provider in the chain
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
> (state=,code=0){color}
> Logs and my storage plugin are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (DRILL-6894) CTAS and CTTAS are not working on S3 storage when cache is disabled
Denys Ordynskiy created DRILL-6894:
--
Summary: CTAS and CTTAS are not working on S3 storage when cache
is disabled
Key: DRILL-6894
URL: https://issues.apache.org/jira/browse/DRILL-6894
Project: Apache Drill
Issue Type: Bug
Affects Versions: 1.15.0
Reporter: Denys Ordynskiy
Attachments: CTAS_drillbit.log, CTAS_drillbit_queries.json,
CTAS_sqlline.log, CTTAS_drillbit.log, CTTAS_drillbit_queries.json,
CTTAS_sqlline.log, s3.json
When S3 storage plugin option "fs.s3a.impl.disable.cache" is true in the config
section,
CTAS and CTTAS queries throwing error in Sqlline:
*create temporary table s3.tmp.`cttastblwithcache2` as select * from
cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 8e386b68-d4fb-4cc6-ba1c-fb41ae0cc9ed on maprhost:31010]
(state=,code=0){color}
*create table s3.tmp.`ctastblwithcache` as select * from cp.`employee.json`;*
{color:#d04437}Error: SYSTEM ERROR: SdkClientException: Unable to load AWS
credentials from any provider in the chain
Fragment 0:0
Please, refer to logs for more information.
[Error Id: 4346d300-44be-4f17-90b6-4f3a0db0a148 on maprhost:31010]
(state=,code=0){color}
Logs and my storage plugin are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6874) CTAS from json to parquet is not working on S3 storage
[
https://issues.apache.org/jira/browse/DRILL-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715206#comment-16715206
]
Denys Ordynskiy commented on DRILL-6874:
Successfully tested on parquet, json and csv files in CTAS.
> CTAS from json to parquet is not working on S3 storage
> --
>
> Key: DRILL-6874
> URL: https://issues.apache.org/jira/browse/DRILL-6874
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.15.0
>
> Attachments: ctasjsontoparquet.zip, drillbit.log,
> drillbit_queries.json, s3src.json, sqlline.log
>
>
> Json file "s3src.json" was uploaded to the s3 storage.
> Query from Json works fine:
> select * from s3.tmp.`s3src.json`;
> | id | first_name | last_name |
> | 1 | first_name1 | last_name1 |
> | 2 | first_name2 | last_name2 |
> | 3 | first_name3 | last_name3 |
> | 4 | first_name4 | last_name4 |
> | 5 | first_name5 | last_name5 |
> 5 rows selected (2.803 seconds)
> CTAS from this json file returns successfully result:
> create table s3.tmp.`ctasjsontoparquet` as select * from s3.tmp.`s3src.json`;
> | Fragment | Number of records written |
> | 0_0 | 5 |
> 1 row selected (9.264 seconds)
> *Query from the created parquet table {color:#d04437}throws an error:{color}*
> select * from s3.tmp.`ctasjsontoparquet`;
> {code:java}
> Error: INTERNAL_ERROR ERROR: Error in parquet record reader.
> Message: Failure in setting up reader
> Parquet Metadata: ParquetMetaData{FileMetaData{schema: message root {
> optional int64 id;
> optional binary first_name (UTF8);
> optional binary last_name (UTF8);
> }
> , metadata: {drill-writer.version=2, drill.version=1.15.0-SNAPSHOT}}, blocks:
> [BlockMetaData{5, 360 [ColumnMetaData{UNCOMPRESSED [id] optional int64 id
> [BIT_PACKED, RLE, PLAIN], 4}, ColumnMetaData{UNCOMPRESSED [first_name]
> optional binary first_name (UTF8) [BIT_PACKED, RLE, PLAIN], 111},
> ColumnMetaData{UNCOMPRESSED [last_name] optional binary last_name (UTF8)
> [BIT_PACKED, RLE, PLAIN], 241}]}]}
> Fragment 0:0
> Please, refer to logs for more information.
> [Error Id: 885723e4-8385-4fb0-87dd-c08b0570db95 on maprhost:31010]
> (state=,code=0)
> {code}
> The same CTAS query works fine on MapRFS and FileSystem storages.
> Log files, json file and created parquet file from S3 are in the attachments.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6863) Drop table is not working if path within workspace starts with '/'
[
https://issues.apache.org/jira/browse/DRILL-6863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707241#comment-16707241
]
Denys Ordynskiy commented on DRILL-6863:
Successfully tested on S3, MapRFS and FileSystem storage plugins on CTAS and
CTTAS.
> Drop table is not working if path within workspace starts with '/'
> --
>
> Key: DRILL-6863
> URL: https://issues.apache.org/jira/browse/DRILL-6863
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.14.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Major
> Labels: ready-to-commit
> Fix For: 1.15.0
>
>
> Drill works incorrectly if path to the table within workspace starts with '/'
> Request "drop table s3.tmp.`drill/transitive_closure/tab1`" works fine,
> but if I add '/' in the begining of the tables path "drop table
> s3.tmp.`{color:#d04437}/{color}drill/transitive_closure/tab1`", Drill is
> trying to find table in the root directory but not in workspace path.
> *Actual result:*
> Drill returns successfully response
> "Table [/drill/transitive_closure/tab1] dropped"
> but table was not dropped.
>
> *Expected result:*
> Table was droped.
> Bug can be reproduced on S3 and DFS storages. On FileSystem storage Drill
> successfully returns error message if "drop table" query starts with '/' in
> table path.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DRILL-6869) Drill allows to create views outside workspace
[
https://issues.apache.org/jira/browse/DRILL-6869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704776#comment-16704776
]
Denys Ordynskiy commented on DRILL-6869:
Successfully tested on S3, MapRFS and FileSystem storage plugins.
> Drill allows to create views outside workspace
> --
>
> Key: DRILL-6869
> URL: https://issues.apache.org/jira/browse/DRILL-6869
> Project: Apache Drill
> Issue Type: Bug
>Affects Versions: 1.15.0
>Reporter: Denys Ordynskiy
>Assignee: Bohdan Kazydub
>Priority: Minor
> Fix For: 1.16.0
>
> Attachments: Amazon_S3_FS_stor_plugin.json,
> FileSystem_stor_plugin.json, MapR_FS_stor_plugin.json
>
>
> Parameter 'allowAccessOutsideWorkspace' is false for tested workspaces.
> On MaprFS and S3 storages Drill allows to create views outside workspace.
> *Example on MapRFS:*
> create view dfs.tmp.`{color:#d04437}*/*{color}testbugonmfs` as SELECT * FROM
> cp.`employee.json` LIMIT 20;
> |ok|summary|
> |true|View '/testbugonmfs' *created successfully in 'dfs.tmp' schema*|
> 1 row selected (0.93 seconds)
> The file "testbugonmfs.view.drill" was *created* in the *root "/" folder,*
> but not in used workspace "/tmp" folder.
> Select query works with root "/" folder {color:#d04437}*outside*{color} the
> dfs.tmp workspace:
> select count * from dfs.tmp.`{color:#d04437}*/*{color}testbugonmfs`;
> |EXPR$0|
> |20|
> 1 row selected (1.813 seconds)
>
> *Example on S3*:
> create view s3.tmp.`{color:#d04437}*/*{color}testbugons3` as SELECT * FROM
> cp.`employee.json` LIMIT 20;
> |ok|summary|
> |true|View '/testbugons3' *created successfully in 's3.tmp' schema*|
> 1 row selected (3.455 seconds)
>
> The file "testbugons3.view.drill" was *created* in the *root "/" bucket
> folder*, but not in used workspace "/tmp" folder.
> Select query also works with root "/" bucket folder
> {color:#d04437}*outside*{color} the s3.tmp workspace:
> select count * from s3.tmp.`/testbugons3`;
> |EXPR$0|
> |20|
> 1 row selected (3.209 seconds)
>
> *Expected result:*
> View should be created within workspace
> On FileSystem storage plugin Drill doesn't allow to create views outside
> workspace.
> Query "create view dfs.tmp.`/testbugonfs` as SELECT * FROM
> cp.`employee.json` LIMIT 20;"
> Returns an error: "{color:#d04437}Error: SYSTEM ERROR:
> FileNotFoundException: /testbugonfs.view.drill (Permission denied){color}".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
