This is both an FYI for the list so the issue gets documented and a suggestion
for the developers. I thought about a JIRA, and would be happy to submit one,
but the issue is pretty environment-specific, so I have not done so at this
point.
In testing Solr 3.3 under WebSphere Application Server
/ & the test/ patches.
> > http://www.nabble.com/file/7971/solr-test.patch solr-test.patch
> > http://www.nabble.com/file/7972/solr-src.patch solr-src.patch
> >
> > This being my first attempt at a contribution, I will humbly welcome any
> > comment.
> > Regards,
> > Henri
> >
>
> --
> View this message in context:
http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10106126
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
/www.nabble.com/file/7972/solr-src.patch solr-src.patch
>
> This being my first attempt at a contribution, I will humbly welcome any
> comment.
> Regards,
> Henri
>
--
View this message in context:
http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10106126
Sent from the Solr - User mailing list archive at Nabble.com.
mbly welcome any
> comment.
> Regards,
> Henri
>
--
View this message in context:
http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10106126
Sent from the Solr - User mailing list archive at Nabble.com.
I'm sorry to say I am *way* behind on my patch reading (and moving into my
new place this weekend where i have no net access isn't going to help) so
i can't comment on the technique (or even style) of this patch ... but if
you could do peopel a favor and open a Jira issue and post it there for
peo
e a great idea, and potentially very useful for my company.
>
> Can you explain a bit about how you would configure the various solr/home
> paths, and how the different indexes would be accessed by clients?
>
> Thanks!
>
> - Michael
>
--
View this message in context:
htt
/Multiple-Solr-Cores-tf3608399.html#a10083581
Sent from the Solr - User mailing list archive at Nabble.com.
mbly welcome any
comment.
Regards,
Henri
--
View this message in context:
http://www.nabble.com/Multiple-Solr-Cores-tf3608399.html#a10082201
Sent from the Solr - User mailing list archive at Nabble.com.
static Singletons i (and many others i suspect) would be
> extremely gratefull .. both for how much it would improve hte reusability
> of Solr in embedded situatiosn like this, but also for how it would
> (hopefully) make hte code eaier to follow for future developers.
>
>
> -Hoss
>
>
>
--
View this message in context:
http://www.nabble.com/Embedding-Solr-vs-Lucene%2C-multiple-Solr-cores--tf3572324.html#a10020669
Sent from the Solr - User mailing list archive at Nabble.com.
: but does not want to deal with the application itself, leaving the 'business
: users' side administer it. Even if there is a dedicated Tomcat for the main
: app, IT will not let the 'business users' install other applications (scope
: of responsibility, code versus data, validation procedures, e
bed Solr but refactor 'some' of its core, assuming it is correct to
>> see
>> one Solr core as the association of one schema & one conf.
>>
>> There have been a few threads about multiple indexes and/or
>> multiple/reloading schemas.
>> From what
gathered, one solution stems from the 'multiple webapp
instances
deployment' and implies 'extracting' the static instance (at least the
SolrCore) & thus host multiple Solr cores in one webapp.
Obviously, the operations (queries/add/delete doc) would need to carry
which
core they
On 4/13/07, Henrib <[EMAIL PROTECTED]> wrote:
I'm trying to choose between embedding Lucene versus embedding Solr in one
webapp.
In Solr terms, functional requirements would more or less lead to multiple
schema & conf (need CRUD/generation on those) and deployment constraints
imply one webapp i
es and/or
multiple/reloading schemas.
>From what I gathered, one solution stems from the 'multiple webapp instances
deployment' and implies 'extracting' the static instance (at least the
SolrCore) & thus host multiple Solr cores in one webapp.
Obviously, the operations
14 matches
Mail list logo
