I found out the solution!
I needed to also add an EdgeNGramFilterFactory to the fields that are the
source of the copyField.
That got the highlighting working again.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Highlighting-with-a-default-copy-field-with
get highlighting?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Highlighting-with-a-default-copy-field-with-EdgeNGramFilterFactory-tp3510374p3510374.html
Sent from the Solr - User mailing list archive at Nabble.com.
Hi,
Is this simply for returning a date string, or do you really need a full-blown
Date object for your years?
I'd probably go with a "tint" field for the faceting on year, if year is the
lowest date resolution you need.
If you need to convert 2008 to 2008-01-01T00:00:00Z to put into a real "dat
What version of Solr are you using? Because 3.2 (and I believe 3.1) and later
have faceting and range on numeric values, so there would be no need to use
two fields.
And you could then avoid the format thing entirely.
Best
Erick
On Wed, Aug 24, 2011 at 5:53 AM, Oliver Schihin
wrote:
> Hello lis
have u tried in your facet_year index analyzer something like this?
this can theoretically do the trick
2011/8/24 Oliver Schihin
> Hello list
>
> My documents come with a field holding a date, always a year:
> 2008
> In the schema, this content is taken for a field as an integer, and
> it
Hello list
My documents come with a field holding a date, always a year:
2008In the schema, this content is taken for a field as an integer, and it will be
searchable.
Through a copyfield-instruction I move the to a -field, you guess, to
use it for faceting and make range queries possible.
I've noticed that using camelCase in field names causes problems.
On 11/5/2010 11:02 AM, Will Milspec wrote:
Hi all,
we're moving from an old lucene version to solr and plan to use the "Copy
Field" functionality. Previously we had "rolled our own" implementatio
list from time to time).
Best
Erick
On Fri, Nov 5, 2010 at 11:02 AM, Will Milspec wrote:
> Hi all,
>
> we're moving from an old lucene version to solr and plan to use the "Copy
> Field" functionality. Previously we had "rolled our own" implementation,
&
Hi all,
we're moving from an old lucene version to solr and plan to use the "Copy
Field" functionality. Previously we had "rolled our own" implementation,
sticking title, description, etc. in a field called 'content'.
We lose some flexibility (i.e. java layer
r non multiValued copy field all:
at
org.apache.solr.client.solrj.embedded.EmbeddedSolrServer.request(EmbeddedSolrServer.java:161)
at
org.apache.solr.client.solrj.request.UpdateRequest.process(UpdateRequest.java:217)
at org.apache.solr.client.solrj.SolrServe
On Sat, Sep 12, 2009 at 3:25 AM, Mohamed Parvez wrote:
> Is its possible to concatenate two fields and copy it to a new field, in
> the
> schema.xml file
>
> I am importing from two tables and both have numeric value as primary key.
>
> If i copy just the primary key, which is a number, from both
Is its possible to concatenate two fields and copy it to a new field, in the
schema.xml file
I am importing from two tables and both have numeric value as primary key.
If i copy just the primary key, which is a number, from both the tables, to
one field and make it primary key, records may get ov
ma.xml:
Used for those fields:
Which are used to populate this field using the copy field directive:
like that (that is what I do, now, at least):
I am copying fields with different types to all_text_de, e.g. title is
differen
/>
>
>
>
>
> words="stopwords_de.txt" />
> generateWordParts="1" generateNumberParts="1" catenateWords="0"
> catenateNumbers="0" catenateAll="0" splitOnCaseChan
;1" />
Used for those fields:
required="true" />
required="false" />
required="false" />
required="false" />
Which are used to populate this field using the copy field directive:
like that (that is what
our "name" field and faceting on the "actor" field.
>
> -Original Message-
> From: Senthil Kumar [mailto:mesent...@gmail.com]
> Sent: Friday, April 24, 2009 11:42 AM
> To: solr-user@lucene.apache.org
> Subject: Copy field : String Vs Text
>
> Hi
or" field.
-Original Message-
From: Senthil Kumar [mailto:mesent...@gmail.com]
Sent: Friday, April 24, 2009 11:42 AM
To: solr-user@lucene.apache.org
Subject: Copy field : String Vs Text
Hi,
I have a requirement as below. The field needs to be available for facet.
The value will not
Hi,
I have a requirement as below. The field needs to be available for facet.
The value will not be a single letter word. But I should be able to search
like a text fields.
Silver stolen
Schema.xml
I should be able to search for the word "silver" on actor field and should
get the
That works thanks!
_
From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com]
Sent: Monday, March 23, 2009 2:11 PM
To: solr-user@lucene.apache.org; cra...@ceiindia.com
Subject: Re: multiple values encountered for non multiValued copy field
multiValued should be camel cased but in
ued="true"/>
>
> person_id
> all
>
>
>
>
>
> INFO: Time taken for getConnection(): 360
> Mar 23, 2009 1:51:25 PM org.apache.solr.handler.dataimport.SolrWriter
> upload
> WARNING: Error creating document :
> SolrInputDocument[{fname=fnam
1:51:25 PM org.apache.solr.handler.dataimport.SolrWriter upload
WARNING: Error creating document :
SolrInputDocument[{fname=fname(1.0)={Peter}, person_id=person_id(1.0)={1}}]
org.apache.solr.common.SolrException: ERROR: multiple values encountered for
non multiValued copy field all: 1
On 3/5/06, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> Can the copy field functionality be applied to dynamic fields?
You're finding the weak points fast, Grant :-)
copyField doesn't work with dynamic fields yet, but it seems like a
good think to enable.
copyField from a
Can the copy field functionality be applied to dynamic fields?
-Grant
--
Grant Ingersoll
http://www.grantingersoll.com
-
Brings words and photos together (easily) with
PhotoMail - it's free and
101 - 123 of 123 matches
Mail list logo
