Lance, I didn't use widcard at all. I use only this, the difference is
quoted or not.
q2=*apartment*
q1=*apartment*
*
*
On Tue, Jul 3, 2012 at 12:06 PM, Lance Norskog goks...@gmail.com wrote:
q2=*apartment*
q1=*apartment*
These are wildcards
On Mon, Jul 2, 2012 at 8:30 PM, Chamnap Chhorn
Hi,
As part of my bachelor thesis I'm trying to archive NRT with Solr 3.6.
I've came up with a basic concept and would be trilled if I could get
some feedback.
The main idea is to use two different Indexes. One persistent on disc
and one in RAM. The plan is to route every added and modified
Hello!
Your query suggests that you are sorting on the 'name' field instead
of the latlng field (sort=name +asc).
The question is what you are trying to achieve ? Do you want to sort
your documents from a given geographical point ? If that's the case
you may want to look here:
Hi,
Thanks for reply.
I want to sort my docs on name field, it is working well only if I have all
fields populated well.
But my latlng field is optional, every doc will not have this value. So those
docs are not getting sorted.
Regards
Harshvardhan Ojha
-Original Message-
From: Rafał
Hello!
But the latlng field is not taken into account when sorting with sort
defined such as in your query. You only sort on the name field and
only that field. You can also define Solr behavior when there is no
value in the field, but adding sortMissingLast=true or
sortMissingFirst=true to your
I found it, the default order is by ASCII code (which is not alphabetical
order).
--
View this message in context:
http://lucene.472066.n3.nabble.com/Facet-Order-when-the-count-is-the-same-tp3992471p3992734.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
I have added field name=latlng indexed=true stored=true
sortMissingLast=false sortMissingFirst=false/ to my schema.xml, although I
am searching on name field.
It seems to be working fine. What is its default behavior?
Regards
Harshvardhan Ojha
-Original Message-
From: Rafał Kuć
Hi,
You might want to take a look at Solr's trunk (very soon to be 4.0.0
alpha release), which already has a near-real-time solution (using
Lucene's near-real-time APIs).
Lucene has NRTCachingDirectory (to use RAM for small / recently
flushed segments), but I don't think Solr uses it yet.
Mike
Chamnap,
I have a hunch you can get away with not using *s.
Michael Della Bitta
Appinions, Inc. -- Where Influence Isn’t a Game.
http://www.appinions.com
On Tue, Jul 3, 2012 at 2:16 AM, Chamnap Chhorn chamnapchh...@gmail.com wrote:
Lance, I
Just adding to the below-- If there is a field(say X) which is not populated
and in the query I am not sorting on this particular field but on another field
(say Y) still the result ordering would depend on X .
Infact in the below problem mentioned by Harsh making X as
sortMissingLast=false
Right. But note two things:
1 the filters were made MultiTermAware based on doing no harm.
When it comes to this kind of change, we wanted to be sure we
weren't messing things up. If you are certain that other filters would
be OK if they were MultiTermAware, let us know and we can make
3 July 2012, Apache Solr™ 4.0-alpha available
The Lucene PMC is pleased to announce the release of Apache Solr 4.0-alpha.
Solr is the popular, blazing fast, open source NoSQL search platform from
the Apache Lucene project. Its major features include powerful full-text
search, hit highlighting,
Thanks Erik. If anyone else has any ideas about the NoSuchFieldError issue
please let me know. Thanks!
-Briggs
On Mon, Jul 2, 2012 at 6:27 PM, Erik Hatcher erik.hatc...@gmail.com wrote:
Interestingly, I just logged the issue of it not showing the right error
in the UI here:
Also, I forgot to include this before, but there is a client side error
which is a failed 404 request to the below URL.
http://localhost:8983/solr/null/admin/system?wt=json
On Tue, Jul 3, 2012 at 8:45 AM, Briggs Thompson w.briggs.thomp...@gmail.com
wrote:
Thanks Erik. If anyone else has any
same problem here:
https://mail.google.com/mail/u/0/?ui=2view=btopver=18zqbez0n5t35q=tomcat%20v.kisselmannqs=truesearch=queryth=13615cfb9a5064bdqt=kisselmann.1.tomcat.1.tomcat's.1.v.1cvid=3
Wow! I didn't know 4.0 alpha was released today. I think I will just get
that going. Woo!!
On Tue, Jul 3, 2012 at 9:00 AM, Vadim Kisselmann v.kisselm...@gmail.comwrote:
same problem here:
OK, this appears to be something with the currency type. It works fine for
regular float fields. I can't get the multiValued currency types to work with
range queries. Don't quite know what I was doing when I thought they
_did_ work.
One work-around I think, if you are using a single currency USD
Hey Vadim
Right now JIRA is Down for Maintenance, but afaik there was another comment
asking for more informations. I'll check Eric's Issue today or tomorrow and see
how we can handle (and hopefully fix) that.
Regards
Stefan
On Tuesday, July 3, 2012 at 4:00 PM, Vadim Kisselmann wrote:
same
This site is pretty cool also, just filter on solr-user like this:
http://markmail.org/search/?q=list%3Aorg.apache.lucene.solr-user
-Original Message-
From: Chris Hostetter [mailto:hossman_luc...@fucit.org]
Sent: Monday, July 02, 2012 5:34 PM
To: solr-user@lucene.apache.org
Subject: Re:
I had the same problem with jetty. It turned out that broken pipe happens when
application disconnects from jetty. In my case I was using php client and it
had 10 sec restriction in curl request. When solr takes more than 10 sec to
respond, curl automatically disconnected from jetty.
Hope
I also had this problem on solr/tomcat and finally saw the errors were coming
from my application side disconnecting from solr after a timeout. This was
happening when solr was busy doing an optimize and thus not responding quickly
enough. Initially when I saw this in the logs, I was quite
Hi Stefan,
sorry, i overlooked your latest comment with the new issue in SOLR-3238 ;)
Should i open an new issue? I´m not testing it with newer
trunk-versions about a couple of months because
solr cloud with an external ZK and tomcat fails too, but i can do it
and post all the errors which i find
Some interesting findings over the last hours, that may change the context of
this discussion...
Due to the nature of the application, I need the ability to fire off individual
ADDs on several different entities at basically the same time. So, I am
making 2-4 Solr ADD calls within 100ms of
A DIH request handler can only process one run at a time. So if DIH is still
in process and you kick off a new DIH full-import it will silently ignore the
new command. To have more than one DIH run going at a time it is necessary
to configure more than one handler instance in sorlconfig.xml.
Well that little bit of knowledge changes things for me, doesn't it? I
appreciate your response very much. Without knowing that about the DIH, I
attempted to have my DIH handler handle all circumstances, namely the batch,
scheduled job, and immediate/NRT indexing. Looks like I'm going to
Sorry can't answer your question directly. However map scale may render
this very tricky or even redundant.
UI may be a better place for a solution rather than the data. Take a look
at https://developers.google.com/maps/articles/toomanymarkers for lots of
options
lee c
On 3 July 2012 03:49,
On Tuesday, July 3, 2012 at 8:10 PM, Vadim Kisselmann wrote:
sorry, i overlooked your latest comment with the new issue in SOLR-3238 ;)
Should i open an new issue?
NP Vadim, yes a new Issue would help .. all available Information too :)
Chamnap:
I've seen various e-mail programs put the asterisk in for terms that
are in bold face.
The queries you pasted have lots of * characters in it, I suspect
that they were just
things you put in bold in your original, that may be the source of the
confusion about
whether you were using
Mike:
Have you considered using one (or several) SolrJ clients to do your
indexing? That can give you a finer control granularity than DIH. Or
even do your NRT with SolrJ or
Here's an example program, you can take out the Tika stuff pretty easily..
Best
Erick
On Tue, Jul 3, 2012 at 3:35
Good afternoon.
I downloaded Solandra from github and trying to run Solandra. I get an
exception about creating seed_provider.
I have attached cassandra.yaml for reference. Could you please let me know
what could be the problem with yaml.
Thanks
Venkat
I haven't, but will consider those alternatives. I think right now I'm going
to go w/ a hybrid approach, meaning my scheduled and full updates will continue
to use the DIH, as those seem to work really well. My NTR indexing needs will
be handled via the JSON processor. For individual updates
Hello!
I think you should ask that question on Solandra mailing list as your issue is
not connected directly to Solr, at least in my opinion :)
--
Regards,
Rafał Kuć
Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch - ElasticSearch
Good afternoon.I downloaded Solandra from github
So, this was the solution, sorry to post it so late, just in case it helps
anyone:
/etc/init.d/ntp stop; date; date `date +%m%d%H%M%C%y.%S`; date;
/etc/init.d/ntp start
And tomcat magically switched from 100% CPU to 0.5% :)
From:
Jack, can you please explain this in some more detail? Such as how to write
my own search component to modify request to add bq parameter and get
customized result back?
--
View this message in context:
Hi
I am new to nutch and was trying it out using the instructions here
http://wiki.apache.org/nutch/NutchTutorial
After changing the schema.xml of Solr to what Nutch has I keep getting this
error..
I am unable to start the solr server.
org.apache.solr.common.SolrException: undefined field
Either add the text field back to the schema (consult the Solr example
schema) or remove or change all references to text in solrconfig.xml to
some other field that you do still have in the schema.
-- Jack Krupansky
-Original Message-
From: 12rad
Sent: Tuesday, July 03, 2012 7:30 PM
Hi ,
I'm using solr cell(solrj) to index plain text files, but am encountering
IllegalCharsetNameException: Could you please point out if anything should
be added in schema.xml file. I could index the other mime types
efficiently. I gave the field type as text.
fieldType name=text
I had a similar problem so I submitted this patch:
https://issues.apache.org/jira/browse/SOLR-2351
I haven't applied this to trunk in a while but my goal was to ensure
that bf parameters were passed down and respected by the MLT handler.
Let me know if this works for you or not. If there is
So couple questions on this (comment first then question):
1) I guess you can't have four combinations b/c
index=false/stored=false has no meaning?
2) If you set less fields stored=true does this reduce the memory
footprint for the document cache? Or better yet, I can store more
documents in the
39 matches
Mail list logo
