The issue is the HTTP caching feature of Solr, for better or worse in
this case. It confuses me often when I hit this myself. Try hitting
that URL with curl and you'll see it change since no caching is
involved client-side.
For sanity's sake you can turn off HTTP caching in solrconfig.xml:
<httpCaching never304="true"/>
On Apr 24, 2008, at 7:28 PM, Chris Harris wrote:
No luck with control-R, or with F5. I'm on Windows here if you think
that's a potential problem.
For now I've found a silly workaround: If
http://localhost:8983/solr/dataimport?command=status
doesn't work, then you can replace "command=status" with almost
anything at all and then you'll be able to get a fresh view of the
status. (This is because the handler takes "status" as the default
command.) For example, both the following also give the current
status:
http://localhost:8983/solr/dataimport?command=statusXXX
http://localhost:8983/solr/dataimport?abcdefg
If what I put after the question mark is something I haven't tried
before, then I get a fresh status update. This works as long as I
don't pick a URL that's identical to one I've tried recently.
On Thu, Apr 24, 2008 at 3:13 PM, Otis Gospodnetic
<[EMAIL PROTECTED]> wrote:
Chris - what happens if you hit ctrl-R (or command-R on OSX)?
That should bypass the browser cache.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
From: Chris Harris <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Thursday, April 24, 2008 6:04:05 PM
Subject: Caching of DataImportHandler's Status Page
I'm playing with the DataImportHandler, which so far seems pretty
cool. (I've applied the latest patch from JIRA to a fresh
download of
trunk revision 651344. I'm using the basic Jetty setup in the
example
directory.) The thing that's bugging me is that while the handler's
status page (http://localhost:8983/solr/dataimport?command=status)
loads fine, if I hit reload in my browser (either IE or FF), the
page
won't update; the only way to get the page to provide up-to-date
indexing status information seems to be to clear the browser
cache and
only then to reload the page. Does anyone know whether this is most
likely a Jetty issue, a Solr issue, a DataImportHandler issue, or a
more idiosyncratic problem with my setup?
Thanks,
Chris
