RE: lucene-3.0.3

From: Prasad KVSH [mailto:prasad.kokep...@ness.com] Sent: Wed 2/1/2012 10:23 PM To: java-user@lucene.apache.org; java-user@lucene.apache.org Subject: RE: lucene-3.0.3 Hi, Please find our requirement and we trying to accomplish this. Our client is looking for a Extended search engine like

Re: lucene-3.0.3

for TXT files only using lucene-3.0.3. > >Thanks > >Prasad > > > > >From: KARTHIK SHIVAKUMAR [mailto:nskarthi...@gmail.com] >Sent: Wed 2/1/2012 7:04 PM >To: java-user@lucene.apache.org >Subject: Re: lucene-3.0.3 > > > &

RE: lucene-3.0.3

From: KARTHIK SHIVAKUMAR [mailto:nskarthi...@gmail.com] Sent: Wed 2/1/2012 7:04 PM To: java-user@lucene.apache.org Subject: Re: lucene-3.0.3 Hi >>lucene-3.0.3 can be used for searching a text from Lucene 's primary job is to do a text search. May it

RE: lucene-3.0.3

__ From: KARTHIK SHIVAKUMAR [mailto:nskarthi...@gmail.com] Sent: Wed 2/1/2012 7:04 PM To: java-user@lucene.apache.org Subject: Re: lucene-3.0.3 Hi >>lucene-3.0.3 can be used for searching a text from Lucene 's primary job is to do a text search. May it be PDF/HTML/XML/MSword/PPT/

Re: lucene-3.0.3

ptions. > > Thanks > Prasad > > -Original Message- > From: Ian Lea [mailto:ian@gmail.com] > Sent: Wednesday, February 01, 2012 7:22 PM > To: java-user@lucene.apache.org > Subject: Re: lucene-3.0.3 > > You could also take a look at Solr.  From > h

RE: lucene-3.0.3

It will be great if you provide some working examples on this. We tried to deploy solr.war but getting exceptions. Thanks Prasad -Original Message- From: Ian Lea [mailto:ian@gmail.com] Sent: Wednesday, February 01, 2012 7:22 PM To: java-user@lucene.apache.org Subject: Re: lucene

RE: lucene-3.0.3

Prasad -Original Message- From: KARTHIK SHIVAKUMAR [mailto:nskarthi...@gmail.com] Sent: Wednesday, February 01, 2012 7:04 PM To: java-user@lucene.apache.org Subject: Re: lucene-3.0.3 Hi >>lucene-3.0.3 can be used for searching a text from Lucene 's primary job is to do a text s

Re: lucene-3.0.3

You could also take a look at Solr. From http://lucene.apache.org/solr/features.html * Easy ways to pull in data from databases and XML files from local disk and HTTP sources * Rich Document Parsing and Indexing (PDF, Word, HTML, etc) using Apache Tika Sounds just what you need. -- Ian. O

Re: lucene-3.0.3

Hi >>lucene-3.0.3 can be used for searching a text from Lucene 's primary job is to do a text search. May it be PDF/HTML/XML/MSword/PPT/XLS U have to have the code for plugin to do 2 things 1) Strip text from either of the Documents (PDF/HTML/XML/MSword/PPT/XLS) 2) Index this processed text us

RE: Lucene 3.0.3 with debug information

asn't forwarded to the list, apparently). Dawid -- Forwarded message -- From: Paul Taylor mailto:paul_t...@fastmail.fm>> Date: Fri, Apr 29, 2011 at 10:11 PM Subject: Re: Lucene 3.0.3 with debug information To: Dawid Weiss mailto:dawid.we...@gmail.com>> On 29/04/2

Re: Lucene 3.0.3 with debug information

On Fri, Apr 29, 2011 at 4:25 PM, Paul Taylor wrote: >> Hmm maybe that is enough, Im not sure. I'm profiling with YourkitProfiler >> and it doesnt show anything within the lucene classes so I assumed this >> meant they didnt contain the neccessary debugging info but I would have >> thought that -g

RE: Lucene 3.0.3 with debug information

Hi Paul, On 4/29/2011 at 4:14 PM, Paul Taylor wrote: > On 29/04/2011 16:03, Steven A Rowe wrote: > > What did you find about Luke that's buggy? Bug reports are very > > useful; please contribute in this way. > > Please see previous post, in summary mistake on my part. Okay... Which previous post

Re: Lucene 3.0.3 with debug information

On 29/04/2011 21:14, Paul Taylor wrote: Hmm maybe that is enough, Im not sure. I'm profiling with YourkitProfiler and it doesnt show anything within the lucene classes so I assumed this meant they didnt contain the neccessary debugging info but I would have thought that -g is all I need tha

Re: Lucene 3.0.3 with debug information

