-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
openaddress import elasticsearch duplicate values search for pip-service. #445
Comments
Repost for the first 5 URL.
|
That does seem redundant, I suspect what you're seeing is multiple addresses within the same building which share the same lat/long in the source CSV. It would be a nice optimization of we could prevent these duplicate (or even better very near duplicate) lat/lon queries. Are you able to confirm that the duplication is in the source data and not an application error? |
I'm not sure how easy it would be to apply some sort of query caching for these queries... If there was no parallelism it would be simple, it's still totally possible, maybe a rolling buffer which queues those addresses multiple times, queries once and then calls the callback for each matching item in the queue? Anyway I think for now it's fine how it is, it's not causing any issues and so it may be preferable to leave it as-is (with a minor performance hit) rather than add complex code which may be prone to bugs? I could be wrong, depends on the implementation.. |
If someone is interested in looking at this, I think it could be a nice addition to https://github.com/pelias/microservice-wrapper/blob/master/service.js I suspect that either there is an existing Of course the implementation would need to be able to handle parallelism, although this is probably easy in nodejs because it's single-threaded. |
Hi, I'm the author of superagent-cache. I just stumbled upon this issue and thought I'd link to the docs for the preventDuplicateCalls feature. |
Hey team!
I was geocoding with the manual build Openaddress data import to Elasticsearch.
I have noticed that there is a duplicate search request for pip-service.
Latitude and longitude are the same for duplicate requests.
logs are following.
The text was updated successfully, but these errors were encountered: