Re: Defining a phonetic analyzer and searcher via the schema API

2018-03-12 Thread Erick Erickson
Chris: LGTM, except maybe ;). You'll want to look closely at your admin UI/Analysis page for the field (or fieldType) once it's defined. Uncheck the "verbose" box when you look the first time, it'll be less confusing. That'll show you _exactly_ what the results are and whether they match

Re: Defining a phonetic analyzer and searcher via the schema API

2018-03-12 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Erick, On 3/12/18 1:00 PM, Erick Erickson wrote: > bq: which you aren't supposed to edit directly. > > Well, kind of. Here's why it's "discouraged": > https://lucene.apache.org/solr/guide/6_6/schema-api.html. > > But as long as you don't

Re: Defining a phonetic analyzer and searcher via the schema API

2018-03-12 Thread Walter Underwood
People can discourage that, but we only use hand-edited schema and solrconfig files. Those are checked into version control. I wrote some Python to load them into Zookeeper and reload the cluster. This allows us to use the same configs in dev, test, and prod. We can actually test things before

Re: Defining a phonetic analyzer and searcher via the schema API

2018-03-12 Thread Erick Erickson
bq: which you aren't supposed to edit directly. Well, kind of. Here's why it's "discouraged": https://lucene.apache.org/solr/guide/6_6/schema-api.html. But as long as you don't mix-and-match hand-editing with using the schema API you can hand edit it freely. You're then in charge of pushing it