mysql-partitioner 0.1.2 → 0.1.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7bb0ba3d4223d4f8ba5ff0ee0680a74f625d8a6b
-  data.tar.gz: 54a8acd9478b085803aeec26b898026ad130578a
+  metadata.gz: dba04134b4d190b8c7f19da8e026d3fbd5f2e591
+  data.tar.gz: 815d422aae033d0bc0fe56a5326a231d9eae99ce
 SHA512:
-  metadata.gz: 4ec7efe09a2ff1d1d789d51c29e840a26716ebced29a84bf6676ec811750bb8d96d5cad7c7c817f4c93833dc202e552e01ce2f184778bf37ee8d5589991e7ad4
-  data.tar.gz: 14b136f672ecfd896eade781c49e0238ab60d0880ebc54be9f226a5c1a2e94c2f1ffe28d54d4360b722d7870a1ae5e9d494f4480d4f4d8c627c0ed954792e6e2
+  metadata.gz: bee2b105025933273c7a42d2b0d2079f9728afbccca26918b35717f118a17856a01703d184515d57dc80786a2af0ceba07aa7d5ad033909a8eee49b3b16a61ec
+  data.tar.gz: 5cc8f61e685880df9fd0a758c3f81cfaaf8bb3b2423f032f9643cb03892b425b016de6839eb3e9a8b04a517290a28442359ec11721e4556a66090d6db8ce0f4c

data/README.md

@@ -1,8 +1,6 @@
-# Mysql::Partition
+# Mysql::Partitioner
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/mysql/partitioner`. To experiment with that code, run `bin/console` for an interactive prompt.
-
-TODO: Delete this and the text above, and describe your gem
+Mysql partition management tools
 
 ## Installation
 
@@ -22,25 +20,94 @@ Or install it yourself as:
 
 ## Usage
 
-`
+```
 Usage: mysql-partitioner [options]
     -c, --config CONFIG_NAME
         --cmd check or migrate
         --dry-run
     -d, --debug
-`
+```
+
+sample config
+
+* https://github.com/maedama/mysql-partitioner/blob/master/sample/config.yaml
+
+## Features
+
+
+### Supported partition type
+
+Currently it supports, Range partition without sub partition
+
+### Supported Partition Strategy
+
+##### PartitionByPkDropByRange
+
+This Strategy allows us to partition table with Primary Key, and at the same time manage partition by timestamp
+
+| Parameter | Description |
+|-----------|-------------|
+| Key | Partition Key |
+| time_key | Time key |
+| min_empty_partitions | If empty partitions is less than this number, check command would fail |
+| desirable_empty_partitions | When migration happens, mysql-partitioner will prepare this number of  partitions  for future |
+| range | Range of each partitions |
+| ttl | when migration happens tool will drop partitions with all items in partition is older than this ttl |
+
+
+Typical example of partitioning with timestamp is like bellow.
+
+```
+CREATE TABLE test(
+    id big int unsigned NOT NULL,
+    content varchar(255) NOT NULL,
+    created_at DATETIME NOT NULL,
+    PRIMARY KEY(id, created_at)
+) Engine=InnoDB;
+
+``` 
+
+By including created_at in primary key, mysql can know which partition each data belongs to.
+And each data will be unique if and only if it is unique in the partition they belong to.
+
+But this approach has major fallback in terms of performance.
+
+i.e Query like bellow would be very slow in such a partitions
+
+```
+SELECT * FROM test WHERE id in (1, 100, 10000,1000000,10000000000000)
+```
+
+Instead of such an partitioning, this strategy partions table like bellow,
+
+```
+CREATE TABLE test(
+    id big int unsigned NOT NULL,
+    content varchar(255) NOT NULL,
+    created_at DATETIME NOT NULL,
+    PRIMARY KEY(id, created_at)
+) Engine=InnoDB;
+
+```
+
+When migration happens, toosl find all partitions with following condition and drops them.
+
+* Is not most recent active partition
+* All items in partitions is older that specified ttl
+
+Additionally tool will also try to make new_partitions with specified parameter
 
 
 ## Example
 
-`
+```
 CREATE TABLE `partition_test` (
   `id` bigint(20) unsigned NOT NULL,
   `created_at` datetime NOT NULL,
   `updated_at` datetime NOT NULL,
   PRIMARY KEY (`id`)
 ) Engine=InnoDB
-`
+```
 
 Initialize first partition
 

data/lib/mysql/partitioner/operation/range.rb

@@ -18,7 +18,7 @@ module Mysql
         def get_current_partitions
           results = self.session.query(<<SQL)
 SELECT PARTITION_EXPRESSION, PARTITION_DESCRIPTION, PARTITION_ORDINAL_POSITION, PARTITION_METHOD, SUBPARTITION_EXPRESSION
-FROM INFORMATION_SCHEMA.PARTITIONS WHERE TABLE_NAME="#{ self.table }" AND TABLE_SCHEMA="#{ self.database }"
+FROM INFORMATION_SCHEMA.PARTITIONS WHERE TABLE_NAME="#{ self.table }" AND TABLE_SCHEMA="#{ self.database } ORDER BY PARTITION_ORDINAL_POSITION ASC"
 SQL
           results.map {|item|
             Mysql::Partitioner::Partition::Range.new(item["PARTITION_DESCRIPTION"])

data/lib/mysql/partitioner/version.rb

@@ -1,5 +1,5 @@
 module Mysql
   module Partitioner
-    VERSION = "0.1.2"
+    VERSION = "0.1.3"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mysql-partitioner
 version: !ruby/object:Gem::Version
-  version: 0.1.2
+  version: 0.1.3
 platform: ruby
 authors:
 - maedama