In T9670#142765, @epriestley wrote:Thanks for testing the patch, should be in HEAD now. Let us know if you run into anything else.
Not sure what @tycho.tatitscheff ran into.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Nov 2 2015
Nov 2 2015
kozejonaz added a comment to T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.
kozejonaz added a comment to T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.
@epriestley/@tycho.tatitscheff: We managed to test D14370 now, and it totally fixes our problem!
kozejonaz added a comment to T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.
In T9670#142547, @tycho.tatitscheff wrote:I tested and i does not fix !
Well, I didn't move to elastic 2.0 but restarting elasticsearch, reindexing rerestarting and reruning plugin doesn't leave me the same error.
Oct 31 2015
Oct 31 2015
kozejonaz added a comment to T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.
In T9670#142544, @epriestley wrote:D14370 likely fixes this, although I don't have ElasticSearch 2.0 locally and haven't tested it. I'd guess this will give you a clean bill of health:
- Apply the patch;
- run bin/search index --all to rebuild all indexes;
- run the ElasticSearch tool again.
Can you let me know if that works?
Oct 29 2015
Oct 29 2015
kozejonaz added a comment to T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.
After a closer look there seem to be quite a lot of inconsistencies for the different .when fields.
kozejonaz updated the task description for T9670: Conflicting field mappings for phabricator index when upgrading to Elasticsearch 2.0.