Re: A defect in Schema API with Add a New Copy Field Rule?

2015-05-07 Thread Steve Rowe
On May 6, 2015, at 8:25 PM, Yonik Seeley ysee...@gmail.com wrote: On Wed, May 6, 2015 at 8:10 PM, Steve Rowe sar...@gmail.com 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

Re: A defect in Schema API with Add a New Copy Field Rule?

2015-05-07 Thread Steven White
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.

Re: A defect in Schema API with Add a New Copy Field Rule?

2015-05-06 Thread Steve Rowe
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

Re: A defect in Schema API with Add a New Copy Field Rule?

2015-05-06 Thread Yonik Seeley
On Wed, May 6, 2015 at 8:10 PM, Steve Rowe sar...@gmail.com 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.