Differential D14370

Probable fix for ElasticSearch 2.0 type strictness
ClosedPublic
Actions

Authored by epriestley on Oct 30 2015, 5:00 PM.

Details

Reviewers

chad

Maniphest Tasks

T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0

Commits

Restricted Diffusion Commit
rP4e112537b255: Probable fix for ElasticSearch 2.0 type strictness

Summary

Fixes T9670.

Test Plan

Will follow up on task.

Diff Detail

Repository

rP Phabricator

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

epriestley updated this revision to Diff 34696.Oct 30 2015, 5:00 PM

epriestley retitled this revision from to Probable fix for ElasticSearch 2.0 type strictness.

epriestley updated this object.

epriestley edited the test plan for this revision. (Show Details)

epriestley added a reviewer: chad.

epriestley added a task: T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.

epriestley mentioned this in T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.Oct 30 2015, 5:02 PM

chad accepted this revision.Oct 30 2015, 5:02 PM

chad edited edge metadata.

This revision is now accepted and ready to land.Oct 30 2015, 5:02 PM

Closed by commit rP4e112537b255: Probable fix for ElasticSearch 2.0 type strictness (authored by epriestley, committed by epriestley). · Explain WhyNov 2 2015, 4:21 PM

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

src/

applications/

search/

engine/

PhabricatorElasticSearchEngine.php

2 lines

Diff 34726

View Options

src/applications/search/engine/PhabricatorElasticSearchEngine.php

Probable fix for ElasticSearch 2.0 type strictnessClosedPublicActions