-
Notifications
You must be signed in to change notification settings - Fork 284
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
Updates no longer work with Nominatim 4.x #638
Comments
Hello! Is it possible to fix it somehow, or updates will never work with version >=4 |
There will probably be a new update mechanism at some point but it isn't exactly a priority at the moment. |
Can you help with advice on updating the index without downtime if I am using Nominatim 4? |
That's currently not possible with Nominatim v4. |
Sorry to bother, but is the updating/indexing with Photon v0.4.3 and Nominatim version > 3.7 still not possible? Thanks in advance! |
I am running photon 0.4.3 and nominatim 4.3.1. Nominatim data is kept uptodate by running this once a day: nominatim replication --once Photon call "curl http://localhost:2322/nominatim-update" returns "404 Not found". Is it my fault or is update from noninatim data still not possible. If it is not possible you should delete nominatim updates in your documentation and delete the nominatim update script from repository. Like this it is very missleading. |
The issue is still open. |
I could try to give it some time in the next weeks. I never used it as I managed zero downtime update by having a load balancer with health-checks and two photon servers behind. With this setup you can stop one photon service, import full data and restart the service. Then you can do the same on the second photon service. |
Nominatim updates used to work this way: 1. Import updates using osm2pgsql, 2. run a single SQL command I see two ways to solve the problem:
The first solution is more generic but the second one likely easier to implement. So I was leaning towards the second one for now. |
ybert: at the moment stoping service and importing full data is what we do too. A cron jobs runs this script once a week and creates a new data extract from our daily updated nominatim database: ` java -jar /mnt/overpass_api/photon/photon-*.jar -nominatim-import -host localhost -port 5432 -database nominatim -user photon -password 'xxxxxxxxxxxx' -languages de,en,fr systemctl stop photon.service Creating new full nominatim import for all europe takes aprox 24h on our small server. And after it finishes restart with new data is done quickly. It works for us. Would be great of one of you would reenable the "live" updates. Thanks for great work on photon and nominatim btw. |
Nominatim has moved some of the indexing processing into Python code since version 4.x. The simple update mechansim that Photon uses thus only does half the work. In particular, addr:* parts a no longer properly matched.
If you run regular update on your Photon database you must remain with Nominatim 3.7 for now.
Imports still work against the newer version.
The text was updated successfully, but these errors were encountered: