Can you explain a bit more? Because on the face of it, "unique IDs but shared content" doesn't make sense. The point of unique IDs is that they identify documents uniquely.
A more usual setup is to have the content correspond to the unique id. Is what you want really making your "code" field multivalued? Best Erick On Tue, Nov 16, 2010 at 11:23 AM, Thyago <tschle...@gmail.com> wrote: > Hi, > Is there any way to commit docs with unique key but with shared content ? > Example: > > <field name="id" type="string" indexed="true" stored="true" required="true" > /> > <field name="code" type="int" indexed="true" stored="true" /> > <field name="content" type="text" indexed="true" stored="true" /> > > I have a lot of itens with same content but with different codes. > Because this index is very large there any way to commit docs with unique > id and > code but with shared content to have a smallest index ? > > []'s > Thyago >
