Re: copyField from empty multivalue

Nevermind I think we found this was caused by a bug in our (new) custom indexer On Thu, Aug 6, 2020 at 4:11 PM matthew sporleder wrote: > > I have a copyField: > > > > But sometimes preview ( indexed="true" stored="true" multiValued="true" />) is not populated. > > It appears that the "catcha

Re: copyField - why source should contain * when dest contains *?

Hey Community, I think I have got the answer to my query. This statement about *copyFields *: *The copyField command can use a wildcard (*) character in the dest > parameter only if the source parameter contains one as well. copyField

Re: copyField - why source should contain * when dest contains *?

Hey Chris, Awesome explanation. ...then solr has no idea what full field name to use as the destination > when it seees values in a field "foo" ... should it be "1_bar" ? > "aaa_bar" ? ... "z_bar" ? all three? But how does Solr get the idea what full field name to use as

Re: copyField - why source should contain * when dest contains *?

: Documentation says that we can copy multiple fields using wildcard to one : or more than one fields. correct ... the limitation is in the syntax and the ambiguity that would be unresolvable if you had a wildcard in the dest but not in the source. the wildcard is essentially a variable. if

Re: copyField - why source should contain * when dest contains *?

Hey Erick, Thanks for addressing. Copyfields are intended to copy exactly one field in the input into exactly > one field in the destination, not multiple ones at the same time. Documentation says that we can copy multiple fields using wildcard to one or more than one fields. Remember that S

Re: copyField - why source should contain * when dest contains *?

So how would that work? Copyfields are intended to copy exactly one field in the input into exactly one field in the destination, not multiple ones at the same time. If you need to do that, define multiple copyField directives. I don’t even see how that would work. . Remember that Solr is also

Re: copyfield not working

thanks for the info Andrea! Thanks Jay On Sun, Jan 13, 2019 at 11:53 PM Andrea Gazzarini wrote: > Hi Jay, the text analysis always operates on the indexed content. The > stored content of a filed is left untouched unless you do something > before it gets indexed (e.g. on client side or by an

Re: copyfield not working

copyfield syntax from my schema file... Thanks Jay On Sun, Jan 13, 2019 at 11:46 PM Jay Potharaju wrote: > Hi, > I have a copy field in which i am copying the contents of text_en field to > another custom field. > After indexing i was expecting any of the special characters in the > paragraph

Re: copyfield not working

Hi Jay, the text analysis always operates on the indexed content. The stored content of a filed is left untouched unless you do something before it gets indexed (e.g. on client side or by an UpdateRequestProcessor). Cheers, Andrea On 14/01/2019 08:46, Jay Potharaju wrote: Hi, I have a copy f

Re: copyField match, but how?

You're on the money, Chris. Thank you s much, I didn't even realize "body" wasn't stored. Of course that is the reason!! -- View this message in context: http://lucene.472066.n3.nabble.com/copyField-match-but-how-tp4323327p4323335.html Sent from the Solr - User mailing list archive at Nab

Re: copyField match, but how?

: In my schema.xml, I have these copyFields: you haven't shown us the field/fieldType definitions for any of those fields, so it's possible "simplex" was included in a field that is indexed=true but not stored-false -- which is why you might be able to search on it, but not see it in the field

Re: copyField match, but how?

I think you are not using default field, but rather eDismax field definitions. Still you seem to be matching on alltext anyway. What's the field definition? Did you check the index content with Maple or with Admin Schema field content? Regards, Alex On 3 Mar 2017 5:07 PM, "nbosecker" wrote:

Re: copyField

: 1) Give my need, am I losing anything by writing my own copy-field in my : Java code vs. using Solr's copyField in the schema? nope. : 2) How do I prevent a case where when I copy data from field A and B where : A has "Fable of the Throbbing" and B has "Genius of a Tank Town" which get : copie

Re: copyField based on value of another field

You should work at the UpdateProcessor level : https://wiki.apache.org/solr/UpdateRequestProcessor#Implementing_a_conditional_copyField This should give you some hint. Cheers 2015-06-23 13:45 GMT+01:00 Alistair Young : > Hi folks, > > is it possible to copyField only if another field has a cer

Re: CopyField exclude patterns

