[jira] [Updated] (DRILL-1540) Provide a fallback data format in case Drill is unable to determine one

["Hanifi Gunes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DRILL-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hanifi Gunes updated DRILL-1540:
--------------------------------
    Attachment: DRILL-1540.1.patch.txt

Minor refactoring. Added support for fallback data format. Use *defaultInputFormat* to specify the default format. See below for reference.

{panel:title=example workspace configuration}
"local" : { 
"location" : "/somewhere/data", 
"writable" : true, 
*"defaultInputFormat" : "json"*
} 
{panel}

> Provide a fallback data format in case Drill is unable to determine one
> -----------------------------------------------------------------------
>
>                 Key: DRILL-1540
>                 URL: https://issues.apache.org/jira/browse/DRILL-1540
>             Project: Apache Drill
>          Issue Type: Improvement
>            Reporter: Hanifi Gunes
>            Assignee: Hanifi Gunes
>         Attachments: DRILL-1540.1.patch.txt
>
>
> Drill determines data format looking at the extension. Currently we don't have a fallback data format in case we are unable to determine one - if for instance data file has no extension. In such cases `table not found` exception is thrown. This JIRA proposes specifying a fallback data format per workspace. Workspace level data format fallback should cover major use cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)