Thanks Gora. I do not have optimise automatically enabled, but I am new to
Solr so I am not 100% familiar with all the steps that go on.
I will try your suggestion, but I was hoping first that I could get the data
straight from Solr.
thanks, Csaba
--
View this message in context:
On 2/23/2013 12:27 AM, Raja Kulasekaran wrote:
Hi,
I got the exception *Invalid Date String *as I run the crawl against
webpages .
*
*
Each one use their own date format and as a developer we don't have a
control on it. Instead of throwing exception, It should suppose to convert
into a Solr
How are you doing the backup? You have to coordinate with Solr - files may be
changing when you try and copy it, leaving to an inconsistent index. If you
want to do a live backup, you have to use the backup feature of the replication
handler.
- Mark
On Feb 23, 2013, at 3:54 AM, Prakhar Birla
Hi Ankush,
Instructions for subscribing, and other info about the Solr mailing lists, are
here:
http://lucene.apache.org/solr/discussion.html
Steve
On Feb 23, 2013, at 5:47 AM, Ankush Puri ankush@gmail.com wrote:
Hi,
I've started using solr from last day only.I must say it's really an
Thank you Daniel, it is a nice idea.
I wish there was a better solution, but we will go with yours it seems.
(still open for any other idea)
On Feb 22, 2013 7:47 PM, Daniel Collins danwcoll...@gmail.com wrote:
We had something similar to be fair, a cluster information field which was
Hello Cveres.
I know you said the IDs are unique, but having a look at your config,
your id is defined as
CONCAT(CAST('${book_chapter.title}' AS CHAR),'-',CAST(chapter AS
CHAR)) as solr_id
There are many books out there with the same title and most of them
have a chapter titled Introduction.
So,
Hi Alex,
(13/02/23 10:53), alx...@aim.com wrote:
Hello,
I was unable to change pre and post tags for highlighting when
usefastVectorHighlighter is set to true. Changing default tags in
solrconfig.xml works for standard highlighter though. I searched mailing list
and the net with no success.
Ok. I have revisited this issue as deeply as possible using simplistic
unit tests, tossing out indexes, and starting fresh.
A typical Solr document might have a label, e.g. the string inside the
quotes: Node Type. That would be queried, according to what I've
been able to read, as a Phrase
Scenario:
You're submitting a block of text as a query.
You're content to let solr / lucene handing query parsing and tokenziation,
etc.
But you'd like to have ALL eventually produced leaf-nodes in the parse tree
to have:
* Boolean .MUST (effectively a + prefix)
* Fuzzy match of ~1 or ~2
In a
