Re: Strange behavior of term queries with StoredFields - 4.1

2013-02-12 Thread Ramprakash Ramamoorthy
On Tue, Feb 12, 2013 at 9:17 PM, Ian Lea wrote: > I think you can store field "x" using byte[] as one Field and index it > using String as another Field. Or define your own FieldType and use > the Field(String name, byte[] value, FieldType type) constructor. Or > is that where you're getting an

Re: Optimal way to index

2013-02-12 Thread Mohammad Tariq
It actually did. I'll cross check once more and make sure I was doing it correctly. Warm Regards, Tariq https://mtariq.jux.com/ cloudfront.blogspot.com On Wed, Feb 13, 2013 at 1:44 AM, Ian Lea wrote: > "AA-" indexed as a StringField was matched by a TermQuery for "AA"? > Sounds surprising. > >

Re: Optimal way to index

2013-02-12 Thread Ian Lea
"AA-" indexed as a StringField was matched by a TermQuery for "AA"? Sounds surprising. -- Ian. On Tue, Feb 12, 2013 at 6:32 PM, Mohammad Tariq wrote: > Thanks again Ian. I'll make the changes suggested by you. And I am using > dots because if I search for 'AA' it was giving me 'AA-' as well. >

Re: Optimal way to index

2013-02-12 Thread Mohammad Tariq
Thanks again Ian. I'll make the changes suggested by you. And I am using dots because if I search for 'AA' it was giving me 'AA-' as well. Warm Regards, Tariq https://mtariq.jux.com/ cloudfront.blogspot.com On Tue, Feb 12, 2013 at 9:50 PM, Ian Lea wrote: > From a glance it looks fine. I don't

Re: Optimal way to index

2013-02-12 Thread Ian Lea
>From a glance it looks fine. I don't see what you gain by adding dots - you are using a TermQuery which will only do exact matches. Since you're using StringField your text won't be tokenized but stored as is. I see you're searching on a mixed case term - that's fine as long as you don't expect

Re: Strange behavior of term queries with StoredFields - 4.1

2013-02-12 Thread Ian Lea
I think you can store field "x" using byte[] as one Field and index it using String as another Field. Or define your own FieldType and use the Field(String name, byte[] value, FieldType type) constructor. Or is that where you're getting an Exception? How big is your index, or how small are your

Re: More questions on BlockJoinQuery

2013-02-12 Thread Michael McCandless
On Tue, Feb 12, 2013 at 7:43 AM, Chris Bamford wrote: >> Could you please send this to the java-user@lucene.apache.org list? > > I thought I did! :-) Here it is again: Duh, my bad :) You are right! I saw the "Hi Mike" and stopped there! Responses below: > I have a question about your post

Re: Optimal way to index

2013-02-12 Thread Mohammad Tariq
Hello Ian, * * I started as directed by you and created the index. Here is a small piece of code which I have written. Please have a look over it : * * *public static void main(String[] args) throws IOException, ParseException { * * * *//Specify the analyzer for tokenizing text. The same

Re: More questions on BlockJoinQuery

2013-02-12 Thread Chris Bamford
Hi Mike, > Could you please send this to the java-user@lucene.apache.org list? I thought I did! :-) Here it is again: I have a question about your post "Searching relational content with Lucene's BlockJoinQuery" (http://blog.mikemccandless.com/2012/01/searching-relational-content-with.html).

Re: More questions on BlockJoinQuery

2013-02-12 Thread Michael McCandless
Hi Chris, Could you please send this to the java-user@lucene.apache.org list? I'll try to answer it there ... this way future Googlers can benefit. Mike McCandless http://blog.mikemccandless.com On Tue, Feb 12, 2013 at 2:03 AM, Chris Bamford wrote: > Hi Mike, > > I have a question about your p

Re: Strange behavior of term queries with StoredFields - 4.1

2013-02-12 Thread Ramprakash Ramamoorthy
Ian and et al, Just a doubt. Now that I have to index and store(disk space is a constraint here). I have identified that storing as byte[] helps save some disk. But it isn't possible to index a byte[], am getting an exception when the field to be indexed is a byte[]. So how do I go