db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (DERBY-4962) Create a table function which efficiently migrates data out of foreign databases and which can be used for ongoing data integration
Date Fri, 14 Jun 2013 17:32:23 GMT

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

Rick Hillegas reassigned DERBY-4962:
------------------------------------

    Assignee: Rick Hillegas
    
> Create a table function which efficiently migrates data out of foreign databases and
which can be used for ongoing data integration
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4962
>                 URL: https://issues.apache.org/jira/browse/DERBY-4962
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.9.1.0
>
>         Attachments: ForeignTableVTI.java
>
>
> DDLUtils and other tools are good at copying the shape of foreign schemas into Derby.
It would be good to have a tool which efficiently bulk-copies the foreign data into Derby.
This would be faster than having to dump the foreign data into flat files and then import
those files into Derby. In addition, many data integration applications need to siphon new
data out of foreign database on an ongoing basis. A tool based around a RestrictedVTI would
be able to push the column projection and WHERE clause into the foreign database in order
to speed up the siphoning. I will attach a Restricted VTI which can be used for the following
tasks:
> 1) Initial bulk-loading of Derby from a foreign database.
> 2) Efficient on-going data integration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message