Alexander and Jack Thanks for the reply. Looking at both, I think that the CloneFieldUpdateProcessor can do what I need without having to implement a custom one. By the way, Is there a performance penalty by update processor comparing to copy Field? On Mon, Feb 2, 2015 at 4:29 PM, Alexandre Rafa

Re: CopyField exclude patterns

Not on copyField, You can use UpdateRequestProcessor instead ( http://www.solr-start.com/javadoc/solr-lucene/org/apache/solr/update/processor/CloneFieldUpdateProcessorFactory.html ). This allows to specify both inclusion and exclusion patterns. Regards, Alex. Sign up for my Solr resource

Re: CopyField exclude patterns

Sorry, that feature is not available in Solr at this time. You could implement an update processor which copied only the desired input field values. This can be done in JavaScript using the script update processor. -- Jack Krupansky On Mon, Feb 2, 2015 at 2:53 AM, danny teichthal wrote: > Hi, >

RE: CopyField from text to multi value

Thanks Walter! -Original Message- From: Walter Underwood [mailto:wun...@wunderwood.org] Sent: Monday, October 20, 2014 12:09 AM To: solr-user@lucene.apache.org Subject: Re: CopyField from text to multi value I think that info is available with termvectors. That should give a list of the

Re: CopyField from text to multi value

gt; > > > That is my use case. > > Thanks again > > Tomer > > > > > > -Original Message- > From: Erick Erickson [mailto:erickerick...@gmail.com] > Sent: Sunday, October 19, 2014 5:18 PM > To: solr-user@lucene.apache.org > Subjec

RE: CopyField from text to multi value

al Message- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Sunday, October 19, 2014 5:18 PM To: solr-user@lucene.apache.org Subject: Re: CopyField from text to multi value This really feels like an XY problem, which I think Jack is alluding to. bq: I understand that the analysis chai

Re: CopyField from text to multi value

This really feels like an XY problem, which I think Jack is alluding to. bq: I understand that the analysis chain is applied after the raw input was copied. I need to store the output of the analysis chain as a new multi-value field This statement is really confusing. You can't have the output

Re: CopyField from text to multi value

As always, you need to first examine how you intend to query the fields before you dive into data modeling. In this case, is there any particular reason that you need the individual terms as separate values, as opposed to simply using a tokenized text field? -- Jack Krupansky From: Tomer Levi

RE: CopyField from text to multi value

- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Sunday, October 19, 2014 4:31 PM To: solr-user@lucene.apache.org Subject: Re: CopyField from text to multi value Not quite sure what you're asking here. If you do a copyField, the raw input is, well, copied to the destination fiel

Re: CopyField from text to multi value

Not quite sure what you're asking here. If you do a copyField, the raw input is, well, copied to the destination field and _then_ the analysis chain is applied. Which seems to be what you want, the destination field would be a text-based field, perhaps text_general or some such from the distro. An

Re: CopyField Wildcard Exception possible?

Thank you Ahmet. I am not familiar with using the ScriptUpdateProcessor, but I would look into it. I am also not sure how bad this would be on the import performance. O. O. -- View this message in context: http://lucene.472066.n3.nabble.com/CopyField-Wildcard-Exception-possible-tp4155686p415600

Re: CopyField Wildcard Exception possible?

How about using ScriptUpdateProcessor? On Friday, August 29, 2014 5:39 PM, O. Olson wrote: Thank you Joe. I am not familiar with creating a JIRA ticket. I was however hoping that there might be a solution to this. If there is none, then I would consider explicitly specifying the fields. O. O.

Re: CopyField Wildcard Exception possible?

Thank you Joe. I am not familiar with creating a JIRA ticket. I was however hoping that there might be a solution to this. If there is none, then I would consider explicitly specifying the fields. O. O. -- View this message in context: http://lucene.472066.n3.nabble.com/CopyField-Wildcard-Excep

Re: CopyField Wildcard Exception possible?

We would enjoy this feature as well, if you'd like to create a JIRA ticket. On Thu, Aug 28, 2014 at 4:21 PM, O. Olson wrote: > I have hundreds of fields of the form in my schema.xml: > > multiValued="true"/> > multiValued="true"/> > . > > I also have a field 'text' tha

Re: CopyField can't copy analyzers and Filters

Hello, for Cx_val, there is some fields which are multivalued :) for AllChamp_fr, AllChamp_en..., i juste added them to the schema to test if edismax work. 2014-07-01 17:13 GMT+02:00 Daniel Collins [via Lucene] < ml-node+s472066n4145024...@n3.nabble.com>: > Ok, firstly to say you need to fi

