Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 17 Aug 2011 20:01:27 +0000 (UTC)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <40533147.46434.1313611287842.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28121330.240581294590766131.JavaMail.jira@thor>
Subject: [jira] [Resolved] (DERBY-4962) Create a table function which
 efficiently migrates data out of foreign databases and which can be used
 for ongoing data integration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden resolved DERBY-4962.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.9.0.0

Resolving in 10.9 since the tool was created in that timeframe. I wonder though should this be checked in somewhere?


> 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
>             Fix For: 10.9.0.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira