-
Notifications
You must be signed in to change notification settings - Fork 299
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
Most popular items #33
Comments
Hi, Can you tell us the command you are using to train the model? |
Hi, i edit part of seldon.con file to look like this: "cluster-by-dimension": {
"config": {
"inputPath": "%SELDON_MODELS%",
"outputPath": "%SELDON_MODELS%",
"activate":true,
"startDay" : 1,
"days" : 1,
"activate" : true,
"jdbc" : "jdbc:mysql://mysql:3306/client?user=root&characterEncoding=utf8",
"minActionsPerUser" : 0,
"delta" : 0.1,
"minClusterSize" : 200
},
"training": {
"job_info": {
"cmd": "%SPARK_HOME%/bin/spark-submit",
"cmd_args": [
"--class",
"io.seldon.spark.cluster.ClusterUsersByDimension",
"--master",
"spark://spark-master:7077",
"--driver-memory",
"8g",
"--executor-memory",
"8g",
"--total-executor-cores",
"12",
"%SELDON_SPARK_HOME%/seldon-spark-%SELDON_VERSION%-jar-with-dependencies.jar",
"--client",
"%CLIENT_NAME%",
"--zookeeper",
"%ZK_HOSTS%"
]
},
"job_type": "spark"
}
}, then i run
after that
with output:
and finally I run:
Part of train output:
Maybe I'm missing some settings or something, but the seldon docs is pretty confusing and there is not much about "most popular recommender". I also found this file https://github.com/SeldonIO/seldon-server/blob/d1ec05a6f59b152eca438f1e67e2dc73a3879483/offline-jobs/spark/src/main/scala/io/seldon/spark/recommend/MostPopularJob.scala Thanks |
Issues go stale after 90d of inactivity. |
Hi,
how can I setup seldon-server to recommend most popular items?
I try to set it with "cluster-by-dimension" model, but it always faild on model train action with java.lang.ClassNotFoundException: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException
Thanks
mt.
The text was updated successfully, but these errors were encountered: