-
-
Notifications
You must be signed in to change notification settings - Fork 56
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
Copy prod data to stagging (aka .net) #894
Comments
As discussed with @alexgarel, it would be more interesting to completely drop the What needs to be done:
|
- delete server_domain in image, product_insight and prediction tables - add server_type field to image and prediction tables - use ProductIdentifier (barcode + server_type) instead of barcode in codebase See #894
- delete server_domain in image, product_insight and prediction tables - add server_type field to image and prediction tables - use ProductIdentifier (barcode + server_type) instead of barcode in codebase See #894
- delete server_domain in image, product_insight and prediction tables - add server_type field to image and prediction tables - use ProductIdentifier (barcode + server_type) instead of barcode in codebase See #894
Fixed by #1083. What has been done:
Full docker command ES update by query: docker exec -it robotoff_elasticsearch_1 curl -X POST "http://elastic:$ELASTIC_PASSWORD@localhost:9200/logo/_update_by_query?conflicts=proceed&pretty" -H 'Content-Type: application/json' -d'{"query": {"bool": {"must_not": {"exists": {"field": "server_type"}}}}, "script": {"inline": "ctx._source.server_type = \"off\"", "lang": "painless"}}' |
Well I missed the fact this issue was not really about multi-platform support on Robotoff, so I'm reopening it. |
Problem
On production we have a lot of data but very few in stagging, because there are very few product addition.
For productopener we copy data from production (in mongodb).
Copying data from production to stagging is not that easy because the server_domain column has to be updated which takes a lot of time.
Proposed solution
I'm not sure what is the best option, but I would say:
The text was updated successfully, but these errors were encountered: