Overview
This article provides a view of the EAE database tables that the Recommender service uses the most. This information is usually helpful in troubleshooting issues related to data such as data mismatch, incorrect data shown in the user interface, and the like.
Information
| Table | Notes | Read / Write / Expected Growth |
jivecontentbody |
Purpose: Used for storing content bodies that will be shredded for the recommender. | |
jiverecommendationscores |
Purpose: Stores the score information for a given recommendation in the system which we pass back to the application in order to generate the desired user interface. | |
jiverejectedreco |
Purpose: Stores a list of recommendations that have been rejected by a user (or that the user shouldn't see because of various rules in place). This also acts as a cache when we query for a recommendation that the user just said they weren't interested in since the recommender might not update immediately. |
Cleanup Job: ClearOldRejections- removes everything over two weeks old. This runs when:
|
jiveuserrecommendations |
Purpose: Stores a list of all recommendations in the system. | |
jiveuserstreamparentgroup |
Purpose: Stores the grouped activity items (one per piece of content, per user) for their followed stream. | Cleanup Job: RemoveOldUserStreamItems- expiration 60 days (configurable) |
jiveusertorecommendationlookup |
Purpose: Stores a list of all recommendations that have been provided to a user and maps them to a specific recommendation in the jiveuserrecommendation table. |
NOTE:
Schema changes are common between JIVE versions.
Priyanka Bhotika
Comments