-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not query user's page views #2415
Comments
I think I have found the answer. So the new version of Canvas has changed the mechanism for saving pageviews, which is partially explained in gems/canvas_cassandra/Readme. It's just that the document doesn't clearly describe the changes in parameters, and I don't know if the Canvas system still supports writing pageviews to cassandra, or I haven't read it myself. |
The current canvas version does not support |
Summary:
I have a self-hosted canvas(prod 2024/09/23), and configed a cassandra, copyed analytics. I found the file cassandra.yml has gone, so I created a cassandra.yml, and executed "rake db:migrate" again, the system created tables in cassandra. But I could not query any user's pageviews , and the table page_views is empty in cassandra. I can access "views courses analytics", and canvas display course related data information on the page.
Steps to reproduce:
1.git analytics
2.rake db:migrate successfuly, Setting.set('enable_page_views', 'cassandra')
3.fail to rake db:migrate_pageviews_to_cassandra.
rake aborted!
Don't know how to build task 'db:migrate_pageviews_to_cassandra' (See the list of available tasks with
Expected behavior:
canvas can display course related data information in analytics pages.
administrator can query page view history.
Actual behavior:
the page view history is empty
Additional notes:
I have not found db:migrate_pageviews_to_cassandra in the list of available tasks with
rake --tasks
I found some explanatory text in gems/canvas_cassandra, I'm not sure if there are more detailed explanations or guidance documents available
The text was updated successfully, but these errors were encountered: