allMessageContent:test;subject+asc
there should be a space between subject and asc,
try: http://host/select?q=allMessageContent:test;subject%20asc
+ is supposed to become a space, but it looks like it is staying "+"
On Mar 6, 2007, at 9:50 PM, Yonik Seeley wrote:
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
From what I can see in the logs, these are both invoked after the
commit. However, the query times after a commit are still slow
(around 20 seconds).
Your warming script didn't do any sorts.
Wh
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
From what I can see in the logs, these are both invoked after the
commit. However, the query times after a commit are still slow
(around 20 seconds).
Your warming script didn't do any sorts.
Why don't you also show the part of the log with the
Oops, my bad I didn't see either 186 or 187 before entering 188. :-)
-- j
On 3/6/07, Graham Stead <[EMAIL PROTECTED]> wrote:
Apologies in advance if SOLR-187 and SOLR-188 look the same -- they are
the
same issue. I have been using adjusted scripts locally but hadn't used
Jira
before and wasn'
Apologies in advance if SOLR-187 and SOLR-188 look the same -- they are the
same issue. I have been using adjusted scripts locally but hadn't used Jira
before and wasn't sure of the process. I decided to figure it out after
answering Gola's question this morning...then saw that Jeff had mentioned a
This issue has been logged as:
https://issues.apache.org/jira/browse/SOLR-188
A patch file is included for those who are interested. I've unit tested in
my environment, please validate it for your own environment.
cheers,
j
On 3/5/07, Jeff Rodenburg <[EMAIL PROTECTED]> wrote:
Thanks Hoss.
MySQL has a TIMESTAMP field that can autoupdate everytime something
changes... i've never used it, but that may be a place to look.
alternativly you could add a TRIGGER to automatticaly dump stuff to a
bucket when it changes and clear the bucket when you index
On 3/6/07, Debra <[EMAIL PROTECTED
I would like to avoid such a field in case tables are updated in programs
not under my control + any program that updates these tables has to add
logic for updating this field.
Sergey Polzunov-2 wrote:
>
> additional field in your DB as flag? 1 - dirty, 0 - clean.
>
> Debra wrote:
>> Hi all
Yonik Seeley wrote:
>
> HTMLStripWhitespaceTokenizerFactory works in two phases...
> HTMLStripReader removes the HTML and passes the result to
> WhitespaceTokenizer... at that point, Tokens are generated, but the
> offsets will correspond to the text after HTML removal, not before.
>
> I did it
Thank you, your suggestion looks like the way to go...
Mike Klaas wrote:
>
> On 3/6/07, Debra <[EMAIL PROTECTED]> wrote:
>>
>> I want to add a suffix to my fields names to use the dynamic fields
>> feature.
>> Is there a way to save the field name without the suffix so users can
>> search
>> by
On Mar 6, 2007, at 1:55 PM, Yonik Seeley wrote:
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
I'm looking for some tips / suggestions around reducing the query
time for Solr after I've post'ed a commit request. My Lucene index
contains around 2,000,000 documents, and I have a job that
per
additional field in your DB as flag? 1 - dirty, 0 - clean.
Debra wrote:
Hi all,
This is not a direct solr issue but I need it for indexing.
Is there a way to check if a database record changed since the last index
(with out using a specail flag field that has to be set any-where the record
is
On 3/6/07, Debra <[EMAIL PROTECTED]> wrote:
I want to add a suffix to my fields names to use the dynamic fields feature.
Is there a way to save the field name without the suffix so users can search
by field with plain field name?
No, and I'm not sure that it is possible. Solr needs to know t
Hi all,
This is not a direct solr issue but I need it for indexing.
Is there a way to check if a database record changed since the last index
(with out using a specail flag field that has to be set any-where the record
is updated). I would like to re-index only records that changed.
TIA
Debra
-
Thanks Ryan for the quick reply and for your contribution to solr.
I did write some code to generate a xml document from a sql query (generates
a general xml file that with few changes to a properties file will generate
a solr add xml document), so I'll use that for the time being.
Maybe we can
SOLR-103 is waiting for SOLR-139 to solidify before i post more updates...
I have it running successfully, but it requires too many other patches
to suggest trying to get it running unless you are up for a bit of
work. If you are, i can easily post an update.
About the schema... SOLR-103 uses t
What is the status of the SQL update?
Should all database fields used in sql updates be added to schema.xml before
running the sql update?
--
View this message in context:
http://www.nabble.com/SQL-Update-tf3358303.html#a9341018
Sent from the Solr - User mailing list archive at Nabble.com.
I want to add a suffix to my fields names to use the dynamic fields feature.
Is there a way to save the field name without the suffix so users can search
by field with plain field name?
--
View this message in context:
http://www.nabble.com/Saving-dynamic-field-name-without-dynamic-extension-t
On 3/6/07, Kaan Erdener <[EMAIL PROTECTED]> wrote:
I'm looking for some tips / suggestions around reducing the query
time for Solr after I've post'ed a commit request. My Lucene index
contains around 2,000,000 documents, and I have a job that
periodically removes artibrary documents from Lucene a
hello,
I'm looking for some tips / suggestions around reducing the query
time for Solr after I've post'ed a commit request. My Lucene index
contains around 2,000,000 documents, and I have a job that
periodically removes artibrary documents from Lucene and replaces
them with fresh copies f
Yep, the snapinstaller was failing and it was the same problem as Jeff
posted this morning about bin/optimize, but this time with bin/commit,
not using ${webapp_name}.
I fixed that and worked normally. I've submitted a bug to JIRA as I
think Jeff didn't submit it yet
Mm now I see your other
I forgot to mention that the admin page (solr/admin/stats.jsp) is an
excellent way to see when the last searcher was opened. After running
commit, you should see update to the openedAt and registeredAt timestamps,
e.g.,:
openedAt : Tue Mar 06 08:14:19 PST 2007
registeredAt : Tue Mar 06 08:15:55 PS
Hi Galo,
The snapinstaller actually performs a commit as its last step, so if that
didn't work, it's not surprising that running commit separately didn't work,
either.
I would suggest running the snapinstaller and/or commit scripts with the -V
option. This will produce verbose debugging informati
: getRequestHandlers() would be equivolent to:
: getRequestHandlers( SolrRequestHandler.class )
:
: We will need some way to ask what is registered without knowing the
: path it is registered to.
getting instances by class seems like a pretty special case situation ...
i'd rather not add a bunch
Hi,
I've been testing index replication and after snappulling and installing
the latest version of the master index, if i run a query on the slave i
don't get any results back (tried a commit in despair, which didn't work
either). If I restart the web server (tomcat) then it works.
Am I miss
On 3/6/07, mike topper <[EMAIL PROTECTED]> wrote:
when inserting it it seems like nothing happens ie when i do a query
here is the response for a test description:
himynameistopperand this blahblah is a
test
The tag stripping happens during the analysis phase, and affects what
gets index
I'm trying to use the html stripping factory in order to strip html tags
from my description field when indexing.
I added this fieldtype:
It will probably turn out to be a hardware problem - a bad RAM chip. I
removed it and today I will test Solr again to make sure everything is fine.
On 3/5/07, Bill Au <[EMAIL PROTECTED]> wrote:
Seems like this maybe a JVM bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6500147
http://
28 matches
Mail list logo
