#metabrainz

Oh yea I'll check for that as well

Thanks for reminding

Though it should be responsive by default but I'll still check for it

Hi lucifer monkey

I have updated the PR with the screenshots on desktop and mobile view as well

I had one more query

I created the branch `importer-UI` from the branch `main-importer` but I had created the PR #3317 that merges to main instead of `main-importer`

Now when I go to edit option in the PR, I don't see the option to set `main-importer` as the branch it merges to from the list of branches

suvid: yes you can't do that because `main-importer` is a branch on your github fork not the metabrainz repo.

lucifer[m]: oh

sol first `main-importer` will have to be merged to main and then only `importer-UI` would be merged right?

yes.

Hey lucifer is the entire DB present on wolf?

MB or LB?

MB

yup it us

* yup it is

* ````>>>... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* ```>>> spark.sql("select count(*) from listens l, recording_artist ra where l.recording_mbid = ra.recording_mbid").show()... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* ```... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

Shouldn't the 2 be equal?

no, because in this query filter for listens which have a matching recording mbid in recording artist table. that filters out listens which don't have a recording mbid.

yeah but shouldn't all the listens have a mbid?

i mean if not all atleast like the most of it

right now roughly 10% of the listens have a matching mbid

no, all listens have a msid but not all listens have a mbid.

ah that is probably because your spark wolf setup only has the sample dumps.

again, MB db on wolf is not the same as your spark setup on wolf.

MB db has the full dataset, your spark setup only sample.

so the discrepancy is fine right

yes

is there a possibility to get the entire db or like some more content cause the results are too small to test and verify