Re: CopyField can't copy analyzers and Filters

Ok, firstly to say you need to fix your problem but you can't modify the schema, doesn't really help. If the schema is setup badly, then no amount of help at search time will ever get you the results you want... Secondly, from what I can see in the schema, there is no AllChamp_fr, AllChamp_en, et

Re: CopyField can't copy analyzers and Filters

hello erick, unfortunately i can't modify the schema , me and my team analyzed carefully the problem, so all fields you seeing are required on schema. now i just tested to do different fields maybe it could work if i knew syntaxe of edismax: and on config this is SearchHandler but i

Re: CopyField can't copy analyzers and Filters

OK, back up a bit and consider alternative indexing schemes. For instance, do you really need all those fields? Could you get away with one field where you indexed the field _name_ + associated value? (you'd have to be very careful with your analysis chain, but...) Something like: C67_val_value1 a

Re: CopyField can't copy analyzers and Filters

and i use dynamicfields for NomDocument,ContenuDocument,Postit exemple: ContenuDocument_fr, ContenuDocument_en,ContenuDocument_ar NomDocument,ContenuDocument,Postit language_s fr en,fr,ar true is there any other solution to not separate fileds? Best regards A

Re: CopyField can't copy analyzers and Filters

i have documents (ar, en , fr) i need to index them and keeping analyzer and filter for each languages. here is all fields on schema to enderstand my probleme:

Re: CopyField can't copy analyzers and Filters

But aren't you already creating those 300 fields anyway: If you mean you have issues specifying them in eDisMax, I believe 'qf' parameter allows to specify a wildcard. Alternatively, you can look at the example used in Solr In Action book: https://github.com/treygrainger/solr-in-action/tree/mas

Re: CopyField can't copy analyzers and Filters

Hello, i have 300 feilds which are copied on "AllChamp" if i want to do separated fields then i need to create 300 * Number of languages i have, which is not logical for me. is there any other solution? Best regards Anass BENJELLOUN 2014-07-01 11:28 GMT+02:00 Alexandre Rafalovitch [via Lucene]

Re: CopyField can't copy analyzers and Filters

I believe, you were already answered. If you want to have text parsed/analyzed in different ways, you need to have them in separate fields with separate analyzer stacks. Then use disMax/eDisMax to search across those fields. copyField copies the original content and therefore when you search the

Re: CopyField can't copy analyzers and Filters

Hello, here is my configuration which don't work: shema: config: explicit velocity browse layout Solritas edismax *_ar^2 *_fr^3 *_en^2.2 AllChamp 100% *:* 10 *,

Re: CopyField can't copy analyzers and Filters

Three fields: AllChamp_ar, AllChamp_fr, AllChamp_en. Then query them with dismax. On Jun 30, 2014, at 11:53 AM, benjelloun wrote: > here is my schema: > > required="false" stored="false"/> > required="false" multiValued="true"/> > > required="false" multiValued="true"/> > > required="fa

Re: copyField and storage requirements

On 7/2/2013 1:58 PM, Ali, Saqib wrote: Thanks Shawn. Here is the text_general type definition. We would like to bring down the storage requirement down to a minimum for those 500KB content documents. We just need basic full-text search. Thanks!!! :)

Re: copyField and storage requirements

Thanks Shawn. Here is the text_general type definition. We would like to bring down the storage requirement down to a minimum for those 500KB content documents. We just need basic full-text search. Thanks!!! :)

Re: copyField and storage requirements

On 7/2/2013 12:22 PM, Ali, Saqib wrote: > Newbie question: > > We have the following fields defined in the schema: > > > > > > the content is field is about 500KB data. > > My question is whether Solr stores the entire contents of the that 500KB > content field? > > We want to minimize the

Re: copyField generates "multiple values encountered for non multiValued field"

On Thu, Jun 6, 2013 at 1:52 PM, Jack Krupansky wrote: > "read current state, manipulate fields and then add the document with the > same id)" > > Ahh... then you have an IMPLICIT reference to the field in your Java code - > you explicitly told Solr that you wanted to start with all existing field

Re: copyField generates "multiple values encountered for non multiValued field"

