Re: Some new SOLR features

ically scanning a directory of configuration files. >>>>> When >>>>> a new one appears, or an existing file is touched, load it. When a >>>>> configuration disappears, unload it. This model works very well for >>>>> servlet >>>>&

Re: Some new SOLR features

ad it. When a >>>> configuration disappears, unload it. This model works very well for >>>> servlet >>>> containers. >>>> >>>> Lance >>>> >>>> -Original Message- >>>> From: [EMAIL PR

Re: Some new SOLR features

ROTECTED]> >>>> wrote: >>>> >>>> >>>>> >>>>> My vote is for dynamically scanning a directory of configuration files. >>>>> When >>>>> a new one appears, or an existing file is touched, load it. When a

Re: Some new SOLR features

dnesday, September 17, 2008 11:21 AM To: solr-user@lucene.apache.org Subject: Re: Some new SOLR features On Wed, Sep 17, 2008 at 1:27 PM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: If the configuration code is going to be rewritten then I would like to see the ability to dynamic

Re: Some new SOLR features

g file is touched, load it. When a >>> configuration disappears, unload it. This model works very well for >>> servlet >>> containers. >>> >>> Lance >>> >>> -Original Message- >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTEC

Re: Some new SOLR features

> multi-core allows you to instantiate a completely > new core and swap it for the old one, but it's a bit of a heavyweight > approach. Multi core seems like more of a hack to get around running multiple JVMs. It doesn't seem like the most elegant solutions for most problems because usually the s

Re: Some new SOLR features

08 11:21 AM To: solr-user@lucene.apache.org Subject: Re: Some new SOLR features On Wed, Sep 17, 2008 at 1:27 PM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: If the configuration code is going to be rewritten then I would like to see the ability to dynamically update the configuration a

Re: Some new SOLR features

> That would allow a single request to see a stable view of the > schema, while preventing having to make every aspect of the schema > thread-safe. Yes that is the best approach. > Nothing will stop one from using java serialization for config > persistence, Persistence should not be serialized.

Re: Some new SOLR features

ears, unload it. This model works very well for servlet > containers. > > Lance > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley > Sent: Wednesday, September 17, 2008 11:21 AM > To: solr-user@lucene.apache.org > Subj

Re: Some new SOLR features

Hi Yonik, One approach I have been working on that I will integrate into SOLR is the ability to use serialized objects for the analyzers so that the schema can be defined on the client side if need be. The analyzer classes will be dynamically loaded. Or there is no need for a schema and plain Ja

Re: Some new SOLR features

On Wed, Sep 17, 2008 at 4:50 PM, Henrib <[EMAIL PROTECTED]> wrote: > Yonik Seeley wrote: >> >> ...multi-core allows you to instantiate a completely >> new core and swap it for the old one, but it's a bit of a heavyweight >> approach >> ...a schema object would not be mutable, but >> that one co

Re: Some new SOLR features

L in a Java API, parsers so the current XML could still be used to instantiate those classes. Would that be considered an acceptable first step? -- View this message in context: http://www.nabble.com/Some-new-SOLR-features-tp19494251p19540853.html Sent from the Solr - User mailing list archive at Nabble.com.

RE: Some new SOLR features

] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley Sent: Wednesday, September 17, 2008 11:21 AM To: solr-user@lucene.apache.org Subject: Re: Some new SOLR features On Wed, Sep 17, 2008 at 1:27 PM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: > If the configuration code is going to be rewritt

Re: Some new SOLR features

On Wed, Sep 17, 2008 at 1:27 PM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: > If the configuration code is going to be rewritten then I would like > to see the ability to dynamically update the configuration and schema > without needing to reboot the server. Exactly. Actually, multi-core allows

Re: Some new SOLR features

> Can you define or give an example of what you mean by "hierarchical" queries? Good question, I think Erik Hatcher had more ideas on that. I was imagining joins or sub queries like SQL does. Clearly they won't be efficient, but it's easier than implementing joins (or is it) in SOLR? Joins lim

Re: Some new SOLR features

onfig & schema are shared & can set the > dataDir as a property. > Still a step forward... > > -- > View this message in context: > http://www.nabble.com/Some-new-SOLR-features-tp19494251p19516242.html > Sent from the Solr - User mailing list archive at Nabble.com. > >

Re: Some new SOLR features

On Tue, Sep 16, 2008 at 10:12 AM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: >> SQL database such as H2 > Mainly to offer joins and be able to perform hierarchical queries. Can you define or give an example of what you mean by "hierarchical" queries? A downside of any type of cross-document quer

Re: Some new SOLR features

it does allow to put configurations files in one directory (plus schema & conf can have specific names set for each CoreDescriptor). There actually is a test where the config & schema are shared & can set the dataDir as a property. Still a step forward... -- View this message in context: ht

Re: Some new SOLR features

ryantxu wrote: ... Yes, I would like to see a way to specify all the fieldtypes / handlers in one location and then only specify what fields are available for each core. So yes -- I agree. In 2.0, I hope to flush out configs so they are not monstrous. ... What about using "include" so each

Re: Some new SOLR features

re > not monstrous. > ... > What about using "include" so each core can have a minimal specific configuration and schema & everything else shared between them? Something akin to what's allowed by solr-646. Just couldn't resist :-) Henri -- View this message in

Re: Some new SOLR features

On Sep 16, 2008, at 10:12 AM, Jason Rutherglen wrote: Hello Ryan, SQL database such as H2 Mainly to offer joins and be able to perform hierarchical queries. Also any other types of queries a hybrid SQL search system would offer. This is something that is best built into SOLR rather than Lu

Re: Some new SOLR features

Hello Ryan, > SQL database such as H2 Mainly to offer joins and be able to perform hierarchical queries. Also any other types of queries a hybrid SQL search system would offer. This is something that is best built into SOLR rather than Lucene. It seems like a lot of the users of SOLR work with

Re: Some new SOLR features

Here are my gut reactions to this list... in general, most of this comes down to "sounds great, if someone did the work I'm all for it"! Also, no need to post to solr-user AND solr-dev, probably better to think of solr-user as a superset of solr-dev. 1. Machine learning based suggest

Some new SOLR features

Hello, There are a few features I would like to see in SOLR going forward and I am interested in finding out what other folks thought about them to get a priority list. I believe there are many features that Google and FAST have that SOLR and Lucene will want to implement in future releases. 1.