Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Dev-where branch : Add a feature to filter the data you need #718
Conversation
|
@shlomi-noach can you take a look ? were really stuck here . |
|
what needs to be done |
|
excellent feature, when will this feature merge into the trunk? |
|
nobody filled me in on what is going on so i am confused |
|
ok thank you
…On Wed, Apr 17, 2019 at 9:45 PM dikang123 ***@***.***> wrote:
excellent feature, when will this feature merge into the trunk?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#718 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALVH5LQEVB6I5DDYJ5LD5XLPQ7OEPANCNFSM4G2FQ3NA>
.
--
sierra
|
| @@ -28,6 +28,7 @@ function build { | |||
| echo "Building ${osname} binary" | |||
| export GOOS | |||
| export GOARCH | |||
|
|
|||
sierra2019
Apr 25, 2019
gtc.gho-stjavascript.
gtc.gho-stjavascript.
|
would this work |
|
We would like to use gh-ost, however we need this functionality; can we expect this to be merged anytime soon? |
What needs to be done for this PR ? It's stuck here with "Some checks haven’t completed yet" , and I dont know how to fix it. |
|
@cenkore Looks like the CI pipeline possibly stalled out there. Maybe rebase with the latest master and push the branch up again to kick the CI bits. |
|
I merged latest master into my branch, still stuck here |
The main usage scenarios are as follows:
If you need to clean up some of the data before you doing the gh-ost release, it can release with
-where-reserve-clausedirectly and you don't need to do a clean up first.If you just wanna clear a lot of data, especially for the amount of cleaning is greater than the amount of retention, it can avoid
DELETE + OPTIMIZEoperation.add 2 flags:
where-reserve-clause:used for only copy where clause stmt valuesforce-query-migration-range-values-on-master:if you use where-reserve-clause flag, by default, will query initial migration range values with corresponding where clause stmt on slave. Also you can specify this flag to true , it will query on master and not care where clause stmt like usual and the where clause stmt would be used at copy rows to gho table.modify 1 flag
-
alter:you can specify Noop if you just wanna do a table slimming and not change the table structure