RE: Fields with the same name

=saic@lucene.apache.org [mailto:java-user-return-45558-paul.b.murdoch=saic@lucene.apache.org ] On Behalf Of Erick Erickson Sent: Wednesday, March 24, 2010 4:28 PM To: java-user@lucene.apache.org Subject: Re: Fields with the same name I don't think so, but a quick way to check would

Re: Fields with the same name

I don't think so, but a quick way to check would be to look at your index with a copy of Luke and see what the actual tokens are. But I'm not sure it matters, I don't think you *can* make things work out well; your query-time analysis will be...er...difficult. You only get to specify one analyzer

Fields with the same name

Hi, I have a quick question. If I have an index where some text values are indexed under the same field name, but some are ANALYZED and some are NOT_ANALYZED, does the last value's flags change the flags for the whole field name? For instance if I index 3 sentences under a field name as ANALYZ

Re: Fields with the same name

Yes, assuming as I pointed out that your input string had whitespace between "bar1" and "bar2" in your first example... Erick On Wed, Oct 15, 2008 at 2:32 PM, Rafael Almeida <[EMAIL PROTECTED]>wrote: > On Wed, Oct 15, 2008 at 4:22 PM, Erick Erickson <[EMAIL PROTECTED]> > wrote: > > Yes, in terms

Re: Fields with the same name

On Wed, Oct 15, 2008 at 4:22 PM, Erick Erickson <[EMAIL PROTECTED]> wrote: > Yes, in terms of what you probably mean, but your first > example would index one token "bar1bar2". But if you > changed your first example to (note space): they would > be entirely equivalent. > > doc.add(new Field("foo

Re: Fields with the same name

Yes, in terms of what you probably mean, but your first example would index one token "bar1bar2". But if you changed your first example to (note space): they would be entirely equivalent. doc.add(new Field("foo", "bar1 bar2", Field.Store

Fields with the same name

I didn't quite understand the Document documentation so well, the documentation says: "Adds a field to a document. Several fields may be added with the same name. In this case, if the fields are indexed, their text is treated as though appended for the purposes of search." Would doc.add(new

Re: Fields with the same name?? - Was Re: Payloads and tokenizers

On Tue, Aug 19, 2008 at 2:15 AM, Antony Bowesman <[EMAIL PROTECTED]> wrote: > > Thanks for you time and I appreciate your valuable insight Doron. > Antony > I'm glad I could help! Doron

Re: Fields with the same name?? - Was Re: Payloads and tokenizers

Doron Cohen wrote: The API definitely doesn't promise this. AFAIK implementation wise it happens to be like this but I can be wrong and plus it might change in the future. It would make me nervous to rely on this. I made some tests and it 'seems' to work, but I agree, it also makes me nervous

Re: Fields with the same name?? - Was Re: Payloads and tokenizers

to store the accessId as a payload to the ownerId. > > This is where I came unstuck. For 'n=3' above, I used the > SingleTokenTokenStream as you suggested with the accessId as the payload for > ownerId. However, at the Document level, I cannot get the payloads from the

Fields with the same name?? - Was Re: Payloads and tokenizers

sted with the accessId as the payload for ownerId. However, at the Document level, I cannot get the payloads from the field so, in trying to understand fields with the same name, I discovered that there is a big difference between (a) Field f = new Field("ownerId", "OID1",