{"push_id":573787171,"size":2,"distinct_size":0,"ref":"refs/heads/release","head":"c5f566cd85cf076a83469f27c530d9eacbc45fce","before":"f6e90566affb6ed44c3b61cc231ef9edad06ebc8","commits":[{"sha":"962aa59834f77ae99fdf7167b39e7074017cf593","author":{"email":"2b6bbb4bffb950b0967cd3a1166c66cfcf859973@digital.cabinet-office.gov.uk","name":"Richard Boulton"},"message":"Always configure the location field the same way\n\nThe \"location\" field is defined in three doctypes currently:\naaib_report, european_structural_investment_fund and\ninternational_development_fund.  In two of these cases, it is defined as\nnot_analyzed, but in the aaib_report case it is defined as analyzed.\n\nIt will be much easier to make elasticsearch behave usefully if all our\nfields have the same configuration (for example, if we attempted to\ncompute a facet across the location field currently, we'd get exact\nvalues back from the ESI and IDF documents which could be passed into a\nterms filter, but would get individual tokenised and stemmed words back\nfrom the AAIB documents which wouldn't work in such a filter).\n\nFortunately, the AAIB location field is currently not being searched on\nat all: it's only being used for display.  Therefore, this PR changes\nthe schema so that the \"not_analyzed\" value is used for all \"location\"\nfields, and this should have no effect on searches.","distinct":false,"url":"https://api.github.com/repos/alphagov/rummager/commits/962aa59834f77ae99fdf7167b39e7074017cf593"},{"sha":"c5f566cd85cf076a83469f27c530d9eacbc45fce","author":{"email":"742d16f32570b1c4e9a798a62cbe09b608f64dd7@gmail.com","name":"Dominic Baggott"},"message":"Merge pull request #361 from alphagov/location-schema-consistency\n\nAlways configure the location field the same way","distinct":false,"url":"https://api.github.com/repos/alphagov/rummager/commits/c5f566cd85cf076a83469f27c530d9eacbc45fce"}]}