Re: Semantic indexing in Lucene

Diego, The semanticvectors project has a mailing list and his author, Dominic Widdows, is responding actively there. paul Le 24 mai 2011 à 02:34, Diego Cavalcanti a écrit : > Sorry, I thought the blog was yours! I will read the post and see if it > helps me. Thank you! > > About the Semantic

Re: Semantic indexing in Lucene

I meant to check out the Semantic vectors project, but never got around to it, so there is nothing in the blog (sujitpal.blogspot.com) that talks about semantic vectors at the moment. Its on my (rather long) todo list though... Sorry about that... -sujit On Mon, 2011-05-23 at 21:22 -0300, Diego C

Re: Semantic indexing in Lucene

Sorry, I thought the blog was yours! I will read the post and see if it helps me. Thank you! About the Semantic Vectors project, surely I know how to get its source code. What I said is that I cannot use it only by API, because the Javadoc does not show all methods. I really do not want to change

Re: Semantic indexing in Lucene

It's not my blog! :D I used some of the ideas in that article http://sujitpal.blogspot.com/2009/03/vector-space-classifier-using-lucene.html in order to perform classification with lucene for my tasks. You can get full access to the source code of the project by typing in the command line: svn che

Re: Semantic indexing in Lucene

Hi Yiannis, Thank your for your reply. Yes, I'm referring to project Semantic Vectors. Before sending the previous email, I read the project API and noticed that its most classes don't contain public methods, so that we cannot use the project programmatically (only by command line). I've seen yo

Re: Semantic indexing in Lucene

Hi Diego, Are you referring to that project--> http://code.google.com/p/semanticvectors/ ? If yes , then documentation exists here http://semanticvectors.googlecode.com/svn/javadoc/latest-stable/index.html . Also I think this blog might interest you --> http://sujitpal.blogspot.com/ and the projec

Semantic indexing in Lucene

Hello, I have a project which indexes and scores documents using Lucene. However, I'd like to do that using semantic indexing (LSI, LSA or Semantic Vectors). I've read old posts and some people said that Semantic Vectors plays well with Lucene. However, I noticed that its classes are used only by

FastVectorHighlighter - can FieldFragList expose fragInfo?

Hello, My version: Lucene 3.1.0 I've had to customize the snippet for highlighting based on our application requirements. Specifically, instead of the snippet being a set of relevant fragments in the text, I need it to be the first sentence where a match occurs, with a fixed size from the beginni

Re: QueryParser/StopAnalyzer question

Hi Erick, I think answer to this question depends which hat you put on. If you put search engine hat (or do similar things in, i.e. Google), the results will be the same as what Lucene does at the moment. And that's fair enough - getting more results in search engine world is almost always better

Re: QueryParser/StopAnalyzer question

Hmmm, somehow I missed this days ago Anyway, the Lucene query parsing process isn't quite Boolean logic. I encourage you to think in terms of "required", "optional", and "prohibited". Both queries are equivalent, to see this try attaching &debugQuery=on to your URL and look at the "parsed que

Re: # search in Query

Are you sure that it isn't working? If you use the same analyzer at both indexing and query time you should end up with consistent results. Read up on exactly what your analyzer is doing by looking at the javadocs. Google will find you lots of info on analysis, or get hold of a copy of Lucene In

Re: FastVectorHighlighter StringIndexOutofBounds bug

(11/05/23 14:36), Weiwei Wang wrote: > 1. source string: 7 > 2. WhitespaceTokenizer + EGramTokenFilter > 3. FastVectorHighlighter, > 4. debug info: subInfos=(777((8,11))777((5,8))777((2,5)))/3.0(2,102), > srcIndex is not correctly computed for the second loop of the outer for-loop > How

# search in Query

I have some bellow value in lucene index field 1#abcd 2#test wer 3# testing rty I wright the query like bellow +fieldname:1# After query parser I see query string become +fieldname:1 is there a way to search given string Thanks & Regards Yogesh

Re: QueryParser/StopAnalyzer question

Not much luck so far :( Just in case if anyone wants to earn some virtual dosh, I have added some 50 bonus points to this question on StackOverflow: http://stackoverflow.com/questions/6044061/lucene-query-parsing-behaviour-joining-query-parts-with-and I also promise to post a solution here if an

Re: stop the search

Thanks a lot. I tried to debug a long query and see when it gets to the collector. I thought it will be better to catch the "stop" action in the search itself and not the top doc collector as I would assume the search action will take long time to finish and once we get to the top doc collector,