Hi all,
I have 2 problem:
1. how to attach my own stylesheet to the output?
2. how the Solr do the update? What kind of update I can ask Solr to do?
Thank you for any answer.
--
View this message in context:
http://www.nabble.com/question-on-xsl-sytlesheet-and-update-tp16064251p16064251.html
S
On Fri, Mar 14, 2008 at 10:15 PM, solr_user <[EMAIL PROTECTED]> wrote:
> No this index was not generated using Solr. I just have the index files
> without access to the source that generated those files. Is there a way
> that I can change my Solr schema so that it wont split axd110 into two
>
Hi Yonik,
No this index was not generated using Solr. I just have the index files
without access to the source that generated those files. Is there a way
that I can change my Solr schema so that it wont split axd110 into two
tokens.
Yonik Seeley wrote:
>
> Was this index generated with S
It was a surprise to discover that
dateorigin_sort:""
is a syntax error, but
dateorigin_sort:["" TO *]
is legit. This says that there's a bug in the Lucene syntax parser?
Anyway, with a little more research I discover that this query:
http://64.71.164.205:8080/solr/select/?q=*:*&v
Was this index generated with Solr? If so, what does the index
analyzer look like for that field?
WordDelimiterFilter would split axd110 into two tokens, so it must
have been indexed in a compatible way (see the example schema.xml).
-Yonik
On Fri, Mar 14, 2008 at 8:51 PM, solr_user <[EMAIL PROTE
Hi,
I am trying to do alphanumeric search for terms like "axd110", but I don't
get any results back from Solr. When I open my index using Luke, I am able
to search for these terms and get results back, so I definitely know that
the terms are present in the index. Below is the query section f
: dateorigin_sort:"" gives a syntax error. I'm using Solr 1.2. Should
: this work in Solr 1.3? Is it legal in a newer Lucene parser?
Hmm.. not sure. did you try the range query suggestion? ...
: well, technically range queries "work" they just don't "work" on numeric
: ranges ... they'd be le
On Mar 14, 2008, at 2:23 PM, peter360 wrote:
Thanks for your suggestion and I pretty much agree. Part of the
reason,
which I didn't mention in my original question, that I am looking
for a
command line tool is to use it for quick diagnosis. I could point
it to a
different index just by c
dateorigin_sort:"" gives a syntax error. I'm using Solr 1.2. Should
this work in Solr 1.3? Is it legal in a newer Lucene parser?
message Query parsing error: Cannot parse 'dateorigin_sort:""':
Lexical error at line 1, column 19. Encountered: after : "\"\""
description The re
: Somehow the index has acquired one record out of millions in which an
: integer value has been populated by an empty string. I would like to isolate
: this record and remove it. This field exists solely to make sorting faster,
: and since it has an empty record, sorting blows up.
:
: Is it po
Thanks for your suggestion and I pretty much agree. Part of the reason,
which I didn't mention in my original question, that I am looking for a
command line tool is to use it for quick diagnosis. I could point it to a
different index just by changing one of the command line parameters, without
Great! I'll take a look at Luke. Thanks.
- peter
jonbaer wrote:
>
> You can do this via Luke
>
> http://www.getopt.org/luke/
>
> -snip-
> Command-line argument parsing. Now you can open an index on startup,
> and optionally execute a script
> Scripting plugin, which allows you to interact
: > +(((title_t:mass) (title_t:air) (title_t:flow))~3) ()',
: > And is that extra () indicative of something? I have some stuff going on
: > with synonyms and I'm wondering if the position of the tokens is off and
: > causing this.
:
: That extra clause is Solr's dismax code putting in an empty c
: > Where within Solr is uniqueness enforced? I'd like to at least put
: > some debug checking in there.
:
: During the add (in DirectUpdateHandler2) docs are kept track of, and
: during a commit they are checked for dups. That code has been very
Just for the record: there is one other easy w
On Fri, Mar 14, 2008 at 11:49 AM, Brian Whitman
<[EMAIL PROTECTED]> wrote:
> So, if we sent 4000 "updates" (replacements of docs already existing)
> to the index that has a 30m autocommit, and it crashed before the
> commit could happen, when it started back up I'd see both copies like
> that?
On Mar 14, 2008, at 11:37 AM, Yonik Seeley wrote:
During the add (in DirectUpdateHandler2) docs are kept track of, and
during a commit they are checked for dups. That code has been very
well tested though, and I've only seen duplicates on a JVM
crash/restart. That's because docs are added to t
On Fri, Mar 14, 2008 at 11:31 AM, Brian Whitman
<[EMAIL PROTECTED]> wrote:
> Where within Solr is uniqueness enforced? I'd like to at least put
> some debug checking in there.
During the add (in DirectUpdateHandler2) docs are kept track of, and
during a commit they are checked for dups. That co
Doesn't look like it. We do rsyncing but only as a backup for this
index-- these queries are hitting the live index.
Also, the results we get back are not exact duplicates, even though
the ID is the same. For example, if we update a document (replace an
existing document) with new informati
Hi Tashfeen,
SolrJ (the java client) is going to be released with the upcoming Solr 1.3
You can download a nightly build and run "ant dist" to build SolrJ
jar. It's very stable and well tested so you shouldn't have any
problems.
On Fri, Mar 14, 2008 at 8:25 PM, Tashfeen Ekram <[EMAIL PROTECTED]>
I am sorry for the newbie question but I have searched every where i can not
seem to find a build of the solr java client.
It seems as though perhaps it does not exist. Is that true?
thanks,
tashfeen
-
Looking for last minute shopping deals? Find them
Got it.
Thanks so much.
Brendan
On Mar 14, 2008, at 8:11 AM, Erik Hatcher wrote:
On Mar 13, 2008, at 3:06 AM, Brendan Grainger wrote:
Just started using the Dismax handler and it looks very promising.
However I'm a little confused about this query. Could somebody
please explain why I'm g
On Mar 13, 2008, at 3:06 AM, Brendan Grainger wrote:
Just started using the Dismax handler and it looks very promising.
However I'm a little confused about this query. Could somebody
please explain why I'm getting a phrase query here?
You're not actually getting a PhraseQuery. The
Disjun
The latest one won't apply to the trunk because it's too old. It hasn't been updated to match
changes made to Solr since mid-February. One of the things I know has to change is that in
CollapseComponent->prepare/process, the parameters need to change to just accept a ResponseBuilder.
Other th
Hi,
I am using java 1.6, the tomcat 5.5 also contains this file. But actually
this is the problems solved by adding 4 jar...I think the problem may be
come will xalan.jar ( resolver.jar I am not so sure)
but anyone in trouble can try this sequence
xalan.jar->resolver.jar->xercesImpl.jar->xml-api
24 matches
Mail list logo
