Re: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache Lucene.Net 2.9.4
Do it, if you need it. +1 Le 10/05/11 20:02, Lombard, Scott a écrit : +1 -Original Message- From: Troy Howard [mailto:thowar...@gmail.com] Sent: Monday, May 09, 2011 4:05 PM To: lucene-net-dev@lucene.apache.org; lucene-net-u...@lucene.apache.org Subject: [Lucene.Net] VOTE: .NET 2.0 Framework Support After Apache Lucene.Net 2.9.4 All, Please cast your votes regarding the topic of .Net Framework support. The question on the table is: Should Apache Lucene.Net 2.9.4 be the last release which supports the .Net 2.0 Framework? Some options are: [+1] - Yes, move forward to the latest .Net Framework version, and drop support for 2.0 completely. New features and performance are more important than backwards compatibility. [0] - Yes, focus on the latest .Net Framework, but also include patches and/or preprocessor directives and conditional compilation blocks to include support for 2.0 when needed. New features, performance, and backwards compatibility are all equally important and it's worth the additional complexity and coding work to meet all of those goals. [-1] No, .Net Framework 2.0 should remain our target platform. Backwards compatibility is more important than new features and performance. This vote is not limited to the Apache Lucene.Net IPMC. All users/contributors/committers/mailing list lurkers are welcome to cast their votes with an equal weight. This has been cross posted to both the dev and user mailing lists. Thanks, Troy This message (and any associated files) is intended only for the use of the individual or entity to which it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you, King Industries, Inc.
Re: Cannot Escape Special charectors Search with Lucene.Net 2.0
Hi Abhilash,
Try with: Test\&\&Test
From Documentation
(http://lucene.apache.org/java/2_3_2/queryparsersyntax.html):
==
Lucene supports escaping special characters that are part of the query
syntax. The current list special characters are
+ - && || ! ( ) { } [ ] ^ " ~ * ? : \
To escape these character use the \ before the character. For example to
search for (1+1):2 use the query:
\(1\+1\)\:2
======
Regards,
Vincent DARON
ASK
Le 17/12/10 12:29, abhilash ramachandran a écrit :
Hi,
My Name is Abhilash, working as .Net developer/support.
I have came acroos an issue with search option in our application which uses
Lucene.Net 2.0 version.
The scenario is if I try search a text "Test&&Test" (it is actually
Test&&Test.doc, which is trying to search), it returns 0 hits. While
debugging I could see that the line which wrote to Parse the query is giving
the problem,
Here is the error line code:
Query q=null;
q = new global::Lucene.Net.QueryParsers.QueryParser("content", new
StandardAnalyzer()).Parse(query);
The variable query at above point contains as this:
(title:(Test&&Test) shorttitle:(Test&&Test) content:(Test&&Test)
keywords:(Test&&Test) description:(Test&&Test) )
and q will get as this:
title:"test test" shorttitle:"test test" content:"test test" keywords:"test
test" description:"test test"
And hence the hit length will be 0 at
IndexSearcher searcher = new IndexSearcher(indexPath);
Hits hits = searcher.Search(q);
I tried adding"\" before&&, tried escape, tried enclosing the text in a ""
but all result the same outcome.
Could anyone please hlep me with any fix to it?
If require I can post the full code here.
Hope to hear from Lucene.Net.
Many thanks
Abhilash
--
Vincent DARON
ASK
Re: [jira] Commented: (LUCENENET-380) Evaluate Sharpen as a port tool
If it's easier to keep the sync between java and C# with Sharpen, the price of the sharpen-specific classes is maybe not that high. My 2 cents Regards, On Wed, 8 Dec 2010 14:08:02 -0500 (EST), "Neal Granroth (JIRA)" wrote: > [ > https://issues.apache.org/jira/browse/LUCENENET-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969427#action_12969427 > ] > > Neal Granroth commented on LUCENENET-380: > - > > I had looked them over several weeks ago, but had no additional comment > than the one you'd made about needing to find a way to eliminate > conversions which make use of Sharpen-specific classes. Hopefully others > with a larger stake than I in keeping the project alive will chime in. > > >> Evaluate Sharpen as a port tool >> --- >> >> Key: LUCENENET-380 >> URL: https://issues.apache.org/jira/browse/LUCENENET-380 >> Project: Lucene.Net >> Issue Type: Task >>Reporter: George Aroush >> Attachments: >> 3.0.2_JavaToCSharpConverter_AfterPostProcessing.zip, >> 3.0.2_JavaToCSharpConverter_NoPostProcessing.zip, >> IndexWriter.java, Lucene.Net.Sharpen20101104.zip, >> Lucene.Net.Sharpen20101114.zip, NIOFSDirectory.java, >> QueryParser.java, TestBufferedIndexInput.java, >> TestDateFilter.java >> >> >> This task is to evaluate Sharpen as a port tool for Lucene.Net. >> The files to be evaluated are attached. We need to run those files >> (which are off Java Lucene 2.9.2) against Sharpen and compare the result >> against JLCA result.
Re: How Can I Deal with Special Chars like #, /,
All the syntax for the queryparser can be found here :
http://lucene.apache.org/java/2_4_0/queryparsersyntax.html
Escaping Special Characters
Lucene supports escaping special characters that are part of the query
syntax. The current list special characters are
+ - && || ! ( ) { } [ ] ^ " ~ * ? : \
To escape these character use the \ before the character. For example to
search for (1+1):2 use the query:
\(1\+1\)\:2
Regards,
Vincent DARON
Le 11/11/10 07:07, K a r n a a écrit :
How can I search when my search term contains #, /,&. $, @,
',(,),{,},[,],|,\-,+,=,*,!,~,`etc
for example If I want to search C#, Asp.net, Accounting/ Audinting,
Banking& Financial...
How I can prepare a search query for the above keywords
...
Please let me know if anyone knows the solution...I'm doing trial and
error from past 1 month
still I'm unable to find the solution.
--
Vincent DARON
ASK
Re: Lucene.NET Community Status
Hi all Sharpen from db4o could maybe replace jlca My 2cents... Vincent Le 1 nov. 2010 à 21:55, George Aroush a écrit : Let me jump in here and offer some perspective about Lucene.Net (btw, it's not Lucene.NET :-) ). This is based on my past involvement with the project -- since 2003 when it was on SourceForge.net and called dotLucene. 1) Up until early this year, I have been porting and supporting Lucene.Net since ver 1.4 (back in 2004 on SourceForge.net) to the current release on trunk ver. 2.9.2. This is in NO WAY to say that others have not helped or contributed. I'm just saying that I know the history and have the experience (I wrote and worked on search engines from 1998 to 2002). 2) Doing an initial port of a new Java Lucene release to C# Lucene is very hard; it's the most complex part of the port even using automated tools such as JLCA and my own customize scripts which I use pre-and port JLCA (you can search the listing on how I do the port). What used to take me about 1 months with 90% of tests passing took me well over 4 months (for 2.9.x) with only 10% of tests passing. This was no easy effort and won't be easier now since Java Lucene is using new Java language features that JLCA is not aware of (MS is not maintaining JLCA). Put another way, porting is hard especially when you are dealing with > 5.6 GB source code consistent of > 610 source files. You will know this ONLY if you have tried it out and maintained it -- this is why no one has stepped up to do an initial port otherwise there would be a port by now not only of Java Lucene but other projects too. 3) To simplify ports of new release, maintaining as small as possible delta between release is very important. This was a main pain point when I ported from 2.4 to 2.9. The in-between ports were never done due to lack of time on my end. See point #2. 4) Diverging away from Java Lucene, both API base and algorithm is risky and will just make point #2 more evidence. Not only will you now need a deep knowledge of search engines to catch bugs, but also a deep knowledge of Lucene's internals. Also, you risk compatibility as well as books and existing resources on the web that cover Lucene -- hack, one can take any Java Lucene example and easily read it as a Lucene.Net code or use Luke to debug an index. Keep in mind, the current port model that we have for Lucene.Net keeps the API one-to-one in sync with Java Lucene; just upper case method names. Yes, it's not fully .NET'es, but if you are looking for a search engine that is compatible with the open source search engine standard, and it is available in C#, Lucene.Net is it. 5) Beside making the port simpler, and per point #3 above, doing a line-per-line port, and maintaining API naming as well as the algorithm and file format of Java Lucene in C# Lucene means a Lucene index created by Java Lucene is usable, concurrently, by C# Lucene. I have worked on one such project where a Java and C# code accessing the same index. I'm not too interested in making Lucene.Net .NET'es and end up adding more risk to the project. 6) If anyone wants a different flavor of Lucene.Net, the code is on Apache, just fork it and start a new project. Make it more .NET'es, use the latest that .NET has to offer, and all. However, until when you have first hand experience with the port, and a good knowledge of Lucene and search engines, and the cycles to work on it, I really don't want to exercise this idea it will die as I know few folks have tried. 7) I can't speak for the other committers or those who contributed, but for me, I do this totally during my own time. Each hour I spent on Lucene.Net is an hour away from my family or anything else. I don't get paid, and I hardly get much off my Luene.Net work on the side. As you may know, I was active with Lucene.Net till about early this year, (I had a family emergency). I want to step up again, but we need more participation than just an offer to help or request divergence from the goal of the project, per the points that I made above. I can go on, but the above are to clarify some of the issues and background of Lucene.Net. Please keep those in mind when thinking about this project and how you can contribute -- especially comments about making Lucene.Net more .NET'es -- can't start that till when you first achieve commit-per-commit port of Java Lucene to C# Lucene. If you agree with the above, and it makes sense to you, my suggestion is as follows: 1) Lucene.Net goes back into incubation and start all over again. 2) Start with cleaning up the webpage and make it more like other Apache project site. 3) Put together an official Lucene.Net 2.9.2 and get it released. 4) Start working on the next port. #2, #3 can happen right away, and all that it takes to do them is coming up to speed on how-to using existing
RE: [Fwd: TermEnum usage]
Strange, but OK Thanks a lot for answers Vincent Le jeudi 22 juillet 2010 à 19:54 +0300, Digy a écrit : > It is expected behavior. Please see > > http://lucene.apache.org/java/2_9_2/api/all/org/apache/lucene/index/IndexReader.html#terms%28org.apache.lucene.index.Term%29 > > DIGY > > -Original Message- > From: Vincent DARON [mailto:vda...@ask.be] > Sent: Thursday, July 22, 2010 6:10 PM > To: lucene-net-dev > Subject: [Fwd: TermEnum usage] > > Without any answers, I'm reposting once. Do I have to post bug report ? > > Let me know > > Thanks a lot > > Vincent DARON > ASK >
[Fwd: TermEnum usage]
Without any answers, I'm reposting once. Do I have to post bug report ?
Let me know
Thanks a lot
Vincent DARON
ASK
--- Begin Message ---
Hi all
I'm using Lucene.NET 2.9.2.2 from SVN.
I try to iterate terms of a field in my index, todo so, i'm using
IndexReader.Terms(f) that return a TermEnum.
The classic usage of iterator is the folowing pattern
TermNum enu = reader.Terms(new Term("myfield"));
while(enu.Next())
{
ProcessTerm(enu.Term());
}
But it seems that the TermEnum is already on the first item BEFORE the
first call to Next. The previous code will therefore always skip the
first Term.
Bug ?
Thanks
Vincent DARON
ASK
--- End Message ---
TermEnum usage
Hi all
I'm using Lucene.NET 2.9.2.2 from SVN.
I try to iterate terms of a field in my index, todo so, i'm using
IndexReader.Terms(f) that return a TermEnum.
The classic usage of iterator is the folowing pattern
TermNum enu = reader.Terms(new Term("myfield"));
while(enu.Next())
{
ProcessTerm(enu.Term());
}
But it seems that the TermEnum is already on the first item BEFORE the
first call to Next. The previous code will therefore always skip the
first Term.
Bug ?
Thanks
Vincent DARON
ASK
