: > I guess most people store it as a simple string "key(separator)value". Is
or use dynamic fields to putthe "key" into the field name...
: > > > multiValued="true" />
...could be...
...then index value
if you omitNorms the overhead of having many fields should be low -
allthough i'm no
Shalin Shekhar Mangar wrote:
I guess most people store it as a simple string "key(separator)value". Is
there something special that you want to do with the values that you need a
custom field implementation?
no..not really.. I guess I could achieve it via payloads as well.. the
whole thing a
I guess most people store it as a simple string "key(separator)value". Is
there something special that you want to do with the values that you need a
custom field implementation?
On Mon, Jan 12, 2009 at 5:36 AM, Ian Holsman wrote:
> hi.
> I don't think this is a FAQ, but it's been bugging me for
hi.
I don't think this is a FAQ, but it's been bugging me for a while.
I want to store key/value pairs in a single field. for example
multiValued="true" />
where keyval would be a ID# and the value.
I'm guessing it is as simple as creating my own field class, but I was
wondering if there we
