Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <01aa01d20b86$809cab40$81d601c0$@thetaphi.de>
References: <CAEFAe-FDu3Mzbe7QxkUPG5rkKHET5UxV-nMfjR4c60O3tHdk9Q@mail.gmail.com>
 <016501d20b34$67ebd780$37c38680$@thetaphi.de> <CAEFAe-E2hM8td+bOCRv36xNgD_u02wqMVDkUAaCCWaVqFYFKeA@mail.gmail.com>
 <FD964368-BF41-4910-A9D6-A26C6EABF7AC@thetaphi.de> <019a01d20b74$8ccc8050$a66580f0$@thetaphi.de>
 <1473520862.639625.721622937.30B17BE1@webmail.messagingengine.com>
 <01a901d20b83$df86a410$9e93ec30$@thetaphi.de> <01aa01d20b86$809cab40$81d601c0$@thetaphi.de>
From: Alexandre Rafalovitch <arafalov@gmail.com>
Date: Sun, 11 Sep 2016 11:01:52 +0700
Message-ID: <CAEFAe-FEQuj+ZrVz=qAexagVJ64uUJYFJOzrdA3CFPpVKi5SNQ@mail.gmail.com>
Subject: Re: Is "solr.AnalyzerName" expansion supposed to work for Analyzers?
To: dev@lucene.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 11 Sep 2016 04:02:40 -0000

I feel the total issue might be somewhat above my current code
understanding, but I would be happy to do the grunt work for the
factories to self-describe their parameters. I think that would be
useful in multiple ways. I was already looking at perhaps using MBean
describers for that, as that allows to specify types, acceptable
values, etc.

Regards,
   Alex.
----
Newsletter and resources for Solr beginners and intermediates:
http://www.solr-start.com/


On 11 September 2016 at 00:12, Uwe Schindler <uwe@thetaphi.de> wrote:
> Hi,
>
> In addition this change (to "name" or "type" in the components) would all=
ow to remove Steve Rowe's hack in AbstractAnalysisFactory to keep the class=
 name in the parameter map for serializing, which is Solr specific and shou=
ld not be there! With the "official" names, this is no longer needed and So=
lr could simple serialize the name. This hack hurted me several times alrea=
dy!
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>> -----Original Message-----
>> From: Uwe Schindler [mailto:uwe@thetaphi.de]
>> Sent: Saturday, September 10, 2016 6:54 PM
>> To: dev@lucene.apache.org
>> Subject: RE: Is "solr.AnalyzerName" expansion supposed to work for
>> Analyzers?
>>
>> Let's open an issue to do what I proposed! After that you could add the
>> schema editor GUI.
>>
>> I think Robert already proposed back at that time to add an additional
>> abstract method to each factory that returns the acceptable parameter
>> names. So one could select the component with help of SPI set. Once the
>> component was chosen the acceptable configuration parameters can be
>> retrieved from the instance.
>>
>> Uwe
>>
>> -----
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: uwe@thetaphi.de
>>
>> > -----Original Message-----
>> > From: Upayavira [mailto:uv@odoko.co.uk]
>> > Sent: Saturday, September 10, 2016 5:21 PM
>> > To: dev@lucene.apache.org
>> > Subject: Re: Is "solr.AnalyzerName" expansion supposed to work for
>> > Analyzers?
>> >
>> > On Sat, 10 Sep 2016, at 04:03 PM, Uwe Schindler wrote:
>> > > To add,
>> > >
>> > > the manages schema really makes it easy to "rewrite". My plan would =
be:
>> > >
>> > > - Add a new "type" or "name" attribute to schema.xml, which is contr=
ary
>> > > to "class" attribute usage
>> > > - When a manages schema is loaded, the resolving of classes using th=
e
>> > > hack is done as it is now. Warnings are printed as said before.
>> > > - The managed schema is then changes to switch to the new attribute
>> > > (there is a getter to get the symbolic name from the factory, so
>> > > rewriting is easy)
>> > >
>> > > In addition, this simplifies usage: Some GUI could show a dropdown l=
ist
>> > > for clicking together the analyzer. We just need to add a schema-RES=
T
>> > > endpoint to get all names.
>> > >
>> > > Maybe open an issue targeted for 6.x / 7.0. I'd be happy to help to =
fix
>> > > this, although I could only do the SolrResourceLoader and SolrAnalyz=
er
>> > > stuff.
>> >
>> >  Not knowing how to get a list of acceptable components was the thing
>> >  that stopped me adding that part of the schema API to the admin UI. A=
nd
>> >  API to tell you which components exist would be extremely helpful.
>> >
>> > Upayavira
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> > For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org