document/current/en/features/scaling/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Migration on ShardingSphere</title>
    <link>https://shardingsphere.apache.org/document/current/en/features/scaling/</link>
    <description>Recent content in Data Migration on ShardingSphere</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    
	<atom:link href="https://shardingsphere.apache.org/document/current/en/features/scaling/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Core Concept</title>
      <link>https://shardingsphere.apache.org/document/current/en/features/scaling/concept/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://shardingsphere.apache.org/document/current/en/features/scaling/concept/</guid>
      <description>Nodes Instances for running compute or storage tier component processes. These can either be physical machines, virtual machines, or containers, etc.
Cluster Multiple nodes that are assembled together to provide a specified service.
Source The storage cluster where the original data resides.
Target The target storage cluster to which the original data is to be migrated.
Data Migration Process The entire process of replicating data from one storage cluster to another.</description>
    </item>
    
    <item>
      <title>Limitations</title>
      <link>https://shardingsphere.apache.org/document/current/en/features/scaling/limitations/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://shardingsphere.apache.org/document/current/en/features/scaling/limitations/</guid>
      <description>Procedures Supported  Migration of peripheral data to databases managed by Apache ShardingSphere. Migration of integer or string primary key tables.  Procedures not supported  Migration without primary key tables. Migration of composite primary key tables. Migration on top of the current storage node is not supported, so a brand new database cluster needs to be prepared as the migration target cluster.  </description>
    </item>
    
  </channel>
</rss>