I've been through all that code in Solr, and it sounds like you'd have to
replicate its function. Wow, that's a truly ambitious task! Good Luck!
I'm sure that a fair amount of it could be refactored dramatically to be a
lot simpler since Solr evolved piecemeal over the years, but... that's
another monumental task.
And it would indeed be great to have a field type editor and field type API
for the Solr Admin UI/API itself.
As Uwe indicated, the factories are already in Lucene, so all you need to do
is generate their parameters from the field type filter parameters. But...
for a friendly development tool you would probably like a lot more friendly
parameter checking and error reporting than the raw exceptions (and weak
validation) found in the traditional Solr/Lucene factories. Again, a lot of
that could be refactored since it has evolved over the years, but... that's
another monumental task. Still, Solr would so much the better for it.
And self-describing (and self-documenting) filter factories would be a
fantastic improvement to Solr.
-- Jack Krupansky
-----Original Message-----
From: Alexandre Rafalovitch
Sent: Saturday, July 12, 2014 1:16 PM
To: dev@lucene.apache.org
Subject: Re: Hints on constructing/running Solr analyzer chains standalone
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
On Sat, Jul 12, 2014 at 11:34 PM, Uwe Schindler <u...@thetaphi.de> wrote:
Hi,
Hmmmm, I think it's reasonably straightforward to construct what is
implied
by a Solr analysis chain in Lucene, would that do? Or do you want to read
a
schema.xml file outside Solr?
If the former, then you can pretty much skip the Solr code entirely.
Read this:
http://lucene.apache.org/core/4_9_0/core/org/apache/lucene/analysis/package-summary.html#package_description
To do analysis, Solr is not needed at all, unless you want to read
schema.xml files. If you want to do this, that is quite easy using the
IndexSchema class. You can then get the analyzer from the field type or
field name. How to use the analyzer is described above and unrelated to
Solr.
Uwe
On Sat, Jul 12, 2014 at 6:59 AM, Alexandre Rafalovitch
<arafa...@gmail.com>
wrote:
> Hello,
>
> I am interested in creating and running Solr analyzer chains outside
> of normal process (no live Solr). Just construct a chain, feed it
> tokens and see what happens.
>
> I would appreciate any hints on what that takes and whether there are
> any hidden/weird dependencies (e.g. for resource discoveries). I tried
> tracing through FieldAnalysis calls, but can't actually seem to find
> the point where the actual analysis is done. Just getting lost in sets
> of NamedList<NamedList<... all alike.
>
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For
> additional commands, e-mail: dev-h...@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional
commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