ing to a multivalued field. And you need a simple (non-Map) value for your ID field. -- Jack Krupansky -Original Message----- From: Robert Krüger Sent: Thursday, June 06, 2013 7:25 AM To: solr-user@lucene.apache.org Subject: Re: copyField generates "multiple values encountered for non multi

Re: copyField generates "multiple values encountered for non multiValued field"

-Original Message- From: Robert Krüger Sent: Thursday, June 06, 2013 7:15 AM To: solr-user@lucene.apache.org Subject: Re: copyField generates "multiple values encountered for non multiValued field" On Wed, Jun 5, 2013 at 9:12 PM, Jack Krupansky wrote: Look in the Solr log - the err

Re: copyField generates "multiple values encountered for non multiValued field"

I don't know what I have to do to use the atomic update feature but I am not aware of using it. But the way you describe it, it means that the copyField directive does not overwrite the existing field content and that's an easy explanation to what is happening in my case. Then the second update (wh

Re: copyField generates "multiple values encountered for non multiValued field"

On Wed, Jun 5, 2013 at 9:12 PM, Jack Krupansky wrote: > Look in the Solr log - the error message should tell you what the multiple > values are. For example, > > 95484 [qtp2998209-11] ERROR org.apache.solr.core.SolrCore – > org.apache.solr.common.SolrException: ERROR: [doc=doc-1] multiple values

Re: copyField generates "multiple values encountered for non multiValued field"

: I updated the Index using SolrJ and got the exact same error message there aren't a lot of specifics provided in this thread, so this may not be applicable, but if you mean you actaully using the "atomic updates" feature to update an existing document then the problem is that you still have

Re: copyField generates "multiple values encountered for non multiValued field"

-Original Message- From: Robert Krüger Sent: Wednesday, June 05, 2013 1:17 PM To: solr-user@lucene.apache.org Subject: Re: copyField generates "multiple values encountered for non multiValued field" OK, I have two fields defined as follows: and this copyField dire

Re: copyField generates "multiple values encountered for non multiValued field"

OK, I have two fields defined as follows: and this copyField directive I updated the Index using SolrJ and got the exact same error message that is in the subject. However, while waiting for feedback I built a workaround at the application level and now reconstructing the original state

Re: copyField generates "multiple values encountered for non multiValued field"

Try describing your own symptom in your own words - because his issue related to Solr 1.4. I mean, where exactly are you setting "allowDuplicates=false"?? And why do you think it has anything to do with adding documents to Solr? Solr 1.4 did not have atomic update, so sending the exact same doc

Re: copyField generates "multiple values encountered for non multiValued field"

I think the suggestion I have seen is that copyField should be index-only and - therefore - will not be returned. It is primarily there to make searching easier by aggregating fields or to provide alternative analyzer pipeline. Can you make your copyField destination not stored? Regards, Alex.

Re: copyField with * stops working with 4.2 (related to SOLR-3798 ?)

Thanks for the clarification! Although, maybe we need to come up with some simpler, more clear terminology. -- Jack Krupansky -Original Message- From: Steve Rowe Sent: Wednesday, March 13, 2013 12:50 AM To: solr-user@lucene.apache.org Subject: Re: copyField with * stops working with

Re: copyField with * stops working with 4.2 (related to SOLR-3798 ?)

I committed a fix under SOLR-4567. On Mar 13, 2013, at 12:50 AM, Steve Rowe wrote: > Yes, this is a regression, definitely my fault. Sorry Alex! > > The table on SOLR-3798 is missing this case: a glob matching one or more > explicit fields (as opposed to dynamic fields). > > I've filed a J

Re: copyField with * stops working with 4.2 (related to SOLR-3798 ?)

Yes, this is a regression, definitely my fault. Sorry Alex! The table on SOLR-3798 is missing this case: a glob matching one or more explicit fields (as opposed to dynamic fields). I've filed a JIRA: https://issues.apache.org/jira/browse/SOLR-4567 On Mar 13, 2013, at 12:20 AM, "Jack Krupansk

Re: copyField with * stops working with 4.2 (related to SOLR-3798 ?)

Solr-4503 made the changes to copyField semantics. Indeed, it is not clear whether Solr-4503 (or even Solr-3798) was really intended to de-commit existing functionality. I mean, the normal procedure is to deprecate a feature long before removing it. And, the wiki does not note the decommission

Re: copyField vs single field

ve a clear reason to go the other way. -- Jack Krupansky -Original Message- From: Otis Gospodnetic Sent: Wednesday, February 06, 2013 8:04 PM To: solr-user@lucene.apache.org Subject: Re: copyField vs single field The latter, I believe, but you lose the ability to give different weights to

Re: copyField vs single field

The latter, I believe, but you lose the ability to give different weights to matches on different fields. Otis Solr & ElasticSearch Support http://sematext.com/ On Feb 6, 2013 2:34 PM, "adm1n" wrote: > Hi, > > Let's assume I have to search for a string (textField) in 6-7 different > fields (us

Re: CopyField issue on Solr4.1

Major changes (i.e. 3 -> 4) have some such differences, but usually it's for the better. But it is sometimes disconcerting! Also, sometimes there are different defaults and you can get the old behavior back... Although you haven't quite said what was different. I know the stock typedefs have chang

Re: CopyField issue on Solr4.1

On 1/30/2013 7:28 AM, Upayavira wrote: Stored fields are now compressed in 4.1. There's other efficiencies too in 4.0 that will also result in smaller indexes, but the compressed stored fields is the most significant. The compressed stored fields explains your smaller index. As to why you get

Re: CopyField issue on Solr4.1

There are probably any number of changes between 3.x and 4.x to account for query differences. This includes bug fixes and in some cases new bugs, in areas such as the query parsers and various filters. The first step is to isolate a couple of examples of both false positive queries and false n

Re: CopyField issue on Solr4.1

Stored fields are now compressed in 4.1. There's other efficiencies too in 4.0 that will also result in smaller indexes, but the compressed stored fields is the most significant. Upayavira On Wed, Jan 30, 2013, at 01:59 PM, anarchos78 wrote: > Hello, > > I am using Solr 3.6.1 and I am very satis

Re: copyField - copy only specific words

Possibly with Shingles before the KeepWord filter to deal with multi-word situations (though I am not sure if KeepWord allows space-separate tokens in the file): http://stackoverflow.com/questions/14479473/ Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linke

RE: copyField - copy only specific words

Hi Use the KeepWordFilter on the destination field: http://wiki.apache.org/solr/AnalyzersTokenizersTokenFilters#solr.KeepWordFilterFactory Cheers -Original message- > From:b.riez...@pixel-ink.de > Sent: Fri 25-Jan-2013 11:41 > To: solr-user@lucene.apache.org > Subject: copyField - co

Re: copyField - copy only specific words

I think the best way will be to pre-process the document (or use a custom UpdateRequestProcessor). Other option, if you'll only use the "cities" field for faceting/sorting/searching (you don't need the stored content) would be to use a regular copyField and use a "KeepWordFilter" for the "cities" f

