lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Updated: (SOLR-396) tool to auto generate stub analysis factories
Date Fri, 02 Nov 2007 01:00:50 GMT


Hoss Man updated SOLR-396:

    Attachment: SOLR-396.patch

patch that takes the previous proof of concept and integrates it into the solr build.xml as
a new "stub-factories" target.

patch also includes many new factories produced by this target, included some Russian and
Greek factories that were stubs i filled in with some "char[] charset" selection args (not
that i really understand how/why these filters use these char[]s ... it's all unicode in the
jvm right? but they key is that the factories support all the options the filters support).

> tool to auto generate stub analysis factories
> ---------------------------------------------
>                 Key: SOLR-396
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Minor
>         Attachments: factory-stub.tgz, SOLR-396.patch
> a pet project i've bene working on in some spare time has been looking at source code
and byte code analysis toolkits with the goal of being able to write a tool that could be
pointed at a jar, and it would generate stub Factories for any TokenFilter or Tokenizer classes
it found not already in Solr.
> in the end, it looks like a combination of reflection and some simple pattern matching
is actually the best way to go (byte code loses info about param names, and reflection saves
a lot of the hassle involved in pure source code analysis)
> i've got a proof of concept ready that i'll attach shortly.  I hope to have some time
next week to resubmit this as a patch that integrates it with the solr build.xml in such a
way that anytime we add/update a lucene jar, we can run "ant stub-factories" and have 99%
of the work done for us.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message