Hi:
As you posted, a possibility could be, to define the fields "jobs" and
"batch" as multivalued and use the partial
update<http://solr.pl/en/2012/07/09/solr-4-0-partial-documents-update/>to
add new values to those fields.
Hope it helps.
On Sun, Sep 8, 2013 at 9:49 PM, anurag.jain <anurag.k...@gmail.com> wrote:
> Hi all,
>
> I am using solr dynamic field. i am storing data in the following format:-
>
> ------------------------------------
> id batch_* job_*
> ------------------------------------
>
> So for a doc, data is storing like:-
>
>
> ------------------------------------------------------------------------------------------
> id batch_21 job_21 job_22 batch_22 ...............
>
> ------------------------------------------------------------------------------------------
> 1 120 0 1 121 ...............
>
> ------------------------------------------------------------------------------------------
>
> Using luke request handler i found that currently there are more than 5k
> fields and 3000000 docs. And fields are always increasing because of
> dynamic
> field.
> So i am worried about solr performance or any unknown issues which can come
> to solr. If somebody had experienced please tell me. Please tell the
> correct
> solution to handle these issues.
>
> are there any alternatives of dynamic fields. Can we store information like
> below ?
>
> -------------------------------------------------
> id jobs batch
> -------------------------------------------------
> 21 {21:0,22:1} {21:120,22:121}
> -------------------------------------------------
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Dynamic-Field-tp4088775.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
