Any decent way to accomplish this?
Like data exists since that was imported successfully.
AI-generated summary
In a support thread titled ‘Rebuilding top topics and replies in profiles after import,’ users discuss unresolved issues with profile statistics not updating post-import. TheDarkWizard initially asks for a decent solution, noting that data exists but isn’t reflecting correctly. pfaffman suggests daily background jobs or rake tasks might help, but TheDarkWizard confirms it’s not working. Ghan reports that Sidekiq jobs completed weeks ago, and the ensure_consistency rake task didn’t fix the issue; manually rebuilding via Rails console is too slow for their large dataset. TheDarkWizard seeks input from the @team and notes they’re still investigating alternatives beyond console commands. codinghorror follows up, and TheDarkWizard explains they paused testing as the community wasn’t ready for migration, but believes one test rebuild may have worked — crediting Ghan for the migration script. TheDarkWizard plans to revisit the issue soon. In a final reply, TheDarkWizard confirms the problem remains unresolved despite prior efforts.
I think that stuff gets done daily?
It does not it seems.
Have all of your sidekiq jobs completed? If they have, you can look at the bulk importers and there are some rake tasks that might do that. (Or perhaps someone else will give you an actual answer.)
Yes, all the sidekiq jobs have run successfully. The import has been running for a couple of weeks now and this data has not corrected itself. The ensure_consistency rake task run after import doesn’t seem to rebuild this. There’s a rails console command to rebuild topic statistics that appears to fix this value, but that method is extremely slow. With our topic count we’d be looking at over a month for it to process all the topics at the rate it was going.
Any ideas from anyone on the @team
Would be cool to properly fix profile stats.
We still investigating how to resolve this that isn’t just a rails console command.
Did you ever get this resolved @TheDarkWizard?
I apologize for the delay in getting back to you.
We paused our rebuild tests for now since the community wasn’t ready for the migration but we did many rebuilds and tests, and I believe one of them worked. @Ghan was the person responsible for building the migration script, so he’d be able to answer better. I did the styling and other decisions for our site.
Going to possibly start looking at all this again, will report back any issues that come up!
We still haven’t figured this out.