[
https://issues.apache.org/jira/browse/DRILL-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173211#comment-14173211
]
Hanifi Gunes edited comment on DRILL-1540 at 10/16/14 1:32 AM:
---------------------------------------------------------------
i) Minor refactoring. ii) 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}
was (Author: hgunes):
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)
