Deployer search-index should respect redirects
See original GitHub issueIf you use the --update
option when you run the search-index
(bulk uploading to Elasticsearch), we need to respect redirects too.
If we don’t re-create the Elasticsearch index every 24h, we might end up with 2 documents that contain almost the same content but spread across its old URL and its new URL.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Redirects and Google Search | Documentation
Redirecting URLs is the practice of resolving an existing URL to a different one, effectively telling your visitors and Google Search that a ......
Read more >Manage Redirects to External URLs - Salesforce Help
Under External Redirections, in the Allow redirections to untrusted external URLs field, specify the desired behavior when a user clicks an untrusted external ......
Read more >301 and 302 Redirect Rules - Support Center - WP Engine
Redirects, or rewrites, are rules you can create to have certain URLs automatically go to a new location anywhere on the internet.
Read more >Redirect Rules for All; How to configure redirects for your static ...
In this post, lets walk through configuring redirect rules with your ... Browsers need to be told exactly what to do and where...
Read more >Deploy Folder Redirection with Offline Files - Microsoft Learn
This article describes the requirements for deploying the Folder Redirection and Offline Files features together, including the steps that ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
an option to avoid downtime while doing a full recreation of the index would be to use an index alias for the reading usage of elasticsearch in the search endpoint. The script would create a new index (probably with the date of the build in the index name), index all new content in it. Then it would recreate the alias to point to the new index. And then it can delete the old index which is not used anymore.
This way, there is no downtime. While the new index is populated, the search endpoint are still working, as they are still seeing the old data (as the alias still points to the old index at that point).
Right on @schalkneethling, thanks!