Re: copyField multiValued duplicates

Unless you stored all the original fields, I think you're stuck with re-indexing all your docs Best Erick On Mon, Nov 19, 2012 at 12:21 PM, Ravi Solr wrote: > Hello, > I have a couple of questions. I need an easy way to clean up a gaffe > with copyFields (close to a million docs). Is

Re: Copyfield query

Hello! As you can is in the http://wiki.apache.org/solr/SchemaXml#Copy_Fields the actual copying is done before analysis and indexing, so it doesn't matter if you store fields you use as source for your copy fields. -- Regards, Rafał Kuć Sematext :: http://sematext.com/ :: Solr - Lucene

Re: copyField

Oh this one. Yes I have it. myPhone'dan gönderdim 18 May 2012 tarihinde 23:14 saatinde, Yury Kats şunları yazdı: > On 5/18/2012 4:02 PM, Tolga wrote: >> Default field? I'm not sure but I think I do. Will have to look. > > http://wiki.apache.org/solr/SchemaXml#The_Default_Search_Field

Re: copyField

On 5/18/2012 4:02 PM, Tolga wrote: > Default field? I'm not sure but I think I do. Will have to look. http://wiki.apache.org/solr/SchemaXml#The_Default_Search_Field

Re: copyField

Default field? I'm not sure but I think I do. Will have to look. myPhone'dan gönderdim 18 May 2012 tarihinde 18:11 saatinde, Yury Kats şunları yazdı: > On 5/18/2012 9:54 AM, Tolga wrote: >> Hi, >> >> I've put the line > indexed="true"/> in my schema.xml and restarted Solr, crawled my >> we

