lucene 4.3 search not working ShingleAnalyzerWrapper

2013-09-20 Thread illusionz
Hi, I am learning lucene, and have created indexes using LuceneWriter (which worked fine), but when I try an query it with LuceneReader it dose not work, need help on the same. Following is the code for LuceneWriter.java and LuceneReader.java: public class LuceneWriter { public static void mai

Re: Lucene for Log file indexing and search

2013-09-20 Thread Otis Gospodnetic
Hi, Logstash is the piece that first touches your logs, filters them, and then outputs them somewhere. People often use it with ElasticSearch.  Once logs are in ES, they look at them with Kibana. Note: somebody should write a Logstash output for Solr! In Solr world there is Flume, which has a

Re: Custom FieldInfo.IndexOptions

2013-09-20 Thread Marcos Juarez Lopez
Thanks for your quick response Mike. I'll be sure to pay more attention to amount vs quantity in the future :) Just one clarification. I didn't mention we actually are using phrase and proximity queries, which I believe use the position information. If that's the case, is there a way to specify

Re: Strange behaviour of tokenizer with wildcard queries

2013-09-20 Thread Ian Lea
Oh, sorry, didn't catch that. There are some spurious asterisks in your message, as displayed by gmail anyway. The most recent one has "block-major** *" I don't know the answer. Some unwanted interaction between the tokenization and query parser and wildcards? If it's going to split "block-m

Re: Strange behaviour of tokenizer with wildcard queries

2013-09-20 Thread Ramprakash Ramamoorthy
On Fri, Sep 20, 2013 at 6:11 PM, Ian Lea wrote: > It's reasonable that "block-major" won't find anything. > "block-major-57" should match. > Thank you Ian, I understand. But my question is why wouldn't " block-major** *" match?, please note the wildcard at the end! Thanks. > > The split into

Re: Strange behaviour of tokenizer with wildcard queries

2013-09-20 Thread Ian Lea
It's reasonable that "block-major" won't find anything. "block-major-57" should match. The split into block and major-57 will be because, from the javadocs for ClassicTokenizer, "Splits words at hyphens, unless there's a number in the token, in which case the whole token is interpreted as a produc

Strange behaviour of tokenizer with wildcard queries

2013-09-20 Thread Ramprakash Ramamoorthy
Sorry, hit the send button accidentally the last time. Please read below : Hello, We're using lucene 4.1. We have the word "*block-major-57*" indexed. Using the classic analyzer, we get the following tokens : *block*and *major-57*. I search for *block-major*, *the docume

Strange behaviour of tokenizer with wildcard queries

2013-09-20 Thread Ramprakash Ramamoorthy
Hello, We're using lucene 4.1. We have the word "block-major-5" indexed. Using the classic analyzer, we get the following tokens : block and major-5. However, -- With Thanks and Regards, Ramprakash Ramamoorthy, Chennai, India.

Re: Custom FieldInfo.IndexOptions

2013-09-20 Thread Michael McCandless
On Thu, Sep 19, 2013 at 7:18 PM, Marcos Juarez Lopez wrote: > Hi, > > I'm trying to optimize an index we have, and one thing that has come up > recently is that we're not really using term frequencies, and we don't need > any scoring. We noticed that the term frequencies (.doc files) are a > sign

Re: Lucene ToParentBlockJoin problems

2013-09-20 Thread Michael McCandless
Can you boil down your example into a small test case, that fails, and post that? Mike McCandless http://blog.mikemccandless.com On Thu, Sep 19, 2013 at 7:59 PM, krithika r wrote: > Hi, > > I'm trying to do something very simple with the parent/child > blockjoinquery. > > I have a several chil