Dave Borowitz 2ab1af186e Store mergeable field from cache in index ... Eventually this will no longer be part of the serialized change proto, and even with the cache it is still expensive to check mergeability for each change in a list of search results, as the submit type must still be checked in order to look up the mergeability. The new MERGEABLE field now loads from the cache, although ChangeJson and several other callers still depend on the field in Change. This will facilitate index schema upgrades, in that a full reindex will also populate the persistent cache. While we're at it, upgrade Lucene to 4.10.1, which contains some important stability bugfixes[1]. [1] http://lucene.apache.org/core/4_10_1/changes/Changes.html#v4.10.1 Change-Id: I166b85f91bd596a3f0295616c2e72853b692dd54		2014-11-03 12:08:34 -08:00
..
BUCK	Store mergeable field from cache in index	2014-11-03 12:08:34 -08:00