Makes sense. Thanks for the response!
--Bill
On 4/26/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
>
>
> : Why does DateTools.dateToString() return a String representation of my
> Date,
> : but in a different TimeZone. Does it use its own Calendar/TimeZone
> settings?
>
> Yes, DateTime is hardco
Hello,
Why does DateTools.dateToString() return a String representation of my Date,
but in a different TimeZone. Does it use its own Calendar/TimeZone settings?
F.I.
DateFormat format = new SimpleDateFormat("-MM-dd hh:mm:ss.SSS");
System.out.println(DateTools.dateToString(format.parse("2006-
On 4/14/06, Erick Erickson <[EMAIL PROTECTED]> wrote:
>
> Something that took me a while to get was that the analyzer is important
> BOTH in the indexing phase and in the searching phase (assuming you're
> using
> the QueryParser). For you experiment, you probably want to use the
> WhitespaceAnalyz
oops, thought that you were just referring to the lowercase...
:)
On 4/14/06, karl wettin <[EMAIL PROTECTED]> wrote:
>
>
> 14 apr 2006 kl. 17.22 skrev karl wettin:
> >
> > It is the Analyzer that does that. Try creating your IndexSearcher
> > with a KeywordAnalyzer (it think).
>
> err
>
> It is th
AIL PROTECTED]> wrote:
>
> On 4/14/06, Bill Snyder <[EMAIL PROTECTED]> wrote:
> >
> > AHA! I am using the Search tab and have enteres the query :
> >
> > location:Z:\install\logs\archive.log.D20060406.T141958
> >
> > the query details says the query w
"
So, lucence does not store the file path exactly?! It converts it all lower
case! Is there some property I should turn on?
Plus, it is not storing the backslash. Should I be escaping these in the
index before storing them? It seems so.
-Bill
On 4/14/06, Bill Snyder <[EMAIL PROTECTED]> wro
nalyze whats getting indexed. Have you tried that?
>
> On 4/14/06, Bill Snyder <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > We am using Lucene to facilitate searching of our applications log
> files.
> > I
> > am noticing some inconsistencies i
Hello,
We am using Lucene to facilitate searching of our applications log files. I
am noticing some inconsistencies in result sets when searching on certain
fields.
One field we index is the file path. I am using a simple query like
"location:Z:\logs\someLogFile.log". However, I can never get pat
Hello,
How can I configure Lucene to handle numeric range searches? (This question
has been asked 100 times, I'm sure.)
I've tried the suggestions on the SearchNumericalFields wiki page. This
seems to work for simple queries. Searching for "line:[1 to 10]" gives me
lines 1 thru 10 of the documen
