You have a local clone of a github repository, somebody created a pull request against this repository and you would like to apply it to your clone before the maintainer of the origin actually merges it.
How to do that?
It is actually surprisingly neat. When you look at the url of a github PR:
You can just add ‘.patch’ at the end of the url to get a nicely formatted email patch:
From there on, you have a few options. If you download the patch (in say pr.patch) at the root of your clone, you can apply it:
git am ./pr.patch
If you want to apply the code patch without actually apply the commits, you can use your old trusty patch command:
patch -p 1 < ./pr.patch
If you are lazy (as my director studies always said, ‘laziness drives progress’), you can do all in one line:
wget -q -O - 'https://github.com/torvalds/linux/pull/42.patch' | git am
If you have a load in multiple steps (say data is first loaded in a staging schema, then moved to another one), using MOVE_PARTITIONS_TO_TABLE() is the best option. This is very fast, as you do not need to actually issue INSERT or DELETE statements or deal with the delete vectors. Vertica just moves in one go a block of data, and you are done.
When you issue this function, Vertica will first issue a moveout to empty the WOS before moving data. This does make sense, as if data is loaded in memory, you still want to make sure it is moved with the rest of the of the partition already on disk.
Since at least Vertica 7.0.1-1, using this function might give you the error message:
select move_partitions_to_table ('stg.A', 0, 24, 'vault.A')
ERROR: A Moveout operation is already in progress on projection vault.B_node0002
As you can see, a moveout on table A fails because of a moveout on table B, which does not seem to make sense.
It has actually been confirmed that it does not make sense, and it actually is a bug in Vertica 7.0.1-1, which should be fixed in theory in the next service pack.
In the mean time, you can work around the bug by issuing INSERTs/DELETEs, or have your code checks if a moveout is already running before issuing the move_partitions_to_table() statement.
EDIT: The hotfix 7.1.1-1 (11/2014) fixes the bug.