Thanks Steve and Yonik. This now makes sense. Updating the doc will be of
a big help.
With regards to deleting a copy-field, what I found is that if I have N
instances of the same copy-field, I have to issue N deletes to remove them
all. This behavior matches with the add and need to be kept.
> On May 6, 2015, at 8:25 PM, Yonik Seeley wrote:
>
> On Wed, May 6, 2015 at 8:10 PM, Steve Rowe wrote:
>> It’s by design that you can copyField the same source/dest multiple times -
>> according to Yonik (not sure where this was discussed), this capability has
>> been used in the past to eff
On Wed, May 6, 2015 at 8:10 PM, Steve Rowe wrote:
> It’s by design that you can copyField the same source/dest multiple times -
> according to Yonik (not sure where this was discussed), this capability has
> been used in the past to effectively boost terms in the source field.
Yep, used to be r
Hi Steve,
It’s by design that you can copyField the same source/dest multiple times -
according to Yonik (not sure where this was discussed), this capability has
been used in the past to effectively boost terms in the source field.
The API isn’t symmetric here though: I’m guessing deleting a
Hi Everyone,
I am using the Schema API to add a new copy field per:
https://cwiki.apache.org/confluence/display/solr/Schema+API#SchemaAPI-AddaNewCopyFieldRule
Unlike the other "Add" APIs, this one will not fail if you add an existing
copy field object. In fact, after when I call the API over and
