| Age | Commit message (Collapse) | Author |
|---|
|
This commit migrates events data in such a way that push events are
stored much more efficiently. This is done by creating a shadow table
called "events_for_migration", and a table called "push_event_payloads"
which is used for storing push data of push events. The background
migration in this commit will copy events from the "events" table into
the "events_for_migration" table, push events in will also have a row
created in "push_event_payloads".
This approach allows us to reclaim space in the next release by simply
swapping the "events" and "events_for_migration" tables, then dropping
the old events (now "events_for_migration") table.
The new table structure is also optimised for storage space, and does
not include the unused "title" column nor the "data" column (since this
data is moved to "push_event_payloads").
== Newly Created Events
Newly created events are inserted into both "events" and
"events_for_migration", both using the exact same primary key value. The
table "push_event_payloads" in turn has a foreign key to the _shadow_
table. This removes the need for recreating and validating the foreign
key after swapping the tables. Since the shadow table also has a foreign
key to "projects.id" we also don't have to worry about orphaned rows.
This approach however does require some additional storage as we're
duplicating a portion of the events data for at least 1 release. The
exact amount is hard to estimate, but for GitLab.com this is expected to
be between 10 and 20 GB at most. The background migration in this commit
deliberately does _not_ update the "events" table as doing so would put
a lot of pressure on PostgreSQL's auto vacuuming system.
== Supporting Both Old And New Events
Application code has also been adjusted to support push events using
both the old and new data formats. This is done by creating a PushEvent
class which extends the regular Event class. Using Rails' Single Table
Inheritance system we can ensure the right class is used for the right
data, which in this case is based on the value of `events.action`. To
support displaying old and new data at the same time the PushEvent class
re-defines a few methods of the Event class, falling back to their
original implementations for push events in the old format.
Once all existing events have been migrated the various push event
related methods can be removed from the Event model, and the calls to
`super` can be removed from the methods in the PushEvent model.
The UI and event atom feed have also been slightly changed to better
handle this new setup, fortunately only a few changes were necessary to
make this work.
== API Changes
The API only displays push data of events in the new format. Supporting
both formats in the API is a bit more difficult compared to the UI.
Since the old push data was not really well documented (apart from one
example that used an incorrect "action" nmae) I decided that supporting
both was not worth the effort, especially since events will be migrated
in a few days _and_ new events are created in the correct format.
|
|
|
|
name when the project full path contains a `/`
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Fix the iids parameters in the API documentation
See merge request !13340
|
|
Since the parameter name is really `iids[]`, it should be used consistently
across the documentation.
|
|
* master: (177 commits)
Add changelog
Bump gitlab-shell version to 5.8.0 to fix Git for Windows 2.14
Make contextual sidebar collapsible
Fixed sidebar context header hover colors
Use correct `Environment`-class within `Gitlab` namespace
Remove gl.Activities from Commits page
Move `let` calls inside the `describe` block using them
Add `/assign me` alias support for assigning issuables to oneself
GRPC::Unavailable (< GRPC::BadStatus) is wrapped in a CommandError
Use `broken_storage` in the fs_shards_spec.
Eager load project creators for project dashboards
Memoize a user's personal projects count
Remove redundant query from User#recent_push
Improve checking if projects would be returned
Change spelling of gitlab-shell
Remove unused #tree-holder
Add custom linter for inline JavaScript to haml_lint
Rename user_can_admin? because it's more accurate
Synchronous zanata community contribution translation
Add Korean translation to i18n
...
|
|
|
|
|
|
Move API "basic usage" to be more visible
See merge request !13171
|
|
Expose target_iid in Events API
See merge request !13247
|
|
|
|
|
|
Extend API: Group Secret Variable
Closes #34519
See merge request !12936
|
|
I found this basic information extrememly hard to find when I looked
at this page.
|
|
|
|
'skip_confirmation'
|
|
Add top-level /merge_requests API endpoint
Closes #28422
See merge request !13060
|
|
Add all ApplicationSettings attributes to the API
See merge request !12851
|
|
Should have been part of !13004.
|
|
This matches the behavior of the /issues endpoint.
|
|
And add support for additional query parameters:
- `author_id`: Returns merge requests created by the given user `id`
- `assignee_id`: Returns merge requests assigned to the given user `id`
- `scope`: Return merge requests for the given scope: `created-by-me`, `assigned-to-me` or `all`
|
|
branch name when the project full patch contains a `/`
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
Add author_id & assignee_id param to /issues API
Closes #29430
See merge request !13004
|
|
In favor of the new `repository_storages`
|
|
Add link to doc/api/ci/lint.md
Closes #35204
See merge request !12914
|
|
Group milestones API endpoint
Closes #34622
See merge request !12819
|
|
v3 API is unsupported after 9.5, but may not be removed
See merge request !13074
|
|
That is, it may not _necessarily_ be removed. We do not provide guarantees for
when API v3 will be available until beyond 9.5.
|
|
|
|
|
|
Allow issues filtering on `author_id` and `assignee_id`.
|
|
|
|
|
|
|
|
|
|
Fixes needed when GitLab sign-in is not enabled
See merge request !12491
|
|
When sign-in is disabled:
- skip password expiration checks
- prevent password reset requests
- don’t show Password tab in User Settings
- don’t allow login with username/password for Git over HTTP requests
- render 404 on requests to Profiles::PasswordsController
|
|
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
The current "basic" merge request API still loads too much data. For integrations
like the Trello Power-up, we just need the basics.
Closes #34920
|
|
Add creation time filters to user search API for admins
Closes #29507
See merge request !12682
|
|
#20628 Enable implicit flow in Gitlab as OAuth Provider
Closes #20628, #2716, and #19470
See merge request !12384
|
|
Allow to enable the performance bar per user or Feature group
Closes #33929 and #34528
See merge request !12362
|
|
Closes #20628 by re-enabling implicit grant in Doorkeeper config. OAuth2 documentation refactored.
|
|
|
|
|
|
|
|
|
|
|
|
|
