Hi,
Thanks man you solved my problem.
Regards,
Saif...
- Original Message -
From: "Terry Steichen" <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 9:25 AM
Subject: Re: Range queries
> As of Lucene 1.3dev1 at least, some range query synta
Thanks for your suggestions Dietrich. I'll try it out.
- Original Message -
From: "Materna, Wolf-Dietrich (empolis B)"
<[EMAIL PROTECTED]>
To: "'Lucene Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 2:54 AM
Subject: AW: Cannot match field containing value "No"
Hello,
Ok thanks for the input.
- Original Message -
From: "Otis Gospodnetic" <[EMAIL PROTECTED]>
To: "Lucene Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 7:06 AM
Subject: Re: how to join 2 queries togther
> Mailing list archives would be the only place for now.
> If you ca
Hi,
Is there any interest in creating an additional distribution for Lucene that
contains some of the code from the sandbox and the contributions? I was
thinking about bringing in the SearchBean, LARM, the optional analyzers,
etc. I know there has been some discussion on this list of what should
I just realized how dense I've been on this thread. All along Terry
has been saying he's indexing date fields as "MMDD" String fields
and I just wasn't getting it. I had my brain locked into thinking the
fields were being indexed as Date fields.
My apologies for the run around on this thr
So you are using 1.3dev1?
I'm not having the same effect you are - and looking at QueryParser.jj
it does this:
private Query getRangeQuery(String field,
Analyzer analyzer,
String part1,
String part2,
Hi,
I want to query for range for date field(which can be broken in year and month) and
also query the title field. I have already tag this field while indexing but i
don't know how to query them together can any one please help me on this.
Thanks.
Regards,
Saif...
As of Lucene 1.3dev1 at least, some range query syntax changes were made.
If you use dates expressed as MMDD (without doing the dateToString
conversion), the expression my_date_field:[0 TO mmdd] returns all
entries up to the date mmdd, and the expression my_date_field:[mmdd
TO null
Followup: after looking at QueryParser.jj (my apologies for not looking
deeper before), it *does* support readable date range queries. But the
dates must both be valid and adhere to DateFormat.SHORT style. I
changed the code I previously sent to this:
String begin = "1/1/02";
First thing you may want to change are those empty catch blocks.
If this is running as your web app user, it looks like it is a, make
sure that this user can write to 'indexFIle' (better name would be
indexDir).
Otis
--- Vinu SB <[EMAIL PROTECTED]> wrote:
> Hi,
> I am relativly new to Lucene and
Stealing somebody else's thread? Bad manners!
Otis
--- Vinu SB <[EMAIL PROTECTED]> wrote:
> Hi,
> I am relativly new to Lucene and I am trying to index
> the docs, as and when they are uploaded to the system,
> by calling the following code: I keep getting 'segment
> file not found error (thru d
Hi,
I am relativly new to Lucene and I am trying to index
the docs, as and when they are uploaded to the system,
by calling the following code: I keep getting 'segment
file not found error (thru debugger), when I was
expecting it to create those index files.
Can anybody look into the following cod
Hi,
I am relativly new to Lucene and I am trying to index
the docs, as and when they are uploaded to the system,
by calling the following code: I keep getting 'segment
file not found error (thru debugger), when I was
expecting it to create those index files.
Can anybody look into the following cod
t mimics the
dateToString functionality that you'd share?
Erik
On Wednesday, January 22, 2003, at 10:20 AM, Terry Steichen wrote:
Erik,
I believe the question was on range queries in general, which of
course work
with the QueryParser.
You can use range queries for dates, provided
This question is more appropriate for lucene-user.
You may also get more help there.
While locking is disabled with a global system property, you normally
set properties with -D command line options when invoking java. If you
do want locks, don't use -D.
I am assuming that you are not mixing indi
On Wednesday 22 January 2003 08:27, Michael Barry wrote:
> I utilize the earlier version and queries such as this work fine with
> QueryParser:
>
> field:[ 20030120 - 20030125 ]
>
> of course the back-end indexer canonocalizes all date fields to MMDD.
> The front-end search code is responsible
On Wednesday 22 January 2003 07:49, Erik Hatcher wrote:
> Unfortunately I don't believe date field range queries work with
> QueryParser, or at least not human-readable dates.
>
> Is that correct?
>
> I think it supports date ranges if they are turned into a numeric
> format, but no human would typ
At 14:51 2003-01-22 -0500, you wrote:
Alain -
Are you sure you are using the analyzer you wrote for both indexing and
querying?
Peter
Alain Lauzon wrote:
Yes, I replaced all StandardAnalyzer with my CompanyAnalyzer and that is
what I am
using at indexing and querying time.
Finally I was f
Hello
I have a strange requirement. I am indexing a single HTML Document and
searching it immediately for one or more keywords (Boolean/Phrase query).
When the keywords are found in the document, I would like to
know if the matched keywords are from hyperlink text, a paragraph or one of
, etc t
Alain -
Are you sure you are using the analyzer you wrote for both indexing and
querying?
Peter
Alain Lauzon wrote:
Finally I was fed up and I manually parsed the state field and put
"ontario" when
it was "ON" and so on for "OR" and "IN". I did the same parse for the
query and
reversed the
Finally I was fed up and I manually parsed the state field and put
"ontario" when
it was "ON" and so on for "OR" and "IN". I did the same parse for the
query and
reversed the parse when displaying the state field so that it will display
ON and
not ontario.
I do not understand what is the bug b
We had a similar problem (under linux) but have had no issues during
testing on windows.
We did two things to solve the problem:
1) Increase the file limit for the program to 4096. The alleviated but
did not completely solve the problem. Under stress testing we would
still fall short of the m
That's what I did. ;-(
At 10:24 2003-01-22 -0800, you wrote:
You don't say whether you threw away the old index or if you switched
the Analyzer on an existing index.
You should throw the old index away and reindex all of your docs with
an Analyzer that handles ON, OR, IN, etc.
Otis
--- Alain
You don't say whether you threw away the old index or if you switched
the Analyzer on an existing index.
You should throw the old index away and reindex all of your docs with
an Analyzer that handles ON, OR, IN, etc.
Otis
--- Alain Lauzon <[EMAIL PROTECTED]> wrote:
> I am having the same problem
I am having the same problem with words "ON", "OR" and "IN",
standing for, Ontario, Oregon and Indiana. I have created my own
Analyzer and remove the stop word "on", "or" and "in" and I have
the same results.
Is there another place in the code that is using those stop words ?
Anybody with the sa
Does this have better performance than using DateFilter?
Regards,
Hui
-Original Message-
From: Michael Barry [mailto:[EMAIL PROTECTED]]
Sent: Wed 1/22/2003 10:27 AM
To: Lucene Users List
Cc:
Subject: Re: Range queries
Thanks for the additions.
I put SearchBean up in contributions to provide for a simple example of
sorting.
I will go through and add your suggestions as it seems to be used by
some people in their systems.
If you have any other items you think should be changed I'd be up for
your suggestions.
Terry and Michael,
Thanks for the clarification. For some reason I though that date
fields were represented more oddly than this format. I stand corrected!
Erik
On Wednesday, January 22, 2003, at 10:27 AM, Michael Barry wrote:
I utilize the earlier version and queries such as this work fin
Hi,
I have been using Lucene in a production enviroment now for about a year,
using version 1.1.I had moved across to the 1.2 release, but as the
result of this the number of file handles that were needed increased
dramatically.
A quick look at some trace from the OS indicated that when the
I utilize the earlier version and queries such as this work fine with
QueryParser:
field:[ 20030120 - 20030125 ]
of course the back-end indexer canonocalizes all date fields to MMDD.
The front-end search code is responsible for canonocalizing the user inputed
dates to MMDD. I think the k
Erik,
I believe the question was on range queries in general, which of course work
with the QueryParser.
You can use range queries for dates, provided, as I believe you imply, the
dates are in lexiographic order (ie, 20030122). (As to whether dates
expresed as such are too challenging for the
Mailing list archives would be the only place for now.
If you can figure out JavaCC you can also look at QueryParser.jj
itself.
It would be nice to add RangeQuery syntax to that Query Parser Syntax
page, yes.
Peter, can you do this?
Thanks,
Otis
--- Charles <[EMAIL PROTECTED]> wrote:
> Thanks fo
Unfortunately I don't believe date field range queries work with
QueryParser, or at least not human-readable dates.
Is that correct?
I think it supports date ranges if they are turned into a numeric
format, but no human would type that kind of query in. I'm sure
supporting true date range que
Tatu,
I believe the range query syntax for the latest Lucene version is
"field:[lower TO upper]", or "field:[null TO upper]", or "field:[lower TO
null]". In earlier versions replace "TO" with a dash ("-").
I also believe that multiple wildcards ("?" and/or "*") work just fine (as
long as they ar
Hello,
I just ran into this exception:
java.lang.NullPointerException
at org.apache.lucene.store.RAMInputStream.(Unknown Source)
at org.apache.lucene.store.RAMDirectory.openFile(Unknown Source)
at org.apache.lucene.index.FieldInfos.(Unknown Source)
at org.apache.lu
Hello,
> I seem to be having trouble matching the value "No". The
> snippet of my insert index code looks like this:
>
> IndexWriter writer = new IndexWriter("indexTest", new
> StandardAnalyzer(), true);
> Document doc = new Document();
> doc.add(Field.Text("YesNo", choice
Okay please disregard this. Found out that the word "no" is removed by the
StandardAnalyser since its one of the stop words.
- Original Message -
From: "Charles" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 6:46 PM
Subject: Cannot match field containing val
Hello all,
I seem to be having trouble matching the value "No". The snippet of my insert index
code looks like this:
IndexWriter writer = new IndexWriter("indexTest", new StandardAnalyzer(), true);
Document doc = new Document();
doc.add(Field.Text("YesNo", choice));
write
Thanks for the advice Otis. I used the BooleanQuery to nest all my sub
queries and it works fine.
However I still have one question, regarding the RangeQuery. Where can I
find an updated list of the syntax for RangeQuery (or any other Queries if
exists)? I was fortunate enough to stumble across a
39 matches
Mail list logo
