Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Queries about the Gitlab Worker data model[To be implemented]

See original GitHub issue

Model Schema expectation for Gitlab Data Collection Worker This query is with regard to the schema which would be created during the implementation of the GitLab Data Collection Worker. After carrying out research pertaining to GitLab’s internal API & how it interacts with their data model, there are some commonly used data tables such as issues, pull_requests, commits etc with respect to GitHub. The Question – Should we be using the existent tables present in the augur schema to store the data during the collection process[Additionally creating tables which are not common] (or) create a new collection of tables solely for GitLab?

I’d prefer the creation of gitlab_<data_model_name> tables under the augur_data schema but thought it would be great to gain some inputs from the community. Adding, I’d also love to hear about any suggestions as I’m attempting to chalk out a data model outline for the idea.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:13 (12 by maintainers)

github_iconTop GitHub Comments

abhinavbajpai2012commented, Mar 22, 2020

Okay. Cool. Actually I once used Stitch which is a subscription-based/paid data collector worker for Lever and JIRA which pushes data to Big Query / AWS Redshift. It used to add extra columns for new attributes being added. This idea felt cool to me as storing extra data should not create a problem but could be used later.

ccarterlandiscommented, Mar 16, 2020

@mrsaicharan1 just gave your proposal a glance and it’s already looking great!! I will leave some detailed review comments in the near future but you’re off to a great start!

Read more comments on GitHub >

github_iconTop Results From Across the Web

SQL Query Guidelines - GitLab Docs
SQL Query Guidelines. This document describes various guidelines to follow when writing SQL queries, either using ActiveRecord/Arel or raw SQL queries.
Read more >
QueryRecorder - GitLab Docs
QueryRecorder is a tool for detecting the N+1 queries problem from tests. Implemented in spec/support/query_recorder.rb via 9c623e3e. As a rule, merge requests ...
Read more >
GitLab scalability
When the application starts, Rails queries the database schema, caching the tables and column types for the data requested. Because of this schema...
Read more >
Store and update namespace statistics in a performant manner
This worker will: Update the root namespace storage statistics by querying all the namespaces through a service. Delete the related ...
Read more >
Database Review Guidelines - GitLab Docs
Queries. If new queries have been introduced or existing queries have been updated, you are required to provide: Query plans for each raw...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found