Is this issue visible for consistently ? I mean are you able to
reproduce this easily?
On Fri, Nov 14, 2008 at 11:15 PM, William Pierce <[EMAIL PROTECTED]> wrote:
> Folks:
>
> I am using the nightly build of 1.3 as of Oct 23 so as to use the replication
> handler. I am running on windows 2003 s
Hi,
Is there a way to specify sort criteria through Solr admin ui. I tried doing it
thorugh the query statement box but it did not work.
Regards,
Sourav
CAUTION - Disclaimer *
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the u
From: Peter Lenahan
I noticed on the solr wiki the comment
" :TODO: we should try to make a DTD for the schema "
Well that wasn't very hard, and an XSD file is much better to work with
than a DTD so I created an XSD file. But I have a few questions about
the test results of applying an XSD sche
Mark,
That sounds great!Good luck with the cleaning :-)
Let me know how I can get a patch --- I'd prefer not do a solr build from
source since we are not Java savvy here:-(
- Bill
--
From: "Mark Miller" <[EMAIL PROTECTED]>
Sent: Saturda
On Nov 15, 2008, at 4:03 AM, Fergus McMenemie wrote:
Thanks for "proving" the stuff for me. I started taking my system
apart
and was considering a fresh install, when I came across an old
lucene jar
file /Library/Java/Extensions/lucene-core-2.3.1.jar which was there
after
a bootcamp tutoria
Okay, I'm fairly certain I've found it. As usual, take a walk and the
solution pops into your head out of the blue.
It looks like Lucene's IndexReader reopen call is not very friendly with
the FSDirectory implementation. If you call reopen and it returns a new
IndexReader, it creates a new ref
Thanks Shalin,
I have added a new field type in my schema as following:
and added my field
After restarting Solr, and making full-import, everything work just fine.
Many thanks.
Regards,
Ahmed
My best wishes,
Regards,
Ahmed Hammad
On Sat, Nov 1
Trunk may actually still hide the issue (possibly), but something really
funky seems to have gone on and I can't find it yet. Do you have any
custom code interacting with solr?
None whatsoever...I am using out-of-the-box solr 1.3 (build of 10/23). I am
using my C# app to http requests to my s
Ive also had the same issues here but when trying to switch to
HTMLStripWhitespaceTokenizerFactor I found that it only removes the
tags but when it comes to all forms of javascript includes in a
document it keeps it all intact so I ended up w/ scripts in the
document text, is there any easy
I think the problem is that DIH catches Exception but not Error so a
StackOverFlowError will slip past it. Normally, the SolrDispatchFilter will
log such errors but the import is performed in a new thread, so the error is
not logged anywhere. However, DIH will not commit documents in this case
(and
I had a similar problem like Giri. I have 17,000 record in one table and DIH
can import only 12464.
After some investigation, I found my problem.
I have a regular expression to strip off html tags form input text, as
following:
The DIH RegEx have stack overflow on the record 17,000 due to erro
Havn't given up, but this has really got me so far. For every path,
FSDirectory allows just one instance of FSDirectory to exist, and it
keeps a ref count of how many have been returned from openDirectory for
a given path. An FSDirectory will not actually be closed unless all
references to it a
Mark,
Thanks for your help and lucid exposition of what may be going onI will
await to hear from you before I plough ahead with the latest trunk bits
Best regards,
-- Bill
--
From: "Mark Miller" <[EMAIL PROTECTED]>
Sent: Saturday, Novem
Hang on. The more I look at this, the more I am thinking that was not
the problem. Directories are pretty strictly managed by Lucene at the
moment, and it should actually be pretty difficult to have one closed
out from under you. They are singletons and reference counted. The
IndexReader would
Mark,
Thanks for your response --- I do appreciate all you volunteers working to
provide such a nice system!
Anyway, I will try the trunk bits as you said. The only problem is that
the later the trunk I use from 1.3, the more of post 1.3 capability I get.
And I feel somewhat exposed runni
Erik,
Thanks for "proving" the stuff for me. I started taking my system apart
and was considering a fresh install, when I came across an old lucene jar
file /Library/Java/Extensions/lucene-core-2.3.1.jar which was there after
a bootcamp tutorial! It was on both my tiger and leopard machines as wel
16 matches
Mail list logo
