[
https://issues.apache.org/jira/browse/METAMODEL-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263502#comment-15263502
]
ASF GitHub Bot commented on METAMODEL-244:
------------------------------------------
GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/99
METAMODEL-244: Added support for Excel datastore as well
I realised that although METAMODEL-244 was 'fixed', I had not applied the
technique to the 'Excel' module. This PR does that.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kaspersorensen/metamodel
feature/excel-column-name-mapping
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/99.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #99
----
commit 1349dc090b8ef8173d91f302e601a94dd1104555
Author: Kasper Sørensen <[email protected]>
Date: 2016-04-29T04:11:50Z
METAMODEL-244: Added support for Excel datastore as well
----
> Ability to specify column names for datastores that may not have named columns
> ------------------------------------------------------------------------------
>
> Key: METAMODEL-244
> URL: https://issues.apache.org/jira/browse/METAMODEL-244
> Project: Apache MetaModel
> Issue Type: New Feature
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
> Fix For: 4.5.3
>
>
> Some datastores don't necesarily define the column names/headers, just the
> data. Therefore it is sometimes needed to define column names manually - or
> even via some pluggable interface that would allow a custom naming strategy.
> I can think of the following modules where this would be relevant:
> * csv
> * fixed-width
> * excel
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
