metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-244) Ability to specify column names for datastores that may not have named columns
Date Mon, 25 Apr 2016 19:27:12 GMT

    [ https://issues.apache.org/jira/browse/METAMODEL-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256849#comment-15256849
] 

ASF GitHub Bot commented on METAMODEL-244:
------------------------------------------

GitHub user kaspersorensen opened a pull request:

    https://github.com/apache/metamodel/pull/97

    Feature/read fixedwidth metadata files

    Assuming that #96 (METAMODEL-244) is going forward, here's a patch that would add another
logical piece on top: A utility reader class that allows reading Fixed Width file configuration
from external metadata files. I encountered two of these formats myself so felt the need for
a utility and that might just as well reside in MetaModel if anyone can reuse it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kaspersorensen/metamodel feature/read-fixedwidth-metadata-files

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metamodel/pull/97.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 #97
    
----
commit 3d0666cabce5e6df40ec341bb1d21b74343d1e3f
Author: kaspersorensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-22T21:54:22Z

    METAMODEL-244: Made ColumnNamingStrategy available to fixedwidth module

commit 0da8f1a1cb9fa8bfe87eb73f38df047d111e196d
Author: kaspersorensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-22T22:50:06Z

    METAMODEL-244: Refactored fixedwidth module a bit and added strategies

commit d5b9e12a016e94af78cceeeaf966a226afe8650d
Author: Kasper Sørensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-24T20:32:15Z

    METAMODEL-244: Scoped the column naming session and state into an object

commit 0fcc4de38faa180a321f01ba724f112a70cd86f9
Author: Kasper Sørensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-24T20:48:28Z

    METAMODEL-244: Implemented naming strategy support in csv module

commit a2314f8da2379f7c6da264b1f20071fa77ac832e
Author: Kasper Sørensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-24T20:54:40Z

    METAMODEL-244: Moved to pkg org.apache.metamodel.schema.naming

commit 0396b1a8d37ac8fd65be984d94723f4fd9e95fb5
Author: kaspersorensen <i.am.kasper.sorensen@gmail.com>
Date:   2016-04-25T19:20:48Z

    Added reader to allow getting fixedwidth config from external files

----


> 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
>
> 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)

Mime
View raw message