This PR contains the integration of the following new tables:
be_read
popularity
read
To integrate these takes, the data generator python script was modified in order to generate better data fitting the new data model. The previous tables user and article were slightly modified to host more coherent datatypes. For example, the timestamp was changed into a BIGINT, and the previous _id column is replaced by the column. The modifications of the 2 tables were reported to the APIs and Frontend.
The read table contains the computed records for the different actions that a user might have done to a given article. The read table contains auto-generated data from the python script. The inserted record of read table will come populate the be_read table thanks to a VRrep stream. The popularity table is updated according to a cron schedule thanks to a CronJob in the Kubernetes cluster.
This PR contains the integration of the following new tables:
To integrate these takes, the data generator python script was modified in order to generate better data fitting the new data model. The previous tables
userandarticlewere slightly modified to host more coherent datatypes. For example, the timestamp was changed into a BIGINT, and the previous_idcolumn is replaced by thecolumn. The modifications of the 2 tables were reported to the APIs and Frontend.The
readtable contains the computed records for the different actions that a user might have done to a given article. Thereadtable contains auto-generated data from the python script. The inserted record ofreadtable will come populate thebe_readtable thanks to a VRrep stream. Thepopularitytable is updated according to a cron schedule thanks to a CronJob in the Kubernetes cluster.