Remove done items

1 files changed, 1 insertions, 62 deletions

diff --git a/TODO.md b/TODO.md
index 29e38c1636b..eec3e3767b6 100644
--- a/TODO.md
+++ b/TODO.md
@@ -5,21 +5,6 @@ This lists some possible improvements to Vespa which have been considered or req
 independently of other work, and are not yet under development. For more information on the code structure in Vespa, see
 [Code-map.md](Code-map.md).
 
-## Query tracing including content nodes
-
-**Effort:** Low<br/>
-**Difficulty:** Low<br/>
-**Skills:** Java, C++, multithreading
-
-Currently, trace information can be requested for a given query by adding travelevel=N to the query. This is useful for 
-debugging as well as understanding performance bottlenecks. However, the trace information only includes execution in 
-the container, not in the content nodes. This is to implement similar tracing capabilities in the search core and 
-integrating trace information from each content node into the container level trace. This would make it easier to 
-understand the execution and performance consequences of various query expressions.
-
-**Code pointers:**
-- [Container-level tracing](https://github.com/vespa-engine/vespa/blob/master/processing/src/main/java/com/yahoo/processing/execution/Execution.java#L245=)
-
 
 ## Support query profiles for document processors
 
@@ -37,42 +22,6 @@ processor profiles by reusing the query profile support also for document proces
 - [Document processors](https://github.com/vespa-engine/vespa/blob/master/docproc/src/main/java/com/yahoo/docproc/DocumentProcessor.java)
 
 
-## Background reindexing
-
-**Effort:** Medium<br/>
-**Difficulty:** Low<br/>
-**Skills:** Java
-
-Some times there is a need to reindex existing data to refresh the set of tokens produced from the raw text: Some search 
-definition changes impacts the tokens produced, and changing versions of linguistics libraries also cause token changes. 
-As content clusters store the raw data of documents it should be possible to reindex locally inside clusters in the 
-background. However, today this is not supported and content need to be rewritten from the outside to refresh tokens, 
-which is inconvenient and suboptimal. This is to support (scheduled or triggered) background reindexing from local data. 
-This can be achieved by configuring a message bus route which feeds content from a cluster back to itself through the 
-indexing container cluster and triggering a visiting job using this route.
-
-**Code pointers:**
-- Document API which can be used to receive a dumpt of documents: [DocumentAccess](https://github.com/vespa-engine/vespa/blob/master/documentapi/src/main/java/com/yahoo/documentapi/DocumentAccess.java)
-
-
-## Change search protocol from fnet to RPC
-
-**Effort:** Medium<br/>
-**Difficulty:** Low<br/>
-**Skills:** Java, C++, networking
-
-Currently, search requests happens over a very old custom protocol called "fnet". While this is efficient, it is hard to extend. 
-We want to replace it by RPC calls. 
-An RPC alternative is already implemented for summary fetch requests, but not for search requests.
-The largest part of this work is to encode the Query object as a Slime structure in Java and decode that structure in C++.
-
-**Code pointers:**
-- FS4 protocol search invokers (to be replaced by RPC): [FS4SearchInvoker](https://github.com/vespa-engine/vespa/blob/master/container-search/src/main/java/com/yahoo/prelude/fastsearch/FS4SearchInvoker.java), [FS4FillInvoker](https://github.com/vespa-engine/vespa/blob/master/container-search/src/main/java/com/yahoo/prelude/fastsearch/FS4FillInvoker.java)
-- Current Query encoding (to be replaced by Slime): [QueryPacket](https://github.com/vespa-engine/vespa/blob/master/container-search/src/main/java/com/yahoo/fs4/QueryPacket.java)
-- Slime: [Java](https://github.com/vespa-engine/vespa/blob/master/vespajlib/src/main/java/com/yahoo/slime/Slime.java), [C++](https://github.com/vespa-engine/vespa/blob/master/vespalib/src/vespa/vespalib/data/slime/slime.h)
-- [C++ query (to be constructed from Slime)](https://github.com/vespa-engine/vespa/blob/master/searchlib/src/vespa/searchlib/query/query.h)
-
-
 ## Java implementation of the content layer for testing
 
 **Effort:** Medium<br/>
@@ -90,17 +39,6 @@ libraries (see the searchlib module).
 - Content cluster mock in Java  (currently empy): [ContentCluster](https://github.com/vespa-engine/vespa/blob/master/application/src/main/java/com/yahoo/application/content/ContentCluster.java)
 - The model of a search definition this must consume config from: [Search](https://github.com/vespa-engine/vespa/blob/master/config-model/src/main/java/com/yahoo/searchdefinition/Search.java)
 
-## Update where
-
-**Effort:** Medium<br/>
-**Difficulty:** Medium<br/>
-**Skills:** Java, C++, distributed systems
-
-Support "update where" operations which changes/removes all documents matching some document selection expression. This 
-entails adding a new document API operation and probably supporting continuations similar to visiting.
-
-- Document operations: [Java](https://github.com/vespa-engine/vespa/tree/master/document/src/main/java/com/yahoo/document/update), [C++](https://github.com/vespa-engine/vespa/tree/master/document/src/vespa/document/update)
-
 
 ## Indexed search in maps
 
@@ -139,6 +77,7 @@ supported is part of the design and analysis needed).
 **Code pointers:**
 - [Document API](https://github.com/vespa-engine/vespa/tree/master/documentapi/src/main/java/com/yahoo/documentapi)
 
+
 ## Global dynamic tensors
 
 **Effort:** High<br/>