Re: copyField

On 5/18/2012 9:54 AM, Tolga wrote: > Hi, > > I've put the line indexed="true"/> in my schema.xml and restarted Solr, crawled my > website, and indexed (I've also committed but do I really have to > commit?). But I still have to search with content:mykeyword at the admin > interface. What do I

Re: copyField

I'll make sure to do that. Thanks myPhone'dan gönderdim 18 May 2012 tarihinde 17:40 saatinde, "Jack Krupansky" şunları yazdı: > Did you also delete all existing documents from the index? Maybe your crawl > did not re-index documents that were already in the index or that hadn't > changed si

Re: copyField

Did you also delete all existing documents from the index? Maybe your crawl did not re-index documents that were already in the index or that hadn't changed since the last crawl, leaving the old index data as it was before the change. -- Jack Krupansky -Original Message- From: Tolga

Re: copyField after analyzer

Hello! It's not possible with copy fields right now. As you wrote - copy fields are copied before analysis is done. -- Regards, Rafał Kuć Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > Hi, > I want to copy/append different fields to one field, while applying a > different analy

Re: copyField question

Hi Tomas: These fields are for searching only. Currently we have around 1.8M docs indexed.and Assuming each Doc has about 20 of these additional fields to be created as dynamic fields (worst case scenario), and also there are about 6K if these different values (I.e. If we were to create static fi

Re: copyField question

I meant, how many values in total? A single document may have 20, but are those 20 shared with other document (even if they have different score) or each document will have 10-20 completely different values? I think Solr could handle a couple hundred of fields, but I don't know how it would behave

Re: copyField question

Hi Tomás: I think there is simplicity in your solution ;) A document would have Tens of different values. (at the most 20)Š So If were to follow your suggestion of naming a dynamic field with the value as the name of the field and the corresponding Score as the value. How would I go about chan

Re: copyField question

> However, If the multivalued complex data field is not possible. Is it possible to use copyField directive to copy fields if a certain score is higher than a threshold ? I don't think that's possible out of the box, but you could use custom UpdateRequestProcessor for for that. How many different

Re: copyField: multivalued field to joined singlevalue field

: > I want to copy all data from a multivalued field joined together in a single : > valued field. : > : > Is there any opportunity to do this by using solr-standards? : : There is not currently, but it certainly makes sense. Part of it has just recently been commited to trunk actually... https

Re: copyField: multivalued field to joined singlevalue field

On Thu, Feb 16, 2012 at 11:35 AM, flyingeagle-de wrote: > Hello, > > I want to copy all data from a multivalued field joined together in a single > valued field. > > Is there any opportunity to do this by using solr-standards? There is not currently, but it certainly makes sense. Anyone know of

Re: CopyField copying to self

On Thu, Oct 6, 2011 at 1:49 AM, Jamie Johnson wrote: > I have a field named test_txt which I am populating in some cases, and > not in others.  I also have a copy field directive to copy data from > _txt to text_txt.  Thigns seem to work except I believe the field is > also copying to itself.  Is

Re: copyField for big indexes

Bill, I was using it as a simple default search field. I realise now that's not a good reason to use copyField. As I see it now, it should be used if you want to search in a way that is different: use different analyzers, etc; not for just searching on multiple fields in a single query. Thank

Re: copyField for big indexes

It depends. copyField may be good if you want to copy into a Soundex field, and then boost the sounded field lower than the tokenized field. What are you trying to do ? On 8/22/11 11:14 AM, "Tom" wrote: >Is it a good rule of thumb, that when dealing with large indexes copyField >should not be

Re: copyField for big indexes

Thanks Erick -- View this message in context: http://lucene.472066.n3.nabble.com/copyField-for-big-indexes-tp3275712p3275816.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: copyField for big indexes

copyField should only be used if there's a good reason, that is you need to tokenize/analyze stuff differently, for instance faceting. It's not so much a matter of the index size, as whether the copyFields are necessary to get your needed functionality. You're right that you can construct queries

Re: CopyField into another CopyField?

: In solr, is it possible to 'chain' copyfields so that you can copy the value : of one into another? ... : : : : Point being, every time I add a new field to the autocomplete, I want it to : automatically also be added to ac_spellcheck without having to do it twice. Sorry no, the Inde

