Hi,
I didn't follow the whole thread closely, but if the goal is to have
information about the original queries entered by users, why not just
look at Solr log or something like Sematext Search Analytics -
http://sematext.com/search-analytics/index.html ?
Otis
Performance Monitoring - http://sema
I have updated the db-data-config.xml to introduce the templateTransformer
and generate a common field (docId) with other data-config files.
db-data-config.xml :
schema.xml:
I take back that suggestion since the highlighter cares nothing about the
actual source query.
If you really want the source terms (before analysis), you probably need to
subclass the desired query parser and have an override method that saves the
source term just before it is analyzed. That's
Add &debugQuery=true to your query request and look at the timings for the
various search components. That should be the first step in figuring out
where to focus your attention for performance improvement.
-- Jack Krupansky
-Original Message-
From: 蒋明原
Sent: Saturday, September 15,
Correcting myself, for #4, Solr doesn't "analyze" string fields such as the
unique key field, but... a transformer or other logic, say in DIH, that
constructs the document key values might behave differently between Solr 1.3
and 3.6. Maybe there was a bug in 1.3 that caused distinct keys to map
Try some queries in both the old and the new and identify some documents
that appear in one and not the other. Then examine a couple of those docs in
detail one field at a time and see if anything is suspicious. Take each
field value and enter it into the Solr Admin Analysis page to see how Solr
I assume you're talking about facets here. Use a series of
facet queries, and use the "key" trick. See:
http://wiki.apache.org/solr/SimpleFacetParameters#key_:_Changing_the_output_key
Best
Erick
On Sat, Sep 15, 2012 at 4:56 AM, Anupam Bhattacharya
wrote:
> How to fetch results for a indexed fiel
You can also use an edismax style handler to automatically search
more than one field given a search term.
Best
Erick
On Fri, Sep 14, 2012 at 8:47 AM, Jack Krupansky wrote:
> As of Solr 3.6, defaultSearchField is deprecated:
>
> * SOLR-2724: Specifying and defaultOperator="..."/> in
> schema.
SolrCloud should be indistinguishable from Solr w/ replication in
terms of functionality, so this should work just fine.
SolrCloud should actually (and I'm kind of guessing here) give _better_
consistency than Solr w/ replication. Consider 4 slaves all with a polling
interval of 10 minutes that ju
I'm not quite sure I follow (and I know nothing about how the highlighter
works with Japanese).
But, you don't highlight fieldTypes, you highlight individual fields and it's
just a comma (or space) separated list. You can set these either on the URL or
in the solrconfig.xml file for your particula
Stab in the dark... This looks like you're somehow getting the wrong
Groovy jars. Can you
print out the Groovy version as a test? Perhaps you have one groovy
version in your
command-line and copied a different version into the libraries Solr knows about?
Because this looks like a pure Groovy error
i have the same problem.and did you got some good idea? wish you can share
it.thanks
在 2012-2-18 上午8:52，"Bryan Loofbourrow" 写道：
> Apologies. I meant to type “1.4 TB” and somehow typed “1.4 GB.” Little
> wonder that no one thought the question was interesting, or figured I must
> be using Sneakerne
I checked highlighter works(DefaultSolrHighlighter).
Can this API re-parse the search terms("q parameter") of Edismax Queries?
If it can do, I would like to reuse API of Solr.
Regards.
2012/9/14 Fumio Takayama
> Hi, Jack
>
> >Are you trying to re-parse the queries that you extract from the lo
How to fetch results for a indexed field of date format in the facet
section as a group in the below format from SOLR ?
Today's (10)
Last 7 Days (20)
Yesterday (30)
Thursday (40)
Wednesday (50)
Tuesday (60)
Monday (70)
Sunday (80)
last Week (90)
Two Week Ago (100)
Last Month (110)
Two Months Ago (
14 matches
Mail list logo
