lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kumaran Ramasubramanian <kums....@gmail.com>
Subject Re: Indexing and storing Long fields
Date Sat, 23 Jul 2016 08:48:51 GMT
Hi Mike,

*Two different fields can be the same name*

Is it so? You mean we can index one field as docvaluefield and also stored
field, Using same name?

And AFAIK, We cannot index one field as analyzed and not analyzed using the
same name. Am i right?

Kumaran R

On Jul 21, 2016 11:50 PM, "Michael McCandless" <lucene@mikemccandless.com>
wrote:
>
> Two different fields can be the same name.
>
> I think the problem is that you are indexing it as doc values, which is
not
> searchable.
>
> To make your numeric fields searchable, use e.g. LongPoint (as of Lucene
> 6.0) or LongField (before 6.0).
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jul 21, 2016 at 11:50 AM, Siraj Haider <siraj@jobdiva.com> wrote:
>
> > Hi,
> > We want to store and index a long value. Currently when we are adding
two
> > fields with same name, one is NumericDocValuesField and the other is
> > StoredField. But it seems like the search is not returning any document
> > when we query on that field, however we are able to retrieve the field
> > values of that field from a search. So, my question is, can we index two
> > different field types with same name or do we have to use different
names
> > for these fields?
> >
> > ------
> > Regards
> > -Siraj Haider
> > (212) 306-0154
> >
> >
> > ________________________________
> >
> > This electronic mail message and any attachments may contain information
> > which is privileged, sensitive and/or otherwise exempt from disclosure
> > under applicable law. The information is intended only for the use of
the
> > individual or entity named as the addressee above. If you are not the
> > intended recipient, you are hereby notified that any disclosure,
copying,
> > distribution (electronic or otherwise) or forwarding of, or the taking
of
> > any action in reliance on, the contents of this transmission is strictly
> > prohibited. If you have received this electronic transmission in error,
> > please notify us by telephone, facsimile, or e-mail as noted above to
> > arrange for the return of any electronic mail or attachments. Thank You.
> >

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message