Notes from #MetaBrainz Meeting 2017-12-11

Tags: #<Tag:0x00007f4d55f03378> #<Tag:0x00007f4d55f03198>

#MetaBrainz Meeting 2017-12-11

Meeting start:
















Consolidated contributing guidelines video

@Freso pointed out (and that it needs updating), @iliekcomputers noted that all GitHub/code projects have a file.

@samj1912 noted that he «[does]n’t think think [he] would watch a video about that» but would read a wiki page and also pointed to as a possible way of achieving something like this. @chhavi showed that there’s also - @samj1912 suggests using

There was some talk of doing it as a GCI task, or as a series of GCI tasks, but it would depend on one or more mentors picking it up and formulating tasks for it.

In summary:

For indexing you probably want to create a table in the database containing the id’s of items that need to be added to the search index.
You can then add a trigger for each table in the database that will fire on insert or update and have this trigger insert a record to this queue table.

The indexer tool just needs to have a loop that select one or a small number of id’s from this queue table, add the items to the index and deletes the id’s once done.

When building your first index you can run an insert into queue_table as select query to add everything to the queue.

Yup, that’s what we were doing. There was a slightly different problem although it’s fixed now. It should be there in the minutes from later meetings.