Supporting Technical Debt Cataloging with TD-Tracker Tool
Table 3
Cataloged technical debts from ElasticSearch issues in GitHub.
Title
Description
Reindex from _source by document ID or query
Be able to ask the system to reindex from the saved JSON by document ID or query. This is useful once we have ES style plugins for manipulating documents that might later change and therefore cause you to want to reindex some set of documents. #490 and #491 would let you query by a set of documents indexed before the required change. If you are going to store the JSON, you can take advantage of that by reindex requests. This might also allow the system to handle schema changes in the future more automatically by reindexing to the new analyzer over time in batch.
Changes API #1242
There should be an integration point for ES and external application where the external applications should be notified of any document changes or updates that happen in ES. CouchDB have a good implementation on it and it would be great if ES can also incorporate something similar or same. CouchDB change notification feature http://guide.couchdb.org/draft/notifications.html
Terms facet gives wrong count with n_shards > 1 #1305
With only one shard the following query gives the correct counts no matter what the size parameter is set to. However, with more than one shard the size parameter affects the accuracy of the counts. If it is equal to or greater than the number of terms returned by the facet query (5 in this case) then it works fine. However, the terms at the bottom of the list start to display low counts as you reduce the size parameter.
