I have been using Solr 1.4 on Tomcat and had been making use of the current
working directory unknowingly. I programmatically create cores as needed. I
create a core via the CoreAdmin by passing in the core name ( CORE_01 ),
instancedir ( CORE_01 ), config ( solr/conf/solrconfig.xml ), and sc
rameters allowed in a POST.
>
> On Thu, Jan 21, 2010 at 7:37 AM, Joe Kessel wrote:
> >
> > Using Solr 1.4 and the StreamingUpdateSolrServer on Weblogic 10.3 and get
> > the following error on commit. The data seems to load fine, and the same
> > code works fine w
Using Solr 1.4 and the StreamingUpdateSolrServer on Weblogic 10.3 and get the
following error on commit. The data seems to load fine, and the same code
works fine with Tomcat. On the client side an Internal Server Error is
reported.
Thanks,
Joe
weblogic.utils.NestedRuntimeException:
> Unless there is a bug in Lucene's NativeFSLock (and it doesn't look
> > like it), the only way I see that this could happen is if there were
> > multiple instances of that class loaded in different classloaders.
> > Are you using any kind of plugins?
> >
> &
t; Could you open a JIRA issue for this?
>
> -Yonik
> http://www.lucidimagination.com
>
>
>
> On Fri, Jan 15, 2010 at 5:50 PM, Joe Kessel wrote:
> >
> > I have an instance of Solr that won't start since I have added the
> > replication startup. I am using Sol
I have an instance of Solr that won't start since I have added the replication
startup. I am using Solr 1.4 and only see
this with my index that contains 200k documents with a total size of 400MB.
Removing the replicate after startup and the instance starts without error. We
found that we n
Hi,
In my environment I create cores on the fly, then replicate the core to all of
the slaves. I first create the core on the master and persist the solr.xml via
the CoreAdmin API. I then do the same on each of my slaves. After loading /
committing / optimizing the data on the master I sen
I finally got around to testing the patch and it works well.
Thanks,
Joe
> Date: Mon, 23 Nov 2009 12:32:46 -0800
> From: hossman_luc...@fucit.org
> To: solr-user@lucene.apache.org
> Subject: RE: UTF-8 Character Set not specifed on OutputStreamWriter in
> StreamingUpdateSolrServer
>
>
>
I do something very similar and it works for me. I noticed on your URL that
you have a mixed case fetchIndex, which the request handler is checking for
fetchindex, all lowercase. If it is not that simple I can try to see the exact
url my code is generating.
Hope it helps,
Joe
> From: e
amWriter in
> StreamingUpdateSolrServer
> From: shalinman...@gmail.com
> To: solr-user@lucene.apache.org
>
> On Wed, Nov 18, 2009 at 6:56 AM, Joe Kessel wrote:
>
> >
> > While trying to make use of the StreamingUpdateSolrServer for updates with
> > the release
While trying to make use of the StreamingUpdateSolrServer for updates with the
release code for Solr.14 I noticed some characters such as é did not show up in
the index correctly. The code should set the CharsetName via the constructor
of the OutputStreamWriter. I noticed that the Commons
New to Solr, not so new to search. I have an existing data model that I am
pushing into a Solr index. For example, I am indexing a product which includes
product brochures in multiple locales. So this single Solr document contains
multiple text fields which require linguistics analyzers. Th
12 matches
Mail list logo
