On Wed, Dec 9, 2009 at 2:41 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > So... the question is, do we have a concrete alternative to this that > is well fleshed out?
I do, I do... just a little variant that is geo specific and hence results in nicer names :-) <fieldType name="point" latSuffix="_lat" lonSuffix="_lon/> <field name="home" type="point"/> <dynamicField name="*_lat" type="tdouble" indexed="true" stored="false"/> <dynamicField name="*_lon" type="tdouble" indexed="true" stored="false"/> <dynamicField name="*_point" type="point"/> home_lat home_lon work_point_lat work_point_lon Note: if you want the double or tripple underscore to help prevent collisions... then you could use latSuffix="___lat" and define the dynamic fields that way. -Yonik http://www.lucidimagination.com On Wed, Dec 9, 2009 at 2:41 PM, Yonik Seeley <yo...@lucidimagination.com> wrote: > Here's an example of how everything could work with dynamic fields > (apologies if it it overlaps with examples already given by others in > this thread) : > > <fieldType name="point" fieldSuffix="_latlon" .../> // the subFields > for the points end in _latlon > <field name="home" type="point"/> > <dynamicField name="*_latlon" type="tdouble" indexed="true" stored="false"/> > > // And we also want to allow point dynamic fields > <dynamicField name="*_point" type="point"/> > > // Note: Grant make point more generic than geo, so it's 0 and 1 > instead of lat and lon > // OK, so now the indexed fields for home would be > home__0_latlon > home__1_latlon > > // And the indexed fields for dynamic field work_point would be > work_point__0_latlon > work_point__1_latlon > > Not the prettiest names... but I think everything is well defined (how > it would work with subFields of differing types.. have another param > specifying a different suffix, how it works with dynamic fields, etc). > > > -Yonik > http://www.lucidimagination.com >
