RegexQuery on multiple fields?

[Oliver Hummel]

Hi,

I've recently tried the RegexQuery with Lucene which works fine with the
following code snippet:

  Hits hits;
  String q = "someregex";
  Term t = new Term("content", q);
  Query query = new RegexQuery(t);
  hits = searcher.search(query);

However, I wonder whether it is possible to use a QueryParser together with the
RegexQuery to determine the field to be searched on dynamically?

I wasn't able to find a solution in the API. Anybody knows one? Or is this not
possible?

Thanks in advance!

  Oliver



--
http://merobase.com - find source code, components and web services

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Strange Behaviour of BooleanQuery?

[Oliver Hummel]

Eric, thanks for your reply.

> I assume it's a typo, but your for loop wouldn't produce your example as
> they'd all be the same field

Actually there are three loops that add it for different fields... :-)

> So, here's what I'd do. Use Query.toString() for both your BooleanQuery and
> the query produced by QueryParser and see what's different, if anything.
> That'll certainly give you a clue. If your QueryParser uses, for instance,
> the StandardAnalyzer, it'll lowercase, remove most punctuation, etc, which
> you wouldn't get with your manually constructed BooleanQuery.

It delivered exactly the same query.

Meanwhile I think I got the problem. It seems to be related with redeploying in
JBoss. Everytime I redeploy now without restarting the server it does not work
anymore...

Thanks!

  Oliver



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Strange Behaviour of BooleanQuery?

[Oliver Hummel]

Hi @all,

I'm a little confused about the behaviour of BooleanQuery. I have a custom
parser that analyzes some text and constrcuts an "ANDed" BooleanQuery. toString
delivers something like this:

  (+field1:term1 +field2:term2)

Looks pretty normal to me, but the problem is it delivers no results (although
there are matching ones of course). What makes it even more confusing is the
fact that when I take the above query and use it with the QueryParser it works
and delivers the expected results...

Any ideas? Perhaps anyone who is able to reproduce it? Am I doing something
wrong or is there a bug?

Here is how I produce the BooleanQuery:

BooleanQuery bq = new BooleanQuery();
for (iterate over terms) {
   t = new Term(field, term);
   bq.add(new TermQuery(t), BooleanClause.Occur.MUST);
}

Any help appreciated, thanks in advance!

  Oliver



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]