Re: copyField generates "multiple values encountered for non multiValued field"

: This is for debugging purposes, so I am sending the exact same data that are : already stored in Solr's index. ... : ERROR: [288400] multiple values encountered for non multiValued field : "field2" [fieldvalue, fieldvalue] : : The scenario: : - "field1" is implicitly single value, type

Re: copyField generates "multiple values encountered for non multiValued field"

Alexander, I saw the same behavior in 1.4.x with non-multivalued fields when "updating" the document in the index (i.e obtaining the doc from the index, modifying some fields and then adding the document with the same id back). I do not know what causes this, but it looks like the copyField logic

Re: copyField of dates unworking?

On May 27, 2011, at 1:04 AM, Ahmet Arslan wrote: > The letter f should be capital Hah! Well-spotted! Thanks. -==- Jack Repenning Technologist Codesion Business Unit CollabNet, Inc. 8000 Marina Boulevard, Suite 600 Brisbane, California 94005 office: +1 650.228.2562 twitter: http://twitter.com/jr

Re: copyField of dates unworking?

> >  The letter f should be capital. copyfield =>copyField

Re: copyField of dates unworking?

On May 26, 2011, at 1:55 PM, anass talby wrote: > it seems like reserved key words can't be used as field names did you try > to changes your date field name? Interesting thought, but it didn't seem to help. I changed the schema so it has both a "date" and a "eventDate" field (so as not to inv

Re: copyField of dates unworking?

it seems like reserved key words can't be used as field names did you try to changes your date field name? On Thu, May 26, 2011 at 9:54 PM, Jack Repenning wrote: > Are there some sort of rules about what sort of fields can be copyFielded > into other fields? > > My schema has (among other things

Re: copyField

> if i define different fields with different boosts and then > copy them into > another field and make a search by using this universal > field, the boosting > will be done? No. copyField just copies raw content.

Re: copyField at search time / multi-language support

This may not be all that helpful, but have you looked at edismax? https://issues.apache.org/jira/browse/SOLR-1553 It allows the full Solr query syntax while preserving the goodness of dismax. This is standard equipment on 3.1, which is being released even as we speak, and I also know it's being u

Re: copyField at search time / multi-language support

p;i=0&by-user=t>> > wrote: > > > From: Markus Jelsma <[hidden > > > email]<http://user/SendEmail.jtp?type=node&node=2747011&i=1&by-user=t>> > > > > Subject: Re: copyField at search time / multi-language support > > > To: [hi

Re: copyField at search time / multi-language support

a wrote: > > From: Markus Jelsma > > Subject: Re: copyField at search time / multi-language support > > To: solr-user@lucene.apache.org > > Cc: "Andy" > > Date: Tuesday, March 29, 2011, 1:29 AM > > https://issues.apache.org/jira/browse/SOLR-1979 &g

Re: copyField at search time / multi-language support

Thanks Markus. Do you know if this patch is good enough for production use? Thanks. Andy --- On Tue, 3/29/11, Markus Jelsma wrote: > From: Markus Jelsma > Subject: Re: copyField at search time / multi-language support > To: solr-user@lucene.apache.org > Cc: "Andy" >

Re: copyField at search time / multi-language support

https://issues.apache.org/jira/browse/SOLR-1979 > Tom, > > Could you share the method you use to perform language detection? Any open > source tools that do that? > > Thanks. > > --- On Mon, 3/28/11, Tom Mortimer wrote: > > From: Tom Mortimer > > Subject: copyField at search time / multi-lang

Re: copyField at search time / multi-language support

Tom, Could you share the method you use to perform language detection? Any open source tools that do that? Thanks. --- On Mon, 3/28/11, Tom Mortimer wrote: > From: Tom Mortimer > Subject: copyField at search time / multi-language support > To: solr-user@lucene.apache.org > Date: Monday, Marc

Re: copyField at search time / multi-language support

On Mon, Mar 28, 2011 at 2:15 PM, Tom Mortimer wrote: > Hi, > > Here's my problem: I'm indexing a corpus with text in a variety of > languages. I'm planning to detect these at index time and send the > text to one of a suitably-configured field (e.g. "mytext_de" for > German, "mytext_cjk" for Chine

  1   2   >