That sounds like a wonderful project, Alexandre — I’ve always wanted such a capability!
I suggest approaching this very pragmatically based on minimizing the time to get something useful, which means leveraging as much as is available already — that means solr’s existing analysis UI screen. I suggest modifying the FieldAnalysisRequestHandler could take optional input of a provided XML fieldType definition in the request instead of using the live schema. It would create a new temporary SolrSchema based on the provided data, then re-use the rest of its field analyzing code based on that schema. Disclaimer: I have yet to look at FieldAnalysisRequestHandler. ~ David Smiley Freelance Apache Lucene/Solr Search Consultant/Developer http://www.linkedin.com/in/davidwsmiley On Sat, Jul 12, 2014 at 1:16 PM, Alexandre Rafalovitch <arafa...@gmail.com> wrote: > I don't want to read the schema.xml, but I do want to create factories > using the same parameters they use in schema. So, it looks like I need > to play around with ResourceLoaders and maybe SPI loaders, so things > like wordlists get loaded. > > Starting from FieldAnalyzer turned out to be a dead-end because it was > using pre-initialized field definitions. But starting again from Test > cases seem to be somewhat more productive. > > The idea for the project is to give a web UI where a user can quickly > put one or more analyzer stacks together and see how it/they perform > against text (multiple texts). A bit similar to FieldAnalyzer but > allow to have multiple stacks side-by-side and NOT needing to reload > the core to add new ones. Then, generate the XML definition, ready for > pasting in. That's the target anyway. > > Regards, > Alex. > Personal: http://www.outerthoughts.com/ and @arafalov > Solr resources: http://www.solr-start.com/ and @solrstart > Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 > >
