On Sat, Nov 15, 2008 at 6:33 AM, Chris Hostetter <[EMAIL PROTECTED]> wrote: > > : > Is here a bug in DIH that caused these unrecognized fields to be ignored, > : > or is it possible the errors were logged (by DUH2 maybe? ... it's been a > : > while since i looked at the update code) but DIH didn't notice them and > : > reported success anyway? > : > : > : If the data contains a field name which is not defined in the schema.xml, > : then DIH ignores it. This is a very common use-case where you may want to > : process intermediate data and add it to a completely new field. For example, > : if you have first-name and last-name coming in from DB and you want to > : combine them into a new field "name" with TemplateTransformer. > > Ahhhh.... i see. so it's a feature that sometimes acts like a bug :) > > it might be worth considering a new @attribute for <fields> to indicate > that they are going to be used purely as "component" fields (ie: your > first-name/last-name example) and then have DIH pass all non-component > fields along and error if undefined in the schema just like other updating > RequestHandlers do. > > either that, or require that people declaure indexed="false" > stored="false" fields in the schema for these intermediate component > fields so that we can properly warn then when DIH is getting data it > doesn't know what to do with -- protecting people from field name typos > and returning errors instead of silently ignoring unexpected input is > fairly important behavir -- especially for new users. > Actually it is done by DIH . When the dataconfig is loaded DIH reports these information on the console. though it is limited , it helps to a certain extent > -Hoss > >
-- --Noble Paul
