[
https://issues.apache.org/jira/browse/DRILL-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aditya Kishore updated DRILL-1540:
----------------------------------
Attachment: DRILL-1540-Provide-a-fallback-data-format-in-case-Dr.patch
Just realized that this change could cause Drill bit startup failure in
existing cluster since Jackson will not longer see {{"storageformat"}} as one
of the property of {{WorkspaceConfig}}.
Updating the patch, adding "storageformat" to ignored property list.
> 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-Provide-a-fallback-data-format-in-case-Dr.patch,
> 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)
