Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD57410D21 for ; Tue, 2 Dec 2014 19:20:12 +0000 (UTC) Received: (qmail 68023 invoked by uid 500); 2 Dec 2014 19:20:12 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 67993 invoked by uid 500); 2 Dec 2014 19:20:12 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 67982 invoked by uid 99); 2 Dec 2014 19:20:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 19:20:12 +0000 Date: Tue, 2 Dec 2014 19:20:12 +0000 (UTC) From: "Abhishek Girish (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-1794) Can not make files with extension "log" to be recognized as json format? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231954#comment-14231954 ] Abhishek Girish commented on DRILL-1794: ---------------------------------------- I tried this out on my setup (doesn't have the patch) and I'm unable to add a custom format for json, with an extension specified. I looked at the patch (but haven't tried it out as yet) and it should fix the issue. > Can not make files with extension "log" to be recognized as json format? > ------------------------------------------------------------------------ > > Key: DRILL-1794 > URL: https://issues.apache.org/jira/browse/DRILL-1794 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Data Types > Affects Versions: 0.6.0 > Environment: 0.6R3 > Reporter: Hao Zhu > > If we want to use ".log" as the file extension, and also want it to be recognized as json format, I tried to use below storage engine , but failed to read the .log file.. > {code} > "formats": { > "log": { > "type": "json" > }, > "csv": { > "type": "text", > "extensions": [ > "csv" > ], > "delimiter": "," > } > } > {code} > {code} > 0: jdbc:drill:zk=n1a:5181,n2a:5181,n3a:5181> select * from logtest.`test.json`; > +------------+------------+------------+------------+ > | field1 | field2 | field3 | field4 | > +------------+------------+------------+------------+ > | data1 | 100.0 | more data1 | 123.001 | > +------------+------------+------------+------------+ > 1 row selected (0.159 seconds) > 0: jdbc:drill:zk=n1a:5181,n2a:5181,n3a:5181> select * from logtest.`test.log`; > Query failed: Failure while validating sql : org.eigenbase.util.EigenbaseContextException: From line 1, column 16 to line 1, column 22: Table 'logtest.test.log' not found > Error: exception while executing query: Failure while executing query. (state=,code=0) > {code} > Do we support above requirement? > If so, what is the storage plugin text? -- This message was sent by Atlassian JIRA (v6.3.4#6332)