Instead of profiling, provide some more info about the following: - what are the problematic (slow) queries -- are they generated from the code, are they parsed from text? What are they? Certain query types are slow(er) than other query types. - what is the index built from? Natural language (tex

Re: Lucene 3.0.3 with debug information

On 29/04/2011 16:03, Steven A Rowe wrote: Hi Paul, What did you find about Luke that's buggy? Bug reports are very useful; please contribute in this way. Please see previous post, in summary mistake on my part. The official Lucene 3.0.3 distribution jars were compiled using the -g cmdline a

RE: Lucene 3.0.3 with debug information

Hi Paul, What did you find about Luke that's buggy? Bug reports are very useful; please contribute in this way. The official Lucene 3.0.3 distribution jars were compiled using the -g cmdline argument to javac - by default, though, only line number and source file information is generated. If

Re: Lucene 3.0.3 with debug information

> lucene/Search that is taking the time, I also had another attempt using > luke > > but find it incredibly buggy and of little use > Can you expand on this too? What kind of "incredible bugs" did you see? Without feedback there is little progress, so bug reports count. Dawid

Re: Lucene 3.0.3 with debug information

Hey paul, you can simply checkout the tag or download the sources right? http://svn.apache.org/repos/asf/lucene/java/tags/lucene_3_0_3/ or http://ftp.download-by.net/apache//lucene/java/3.0.3/ simon On Fri, Apr 29, 2011 at 1:09 PM, Paul Taylor wrote: > Is there a built debug version of lucene 3

RE: lucene 3.0.3 | QueryParser | MultiFieldQueryParser

two:.net)", mfqp.parse("c# AND .net").toString()); } Steve > -Original Message- > From: Ranjit Kumar [mailto:ranjit.ku...@otssolutions.com] > Sent: Wednesday, April 27, 2011 3:24 AM > To: java-user-h...@lucene.apache.org; java-user@lucene.a

Re: lucene 3.0.3 | QueryParser | MultiFieldQueryParser

Hi, while creating index with the help of lucene standardAnalyzer, we cannot make difference between c, c++ and c# as lucene do not create index for c++ and c#. To make the difference between these term I need to change the grammar of lucene with the help of jFlex, it force me to create my own

Re: lucene 3.0.3 | QueryParser | MultiFieldQueryParser

hope to sent some detail about it. 2011-04-26 haichengyl 发件人： Ranjit Kumar 发送时间： 2011-04-26 21:55:04 收件人： java-user-h...@lucene.apache.org; java-user@lucene.apache.org 抄送： 主题： lucene 3.0.3 | QueryParser | MultiFieldQueryParser Hi, I have created my own custom analyzer and uses jFl

Re: lucene 3.0.3 | QueryParser | MultiFieldQueryParser

help to give some detail info 2011-04-26 haichengyl 发件人： Ranjit Kumar 发送时间： 2011-04-26 21:55:04 收件人： java-user-h...@lucene.apache.org; java-user@lucene.apache.org 抄送： 主题： lucene 3.0.3 | QueryParser | MultiFieldQueryParser Hi, I have created my own custom analyzer and uses jFlex t

RE: lucene 3.0.3 | QueryParser | MultiFieldQueryParser

Hi Ranjit, I suspect the problem is not QueryParser, since the definition includes the '#' character (from ): | <#_TERM_START_CHAR: ( ~[ " ", "\t", "\n",

Re: lucene 3.0.3 | searching problem with *.docx file

You've given us anything to go on here, except "it doesn't work". You might review this page: http://wiki.apache.org/solr/UsingMailingLists Best Erick On Tue, Apr 12, 2011 at 9:05 AM, Ranjit Kumar wrote: > Hi, > > I am creating index with help of StandardAnalyzer for *.docx file it's > fine. Bu

RE: lucene 3.0.3 | searching problem with *.docx file

Hi Ranjit, Do you know about Luke? It will let you see what's in your index, and much more: http://code.google.com/p/luke/ Steve > -Original Message- > From: Ranjit Kumar [mailto:ranjit.ku...@otssolutions.com] > Sent: Tuesday, April 12, 2011 9:05 AM > To: java-user-h...@lucene.apa

RE: lucene 3.0.3 | phrase query problem

Hi Kumar, 1) For your question in last mail: for tool luke, go to site http://www.getopt.org/luke/ and click "launch luke now", then pointing to your lucene data folder. Also the book "Lucene in Action" is a great source (go to .amazon.com and search this book) where everything (almost) is

Re: lucene 3.0.3 | phrase query problem

Hi Ranjit, That would be because all stop words (space, comma, stop word set, etc..) would be treated in a similar fashion and escaped while indexing, subject to the analyzer you use while index your content. Hope that explains the issue. -- Anshum Gupta http://ai-cafe.blogspot.com On Thu, Feb 1

RE: lucene 3.0.3 | phrase query problem

Hi, I think using Field.Index.NOT_ANALYZED means ignoring StandardAnalyzer, so we index "sql. server" as one word. You may use luke to see how this field is indexed. In this case we can only search whole term (without case change even), if using the StandardAnalyzer to analyze "sql. server" w