Erick Erickson wrote:
It's especially helpful if you can take a bit of time to pare away
all the unnecessary stuff in your example files and/or comment
what you think the important bits are.
entered as SOLR-1782 in jira
--
View this message in context:
Xavier Schepler wrote:
for example, concept_user_*, and I will have maybe more than 200 users
using this feature.
I've done tests with many hundred dynamically created fields (ie foo_1 thru
f_400). generally speaking, I havent noticed any noticeable performance
issues from having that
I have been able to apply and use the solr-236 patch (field collapsing)
successfully.
Very, very cool and powerful.
My one comment/concern is that the collapseCount and aggregate function
values in the collapse_counts list only represent the collapsed documents
(ie the ones that are not shown
Joe Calderon-2 wrote:
you can do that very easily yourself in a post processing step after
you receive the solr response
true (and am already doing so).
was thinking that having this done as part of the field collapsing code, it
might be faster than doing so via post processing (ie no
I got latest trunk (feb3/2010) using svn and applied solr-236.
did an ant clean and it seems to build fine with no errors or warnings.
however, when I start solr I get an error (here is a snippet):
SEVERE: org.apache.solr.common.SolrException: Error loading class
'org.apache.so
Thanks Lance, I appreciate your response.
I know what a DIH is and have already written custom transformers. I just
misunderstood your response to my message (I wasnt aware that we could use
JS to create transformers).
Anyhow, my intent is to change the tool (create a variation of hsin to
Lance Norskog-2 wrote:
If you use the DataImportHandler you can add your own Javascript code to
do the degree-radian conversion.
Thx Lance, but I am not sure what you mean
--
View this message in context:
I dont believe there is any way to link values in one multivalue field to
values in other multivalue fields.
Re where each doc contains the customer info and info for ALL products that
the customer might have (likely done via dynamicfields):
one thing you might want to consider is that this
Grant Ingersoll-6 wrote:
...
Yep. Also note that I added deg() and rad() functions, but for the most
part is probably better to do the conversion during indexing.
...
as it is not possible for me to convert my data from deg to rad during
import (since queries are done using degrees),
I saw an interesting thread in the solr-dev forum about multiple fields per
fieldtype (https://issues.apache.org/jira/browse/SOLR-1131)
from the sounds of it, it might be of interest and/or use in these types of
problems; for your example, you might be able to define a fieldtype that
houses the
Grant Ingersoll-6 wrote:
...
Yep. Also note that I added deg() and rad() functions, but for the most
part is probably better to do the conversion during indexing.
...
Thanks Grant. I hadnt seen the deg and rad functions. Conversion would be
difficult since I typically work with
I was looking at functionqueries, and noticed that:
1. if I use the sum functionquery, the score in the results is the sum of
the values I want to sum (all well and good and expected):
gdeconto wrote:
...
is there some way to convert the hsin value to distance?
...
I just noticed that the solr wiki states Values must be in Radians and all
my test values were in degrees.
--
View this message in context:
http://old.nabble.com/how-is-score-computed-with-hsin
I am looking at executing a single solr query and having solr automatically
execute one (or more) additional solr queries (inside solr) as a way to save
some overhead/time. I am doing this by overriding the SearchComponent. My
code works and I was looking at ways to optimize the code.
the
tpunder wrote:
Maybe I misunderstand what you are trying to do (or the facet.query
feature). If I did an initial query on my data-set that left me with the
following questions:
...
Scenario:
1. I have a query I want to execute; I would be using the results and facets
returned
2. I also have a couple of dozen other queries that are closely related to
the first query and to the facets returned by that query. For each query, I
would only be using the total number of results
tpunder wrote:
Could you use the facet.query feature
(http://wiki.apache.org/solr/SimpleFacetParameters#facet.query_:_Arbitrary_Query_Faceting)
to reduce it to 2 queries?
So you'd:
1. Send solr the first query
2. Solr executes and returns the query to you
3. You then use the facet
awesome. Thanks for figuring this out guys
wojtekpia wrote:
Good catch. I was testing on a nightly build from mid-July. I just tested
on a similar deployment with nightly code from Oct 5th and everything
seems to work.
My mid-July deployment breaks on sints, integers, sdouble,
my apologies, you are correct; I put the stack trace in an edit of the post
and not in the original post.
re version info:
Solr Specification Version: 1.3.0.2009.07.08.08.05.45
Solr Implementation Version: nightly exported - yonik - 2009-07-08 08:05:45
NOTE: I have some more info on this NPE
Thanks for the reply hossman.
I have successfully created a custom QParserPlugin that implements some
special syntax to help me handle my many dynamic fields.
The syntax looks something like this:
http://127.0.0.1:8994/solr/select...@fn:(1,2,3,4)
Had to create java code to extract the
I did check the other posts, as well as whatever I could find on the net but
didnt find anything.
Has anyone encountered this type of issue, or is what I am doing (extending
QParserPlugin) that unusual??
gdeconto wrote:
...
one thing I noticed is that if I append debugQuery=true
Hi Yonik;
My original post (
http://www.nabble.com/how-can-I-use-debugQuery-if-I-have-extended-QParserPlugin--tt25789546.html
http://www.nabble.com/how-can-I-use-debugQuery-if-I-have-extended-QParserPlugin--tt25789546.html
) has the stack trace. =^D
I am having trouble reproducing this issue
in a previous post, I asked how I would go about creating virtual function in
my solr query; ie: http://127.0.0.1:8994/solr/select...@myfunc(1,2,3,4)
I was trying to find a way to more easily/cleanly perform queries against
large numbers of dynamic fields (ie field1, field2, field3...field99).
sorry if this is a very simple question, but I am stuck (and online searches
for this info havent been fruitful).
Lets say that, in certain circumstances, I want to change the field names
and/or field query values being passed to SOLR.
For example, lets say my unmodified query is
Note that there is a similar question in
http://www.nabble.com/TermsComponent-to25302503.html#a25312549
http://www.nabble.com/TermsComponent-to25302503.html#a25312549
--
View this message in context:
I dont have that answer as I was asking a general question, not one for a
specific situation I am encountering).
what I am essentially asking for is: is there a short, simple and generic
method/technique to deal with large numbers of dynamic fields (rather than
having to specify each and every
Thanks Avlesh.
I was only thinking of something 'like' function queries (since they
appeared to have similar behavior).
Agree that custom QueryParser is looking like my only choice. Now have to
figure out how to do that :-)
Avlesh Singh wrote:
I don't think you need function queries
Can someone point me in the general direction of how to create a custom
queryparser that would allow me to create custom query commands like this:
http://localhost:8994/solr/select?q=myfunction(‘Foo’, 3)
or point me towards an example?
note that the actual functionality of myfunction is not
say I have a dynamic field called Foo* (where * can be in the hundreds) and
want to search Foo* for a value of 3 (for example)
I know I can do this via this:
http://localhost:8994/solr/select?q=(Foo1:3 OR Foo2:3 OR Foo3:3 OR …
Foo999:3)
However, is there a better way? i.e. is there some way
thx for the reply.
you mean into a multivalue field? possible, but was wondering if there was
something more flexible than that. the ability to use a function (ie
myfunction) would open up some possibilities for more complex searching and
search syntax.
I could write my own query parser with
('Bar', 1) AND (myfunction('Etc', 7))
gdeconto wrote:
say I have a dynamic field called Foo* (where * can be in the hundreds)
and want to search Foo* for a value of 3 (for example)
I know I can do this via this:
http://localhost:8994/solr/select?q=(Foo1:3 OR Foo2:3 OR Foo3:3 OR …
Foo999
Yonik Seeley-2 wrote:
It's probably the case that every search engine out there is faster
than Solr at one thing or another, and that Solr is faster or better
at some other things.
I prefer to spend my time improving Solr rather than engage in
benchmarking wars... and Solr 1.4 will
32 matches
Mail list logo
