: No, sorry, I'm still confused. It ought to be a term queries?
: > > System.out.println(new QueryParser("f", new Analyzer() {
: > > public TokenStream tokenStream(String string, Reader reader) {
: > > return new NGramTokenFilter(new StandardTokenizer(reader), 2, 5);
: > > }
: > > }).pars
: This would be nice, but unfortunately I do not have direct access
: to the solr server in my application. I need to parse queries,
: filter out blacklisted facettes and then parse them on to solr
: using solrj.
that depends ... what do you mean by a blacklisted facet?
facet counts are controlle
No, sorry, I'm still confused. It ought to be a term queries?
--
the flooding troll
11 okt 2007 kl. 20.40 skrev Karl Wettin:
I now realize that that phrase makes sense, and that it was another
"feature" in my code that confused me.
So, forget about it.
Bada bing, bada bom.
--
karl
1
I now realize that that phrase makes sense, and that it was another
"feature" in my code that confused me.
So, forget about it.
Bada bing, bada bom.
--
karl
11 okt 2007 kl. 19.47 skrev Karl Wettin:
I don't understand, why does the following code create 2 phrase
queries instead of 20 term
I don't understand, why does the following code create 2 phrase
queries instead of 20 term queries? I'm quite sure I've previously
had QueryParser doing the latter.
System.out.println(new QueryParser("f", new Analyzer() {
public TokenStream tokenStream(String string, Reader reader) {
re
I have used Lucene on SAN in a federal project, works out great. It supports
search clustering, where several other servers search on the shared index
which is produced by another server. Only need to refresh the other
searching servers' IndexSearcher after indexing is done.
--
Chris Lu
-
Hi,
I wonder if there are any known issues having a lucene index on a NAS or SAN
drive? Some basic tests show that it works fine. But are there performance
issues with indexing on NAS for instance?
Thanks,
Yasoja
Martin Dietze wrote:
On Wed, October 10, 2007, Mark Miller wrote:
Back in the day you might have been able to call Query.toString() as the
Query contract says that toString() should output valid QueryParser syntax.
This does not work for many queries though (most notably Span Queries --
Hi All,
I have two questions here
1- Lucene generates id for every document it indexes and it does in
order..0,1,2,3.n .Can i make lucene use my id ( my id for a document
..say randomly generated unique id for a document) as lucene id.
The reason i am asking this question because lucene filt
On Wed, October 10, 2007, Mark Miller wrote:
> Back in the day you might have been able to call Query.toString() as the
> Query contract says that toString() should output valid QueryParser syntax.
> This does not work for many queries though (most notably Span Queries --
> QueryParser knows no
On Wed, October 10, 2007, Chris Hostetter wrote:
> Eh ... not really. it would be easier to just load the Qsol parser in
> solr ... or toString() the query...
This would be nice, but unfortunately I do not have direct access
to the solr server in my application. I need to parse queries,
filter
11 matches
Mail list logo